Suggestion: Clientside Join

[Velox Cruentus]

Alright.... Let's see what we have!

NPCServer updates(6)
http://forums.graalonline.com/forums...ad.php?t=60137

This brings to the attention of clientside joins.

Stefan says security risk. I say more powerful engine.

PHP Code:

...
  item = new TStaticVar();
  item.join("iobj");
  item.setup( 1 );
... 


This, clientside, can be used as something VERY useful for clientside item management. There IS a security risk, but is Stefan's md5sum checks are good, then it should crash the client if they do hamper the scripts.

But! You can make a join function that LIMITS the join CLASSES only to classes in 'clientjoin' Server Options. This would add power to the scripting engine (having variables as classes), AS WELL AS having a secure system.

E.G.:

PHP Code:

clientjoin=door,items,trees 


[Skyld]

But how would you define what in the class to join();?

Would it automatically send and join the clientside script of the class?

[Velox Cruentus]

I would presume so. It would be easy to cache the clientside portion of the class, and have that easily applied to others. Maybe on login, cache the clientside portion of the clientside classes serveroptions.

[Admins]

Problem might be security, that's why it has not been added yet. A clientside-join would require that the client can request any class code. On the other side it is hard to add script code on clientside now, so it might be possible to add.

[petro1212]

Originally Posted by Stefan

Problem might be security, that's why it has not been added yet. A clientside-join would require that the client can request any class code. On the other side it is hard to add script code on clientside now, so it might be possible to add.

Atleast make sure it only works for defined classes listed in serveroptions. Like Velox suggested. Cause it would be annoiying if one manages to do the impossible and somehow inflict damage towards a server

[Admins]

Originally Posted by petro1212

Atleast make sure it only works for defined classes listed in serveroptions. Like Velox suggested. Cause it would be annoiying if one manages to do the impossible and somehow inflict damage towards a server

You can probably not do damage to the server if the server is scripted good, but I could imagine someone using some memory editor to change the name of a class to make some object load a different class into memory which would change variables in a different way. Defining the list of joinable classes might be good yes.