Author Topic: Game rating system. (Trying to make this client sided) FILES AVAILABLE!  (Read 7227 times)

Code: [Select]
switch$(%message)
{
   case 1: %cansend = 1;
   case 2: %cansend = 1;
   case 3: %cansend = 1;
   ...
   case 9: %cansend = 1;
   case 10: %cansend = 1;
   default: %cansend = 0;
}
A server-side mod is abusable. It'd be really, really easy to just set up my server to send you a 10/10 rating every eight seconds with a random BL_ID to make mine appear the best.

A client-side mod doesn't work unless everyone has it - the ratings are a bit useless if only ten people out of the 13,000 or so Blockland currently has can rate it at all.


Hmm, I've been trying to get around that.
Like make a pass word and hide it in the script.

I want to see it work and be tested by people, and I'll find some way around it.

Tom

Too bad its against the rules to DSO.


Tom

DSO encrypts the files so they can't be edited.

Passwords in the file can be taken out really, really easily. Don't bother.

A DSO is an encrypted script file which cannot be read by people but still run by Blockland. However, Blockland uses a different version of the DSO format to other Torque games and Badspot has not included the compiling functions in the game to make files into DSOs - only he can make them, that's what allGameScripts.cs.dso and allGClientScripts.cs.dso are.

Passwords in the file can be taken out really, really easily. Don't bother.

A DSO is an encrypted script file which cannot be read by people but still run by Blockland. However, Blockland uses a different version of the DSO format to other Torque games and Badspot has not included the compiling functions in the game to make files into DSOs - only he can make them, that's what allGameScripts.cs.dso and allGClientScripts.cs.dso are.


What about a pass locked .zip file.
Or a ton of comment spam and really long variable strings that are encoded a ton.

Okay, here is a good example.
This is just a # rating my name and an example server name:




Code: [Select]
-huge sniped-
« Last Edit: July 12, 2009, 02:03:28 AM by Azjherben »

Tom

What about a pass locked .zip file.
Or a ton of comment spam and really long variable strings that are encoded a ton.
Locked zips probably won't be allowed either. People would still be able to find the function if you did lock it somehow.

Locked zips probably won't be allowed either. People would still be able to find the function if you did lock it somehow.


What do you mean allowed?
Will bad-spot personally come and check every zip to see if it's locked then personally go to every person and delete their zip file?

I doubt Blockland will be able to read it at all if it's encrypted.

Also, please remove the massive page-stretching hash code...

Tom


What do you mean allowed?
Will bad-spot personally come and check every zip to see if it's locked then personally go to every person and delete their zip file?
Badspot probably doesn't want locked zip files because people could put malicious code in it and it would be hard for people to find out.

Plus, there's plenty of zip password breakers on the internet.

Badspot probably doesn't want locked zip files because people could put malicious code in it and it would be hard for people to find out.

Maliciouis? Just from a .cs file? Doubt it could do much. If it did, than just delete it.

Tom

Maliciouis? Just from a .cs file? Doubt it could do much. If it did, than just delete it.
People could create lots of little things. Like TBM.

People could create lots of little things. Like TBM.


Wasn't that an old competitor of RTB?