Master at IP

"Hey guys I can't login it says master at IP what should I do am I banned or what please help" is what a lot of players ask on Shoutbox whenever there's server check or downtime.

Could the message be changed to something more specific like only GMs/Admins allowed or something like that? :0

 

Maybe we can change it in the next .wz update.

 

This is a verious serious problem indeed.

 

Actually, this occurs when a server blocks out certain IPs, or just allows one main IP on a certain port. For instance, the login server and game server are on different ports, so when you're trying to connect to the game server via the login server and you're not the "master IP" which would the the IP(s) allowed into that port or server, you would receive said message. But, I agree that it's a serious problem since the Admin has not fixed it yet, or has not got around to telling people when he's using the server as a testing ground. That, or he has coded his network to give some IPs higher priority over other IPs, for instance maybe his GMs have a higher priority on his server than that of a regular player.

Yep.

 

Actually, this occurs when the whitelist config is enabled that and a login request is received from an IP (or other identifier) that does not match an IP (or other identifier) in the loaded whitelist.
When such a connection attempts a login request, the server replies with a packet(s) that instructions the client to display the "master at IP" message.

The server does not begin the login process with the current session if the above action occurs.

However, if a connection that is from an IP address or other identifier that matches an identifier on the whitelist, the login process will be carried out for that particular connection and any other additional processes.

 

I'm a Masters and I can't log in when that screen comes up. How is that not confusing?!?! Pls change.

 

We're currently making a list of things to be fixed in the next .wz update and I've added this to the list (with a suggestion for more suitable text).

The reason you currently get this message when the staff are checking the server prior to letting players on is quite simple. We had to choose from a number of preset error messages, none of which were remotely appropriate, and this was merely the best of a bad bunch!

Giltine, we have another server we use specifically as a testing ground. The error message that Raizel mentioned is only used when we're bringing the server back up after maintenance, updates or a crash.