Why does this happen?

The server status displays inconsistent icons sometimes. I just checked again and now they're all on Update. Last time the server icons sere all on Online/Event even though the overall status was Update. Nobody has been changing the wiki status.

As Nexon works on maintenance, they put up/down the servers constantly to check stuffs. I guess it was a coincidence that the server status was refresh at the time of then putting up the servers again.

Yeah, the script is not broken. It reflects the actual state of the game servers. People keep overriding it because they think it's broken. Look at current game status and Login server. Those are always accurate during maint.

I don't think that is a very good user experience. Nobody was overriding the manual status. Why not just set all servers to update during an update?

Because, the script isn't smart enough to know there's an update. And what if the login server goes down, but the game servers are still up?

If "Current Game Status" is set to "Update", set everything else to the same. What situation would occur where the first is true and the latter is not?

Its actually the inverse....

If Login = online
    GameStatus = best of the servers
else
    GameStatus = login status

What's the algorithm for setting update then?

What do you mean by "setting update"?

The script looks at offline override, and uses that if the server is offline. Hence, if the login server is offline, and OfflineOverride is 'Update', the login status will be 'update'. Same with everything else.

So if the login server is offline and OfflineOverride is Update, set all servers to Update.

I guess. People seem to like the 'actual' statuses though. Too bad we can't do a poll on the wiki.

I like the actual statuses though. Cause it helps map down boss timers...

Can you explain how having Update instead of Online helps this?

No i mean when it's showing the ACTUAL statuses. Not an override.

"Online" would be the actual status. Either way, I am still confused as to how this helps.

Aubog looks at the actual statuses. By knowing (more or less) exactly when a server comes online (before the login does!), he can time the boss spawns.

If we set all statuses to update when the logon is update, then he can't time them properly.

I can time them in other ways. But Eh. It's really easier this way.