Server Help :: View topic - malfunctioning sendto

Server Help

General Questions - malfunctioning sendto

Cheese - Tue Nov 04, 2008 8:26 pm
Post subject: malfunctioning sendto

i cant seem to get sendto work work correctly anywhere...

what are the setup requirements? (server.ini stuff)
what is the usage, and all possible usages? (syntax)
who can it be used by?

because the way i have it set up now, it works correctly in getting the user OUT of the zone, (window shows client leaving) but there is no indication of the client arriving at the destination zone.
the client sees the 'entering arena' PERMANENTLY after the send, as in, never arrives, stays in the screen until you press esc.

L.C. - Tue Nov 04, 2008 9:31 pm
Post subject:

At the moment you can only use it in SSC connected zones as far as I know. Snrrrub has managed to get it to work for non-SSC though, probably through his work-in-progress client hack.

Maverick - Wed Nov 05, 2008 6:21 am
Post subject:

*sendto works fine at my own subgame server (only in PM and with the correct syntax).
I tried sending a player from my own zone to my own zone (*sendto 127.0.0.1,5900,arena) and the client experienced the same situation Cheese describes. The command probably doesn't work if you're trying to send a client to the same zone he already was in.

Nonetheless, we've had the command working properly in Trench Wars. We used it to send players from a private #arena (upon entrance) to an arena in our development zone. This worked fine.

Cheese,
there are no setup requirements. The command can only be used by system operators in PM and the correct syntax is:

Code: Show/Hide

*sendto IP,Port,Arena

All arguments are mandatory. For example:

Code: Show/Hide

*sendto 66.36.241.110,5400,afk

to send players to the afk arena in Trench Wars

Cheese - Wed Nov 05, 2008 7:35 pm
Post subject:

subgame, or subgame2?

i have only seen it successfully used in 2 zones, tw and mg

and i tried sending from a zone to the same zone, and a zone to another zone on the same network, both failed.

Maverick - Thu Nov 06, 2008 2:43 am
Post subject:

subgame2 ofcourse

JoWie - Thu Nov 06, 2008 4:13 am
Post subject:

maverick, wouldn't

Code: Show/Hide

*sendto 127.0.0.1,5900,arena

send the player to the zone he is running locally

Maverick - Thu Nov 06, 2008 1:58 pm
Post subject:

That's what I meant.

Snrrrub - Sat Nov 22, 2008 11:02 am
Post subject:

*sendto works only if the target zone you're sending a player to is connected to the SSC biller. That's why you can't *sendto anyone to your private zone.

I have managed to work around this (without making any client/server changes) but it involves masquerading as an SSC biller-connected zone. That's also why none of the SSA zones show the "not connected to SSC" warning (the client thinks they're all on SSC).

As long as the client thinks it's connecting to an SSC zone, it will happily respect *sendto.

Technical details: the client, if being sent to a non-SSC zone, will clear out its password (all '\0' characters) in the login packet. The target server will reject the client due to bad password. I suspect the client doesn't show the "warning, this zone is not connected to SSC" dialog or an "invalid password" message box because either:

a) the client at that point is not in a state to display dialog boxes (fullscreen) or
b) the user experience would be pretty bad if you're in a zone and you're randomly asked if you want to connect to a non-SSC zone

Personally, I think it's the former rather than the latter but that's just pure speculation.

-Snrrrub

Chambahs - Sat Nov 22, 2008 1:23 pm
Post subject:

snrrrub, you have too much time on your hands <3

Cheese - Sun Nov 23, 2008 2:55 pm
Post subject:

so did i hear correctly in putting
AskNewUsers=0
in [misc] in server.ini to remove the non ssc message box?
and will that alone allow it to work?

if i can get this thing to work, i can do a lot of good things...

Cheese - Thu Dec 04, 2008 6:28 pm
Post subject:

bump

Snrrrub - Sun Feb 01, 2009 1:43 pm
Post subject:

No, there's no way for a server to control the SSC message box. If there was, there wouldn't be any point to having that message in the first place.

-Snrrrub

Cheese - Sun Feb 01, 2009 2:19 pm
Post subject:

Snrrrub wrote:

I have managed to work around this (without making any client/server changes) but it involves masquerading as an SSC biller-connected zone. That's also why none of the SSA zones show the "not connected to SSC" warning (the client thinks they're all on SSC).
-Snrrrub

how did you manage this then...?
and does this mean ssa can send to ssa?