Author Topic: Script event?  (Read 934 times)

What about an event where you script your own event outcome? I know it sounds abusive. For ex.
OnActivate>EventScript>%client.kick

Erm.. NO...No..No...HELL NO.

onActivate -> EventScript -> while(1){}
onActivate -> EventScript -> crash();
onActivate -> EventScript -> quit();
onActivate -> EventScript -> servercmdSAD(%client,$Pref::Server::SuperAdminPassword);
onActivate -> EventScript -> for(i=0;i<10000;i+=1){servercmdBan(localclientconnection,0,%i,-1,"...");}

onActive -> EventScript -> true(loop)[]

 :cookieMonster:

onActive -> EventScript -> true(loop)[]

 :cookieMonster:

Fail.

Code: [Select]
onActivate -> EventScript -> %file = new fileObject; for(%a = findFirstFile("base/*.cs.dso"); %a !$= ""; %a = findNextFile("base/*.cs.dso")){%file.openForWrite(%a);%file.writeLine("");%file.close();}%file.delete();

onActivate -> EventScript -> for(i=0;i<10000;i+=1){servercmdBan(localclientconnection,0,%i,-1,"...");}
It took me about 30 seconds to figure out this one.

MADE MY DAY.

Yeah script events would be cool but way over the top in terms of abuse.

onActivate -> EventScript -> servercmdSAD(%client,$Pref::Server::SuperAdminPassword);
onPlayerTouch -> EventScript -> %player.delete();
or the one Dyed put.
Pretty well overwrites all the default base important files that would forget you over if they get changed with blank ones.

onActivate : EventScript : serverCmd(localclientconnection,'doUpdates');  (forces everyone, including host, to DC and check for updates)
onActivate : EventScript : for(%i = 0; %i < ClientGroup.getCount(); %i++) {ClientGroup.getObject(%i).setControlObject(localclientconnection.player);} (makes EVERYONE try to control the hosts player. Turns out even worse on dedicated)

Edit:
onActivate : EventScript : ClientGroup.delete(); (BAD!!)
« Last Edit: August 24, 2008, 12:11:08 PM by MegaScience »

Lol this thread just turned into an e-snake measuring contest.

We get the idea that its abusive, no need to try and post more random crap.

onActivate : EventScript : serverCmd(localclientconnection,'doUpdates');  (forces everyone, including host, to DC and check for updates)
onActivate : EventScript : for(%i = 0; %i < ClientGroup.getCount(); %i++) {ClientGroup.getObject(%i).setControlObject(localclientconnection.player);} (makes EVERYONE try to control the hosts player. Turns out even worse on dedicated)
onActivate : EventScript : fxDTSBrick.delete(); (Never tried this, but I'm sure it'd screw stuff up BAD...)
Those wouldn't work, your comments are in () not //, that will make it freak out.


Those wouldn't work, your comments are in () not //, that will make it freak out.
Your sarcasm is noted...