4.0 Edit of the Options, and messages comand box suggestion in BYOND Discussion
|
|
Before 4.0, when a server crashed, or closed the place that held the map in the interface would turn to a huge white text box, and errors would show up, rather you got booted/banned, the DS had a fatel error, or if the server Crashed/closed.
In this case the server crashed, so normally you would get "Connection Failed" (simple enough right), but with 4.0 the screen goes black, fine, I go check the new Message/options box, and that just says "Loading Skin". Let me ask you, what does Loading skin have to do with a crashed server(it sounds like It's a Byond problem, not a server problem)?
I rather like the new remote commands, but I think it would be better to have the messages in the map section of the interface, like they were. Also please fix the messages, I don't know how it displays other messages as, but aparently atleast some of the messages are wrong(it took me like 5 minutes talking to the Admin of the game, to find out it was just a server crash).
|
When you disconnect from a server, I think the entire layout should dissappear, default window and all. The O&M window should open and, depending on the clients' preferences, should attempt to reconnect to the server.
Either way, the O&M window would show "Connection killed." or "Connection died." or whatever. Perhaps a distinction can be made between getting kicked out deliberately and the server going down.
To detect this kind of behavior, you could assign "warning levels" of sorts to the server. For each message the server does not reply to in x time, append the warning level. Once it's over a certain number, send a "Sorry server, but you weren't responding so I'm disconnecting" message and perform the behavior above. If the server does respond, reset the warning level.
At least that's how I'd do it when contacting another server through DM. Perhaps this way won't work for BYOND or perhaps a better method is available, but it's just a suggestion. (Suggesting this because I recall Lummox saying about something not being detectable, and I think it's related to this very issue.)
-- Data