Client-Packet Id: 41 Rest: serverid/name
Server-Packet Id: 178 Rest: serverid,servername,ip,port
Could be useful in the future when we possibly have a NPC-server and start to use the Graal v4 client since it needs a scripted serverlist.
serverid could be either the name or the ServerHQ/Playerworlds ID-number. Serverid can’t contain spaces as far as I know.
It’s also needed for graal://Servername to work.
Is that handled by the gserver or the listserver?
Why else would he be requesting it?
[QUOTE=Agret;18382]Is that handled by the gserver or the listserver?[/QUOTE]
The client gets a NPCw with serverwarp Lol; in it.
When the playertriggers it, it sends a question to the server: What is the ip of the server named Lol; The gserver sends a request to the listserver to see if the server exists, if it exists it sends back: id,Name,ip,port
then the gserver sends back that info to the client.
Merged doublepost_______________
I actually found those packets like 4-5 months ago and requested it to be added back then, but I guess it’s not that big of a deal yet.
updated first post to contain packet id’s
___Merged doublepost__________________
lol, serverpacket 170 is called ghostmode in the source. 
They might’ve replaced it when they removed ghost mode.
In v2, v3 and v4 it’s ghostmode. In v5 it’s not. So where have they hidden the old GS1 serverwarp? ;(
Well, I was using the graalrelay to show each packet.
Might be wrong there.
Choosing a server on Loginserver triggers serverwarp so that’s how I got it.
We could just make the gserver spam through all the different IDs since we know the format of the serverwarp packet now.
I have already resolved that issue and another issue too.
Why don’t you share it with the rest of the class? :marlon:
Man I hate you guys sometimes lol
EAGLES SCREAM
No… there’s no cream.
You bastard lol, best moderator ever
Actually, that was my work. I thought that was funnier. 