Just cause I’m feeling generous. Click for bigger image on the second one.
What happens when the server dies?
The main UI - I know Last 5 Events shows 6+ in the window, screen was taken before I fixed the glitch.
I might just get this done soon ^_^
Edited 5am: configuration menu’s about half done (icons and sounds aren’t configurable yet, but the dialog’s face time, fade time, and fade speed are all configurable, along with the delay, timeout, and maximum alerts for the servers).
Features as of right now:
- Core is made of Awesome
- Tray icon has 4 graphics; one for normal, one as an alternate image for flashing, one for when there’s servers in warn status and one for when there’s servers in alert status.
- Saving and Loading is done and compatible with the old SysAlive files, minus a few useless things the other one stored (such as HC for an addon I never finished)
- Able to choose between ConnectOnly (the old SysAlive style) and HTTP (the New and Improved SysAlive style) on a server-by-server basis. HTTP will attempt to download the page served by the server and search for a <body tag; if it finds it, great, server’s online. If it doesn’t, it means one of two things: Either the webpage is throwing an error and it doesn’t have a fancy error page with a <body> tag in it, or the server’s down. Either way, SA3′ll mark it as dead since any good page shouldn’t be returning errors anyways.
- Annoying Sound Effects. Yes, I brought these back; nothing like being awoken out of a sound sleep to some of the loudest sound effects you want to be woken up with when a server is offline
So yeah, the to-do list still has some stuff on it that was considered “standard” in the old SysAlive (minimize to tray, automatically loading the Servers.XML on startup), but those are generally fairly easy to do. The help file for this on the other hand…Not so much.