serverwarp() doesn't work serverside

[Switch]

So I was testing some stuff on jothegreat55555's server, and I tried to make a relog/disconnector (to work on other people), and it doesn't work serversided.

This is the errors in RC that I get

PHP Code:

Script: Function serverwarp not found at line 4 in script of SwitchTest (in level lc_a1.nw at pos (0, 0))
Script: Function serverwarp not found at line 8 in script of SwitchTest (in level lc_a1.nw at pos (0, 0)) 


The first line is using "/relog", the second is using "/disconnect" (obviously).

This is the script I'm using

PHP Code:

function onActionServerSide() {
  if (params[0] == "/relog") {
    with (findPlayer(params[1]))
      serverwarp(servername);
  }
  if (params[0] == "/disconnect") {
    with (findPlayer(params[1]))
      serverwarp("Login");
  }
}

//#CLIENTSIDE
function onPlayerChats() {
  temp.token = player.chat.tokenize();
  if (player.chat.starts("/relog"))
    triggerserver("gui",this.name,temp.token[0],temp.token[1]);
  if (player.chat.starts("/disconnect"))
    triggerserver("gui",this.name,temp.token[0],temp.token[1]);
} 


My question is, is there any way that it will work serversided, or can it be implemented to be serversided?

Not really necassery, I just think it's kind of odd how switching servers seems to be more like something serversided, not clientsided.

[xXziroXx]

Have a clientsided timeout read a random variable, say client.reconnect, then if its true - first unset the variable, then serverwarp. Piece a cake.

EDIT: And it's obviously the client that handles server changes, since it's the client that manually change servers - why would that ever be serversided?

[Tigairius]

Originally Posted by Switch

Not really necassery, I just think it's kind of odd how switching servers seems to be more like something serversided, not clientsided.

just put something like this in a system weapon:

PHP Code:

//#CLIENTSIDE
function onActionclientside() {
  switch(params[0]) {
    case "reconnect":
      serverwarp(servername);
     break;
  }
} 


then serverside just do

PHP Code:

with (findPlayer(params[1])) 
  triggerclient("gui", systemweaponnpcname, "reconnect"); 


[Switch]

Originally Posted by xXziroXx

Have a clientsided timeout read a random variable, say client.reconnect, then if its true - first unset the variable, then serverwarp. Piece a cake.

EDIT: And it's obviously the client that handles server changes, since it's the client that manually change servers - why would that ever be serversided?

heh, dont wanna mess with that
And also, it's SERVER changing.

Originally Posted by Tigairius

just put something like this in a system weapon:

PHP Code:

function onActionclientside() {
  switch(params[0]) {
    case "reconnect":
      serverwarp(servername);
     break;
  }
} 


then serverside just do

PHP Code:

with (findPlayer(params[1])) 
  triggerserver("gui", systemweaponnpcname, "reconnect"); 


Was gonna do that, but not sure they want me to

[Chompy]

Originally Posted by cbk1994

For that script, just keep it clientside anyway.

It's a script to reconnect and disconnect other players. ;p

[cbk1994]

Originally Posted by Chompy

It's a script to reconnect and disconnect other players. ;p

Oh, I read over it too fast :P

[Tolnaftate2004]

You guys really win the obfuscation award.

PHP Code:

addweapon("disc or rec"); 


PHP Code:

//#CLIENTSIDE
function onCreated() { serverwarp("Login or Your-Server"); destroy(); } 


[xXziroXx]

That destroy() won't be called since the player no longer is on the server.

[cbk1994]

Originally Posted by xXziroXx

That destroy() won't be called since the player no longer is on the server.

Yes it would, it lags a bit. But, it's not a good practice in my opinion.

[Tigairius]

Originally Posted by Tolnaftate2004

You guys really win the obfuscation award.

PHP Code:

addweapon("disc or rec"); 


PHP Code:

//#CLIENTSIDE
function onCreated() { serverwarp("Login or Your-Server"); destroy(); } 


I don't like to use an entire weapon for the sake of doing a temporary task.

[Tolnaftate2004]

Originally Posted by xXziroXx

That destroy() won't be called since the player no longer is on the server.

The player object still exists for a while after logoff.

Originally Posted by cbk1994

Yes it would, it lags a bit. But, it's not a good practice in my opinion.

And this lag is of no harm to a player who is not really playing the game....

Originally Posted by Tigairius

I don't like to use an entire weapon for the sake of doing a temporary task.

And I don't like insecure triggers!

[xXziroXx]

Originally Posted by Tolnaftate2004

And I don't like insecure triggers!

So how come you and everyone else ignored my suggestion? Just cram it into a script that already uses a .05 timeout and check for client.reconnect there.

[cbk1994]

Originally Posted by Tolnaftate2004

And this lag is of no harm to a player who is not really playing the game....

I basically meant that once calling serverwarp(), the player stays on the server for a few seconds.

[Tolnaftate2004]

Originally Posted by xXziroXx

So how come you and everyone else ignored my suggestion? Just cram it into a script that already uses a .05 timeout and check for client.reconnect there.

Because... client. variables can be set by a... client...
I could kick you off indefinitely, I guess maybe that's why.

Also, I was not arguing with you cbk, just statin' facts.

[xXziroXx]

Originally Posted by Tolnaftate2004

Because... client. variables can be set by a... client...
I could kick you off indefinitely, I guess maybe that's why.

Yeah, but it's a such a likely scenario.


Then how about checking for clientr.reconnect, and if it is true, reconnect the player. Then, have it set to false upon login in the Control-NPC? Happy now?