AllAlert - An Allegiance monitoring utility

Compellor · Post by **Compellor** » Sun Jun 03, 2012 6:45 pm

Decided to try turning on AllAlert now that there's 35 people online. There were no numbers in the icon. When I clicked on it, it launched ASGS and logged in as normal, but brought up a .NET error widow with no error text. I clicked continue (other option was quit). I then tried to launch allegiance from AllAlert. AllAlert crashed instead.

Tried launching AllAlert again. This time it brought up the "Let's Rock" dialogue immediately, but there's no icon in my taskbar.

So, I let it launch alleg, then quit. Tried Launching AllAlert again, and this time it worked as expected displaying the number 37. I tried turning monitoring on and off. The first time I turned it off it brought up the "let's rock" dialogue, but it hasn't done so in the next three attempts.

Spunkmeyer · Post by **Spunkmeyer** » Sun Jun 03, 2012 7:48 pm

Thanks Compellor.

Compellor wrote:QUOTE (Compellor @ Jun 3 2012, 01:45 PM) Decided to try turning on AllAlert now that there's 35 people online. There were no numbers in the icon. When I clicked on it, it launched ASGS and logged in as normal, but brought up a .NET error widow with no error text. I clicked continue (other option was quit). I then tried to launch allegiance from AllAlert. AllAlert crashed instead.

This happened to me today too. Strange, need to look into it.

QUOTE Tried launching AllAlert again. This time it brought up the "Let's Rock" dialogue immediately, but there's no icon in my taskbar.[/quote]
That's normal, there is a delay in between.

QUOTE So, I let it launch alleg, then quit. Tried Launching AllAlert again, and this time it worked as expected displaying the number 37. I tried turning monitoring on and off. The first time I turned it off it brought up the "let's rock" dialogue, but it hasn't done so in the next three attempts.[/quote]
That's normal too. Alert checking done every minute, so it will not check as soon as you go online. I didn't want it to spam the ASGS server too often if somebody was doing the on and off toggle on purpose. But when you fire it up, it checks immediately.

BillyBishop · Post by **BillyBishop** » Mon Jun 04, 2012 10:36 pm

Nice work spunky, I hope to see it incorporated one day into allegiance/acss itself.

Spunkmeyer · Post by **Spunkmeyer** » Fri Jun 22, 2012 1:30 pm

Since we are going through a dry spell, and ACSS may be a little while longer, I'm going to fix the bug Compellor mentioned above and release an update, tonight. If everyone who isn't logging in because of low player counts uses this, we can easily get the numbers up.

Spunkmeyer · Post by **Spunkmeyer** » Sat Jun 23, 2012 8:08 pm

OK, got a little carried away and tweaked a bunch of stuff:

AllAlert 1.0 changes:

-The bug mentioned above where it would stop working with a strange error should be fixed.
-Rewrote the monitoring on/off logic from scratch, should be more robust now.
-Using a different mechanism to control ASGS, this should hopefully work consistently across all OS.
-Timeout for monitoring can now be set between 15 and 120 minutes, default has been increased from 30 minutes to 120 minutes.
-Monitoring will be turned on when you first launch the program.
-The alert box will now be displayed on top of all other windows.
-If you try to click the icon while it's already switching monitoring states, it'll beep at you and do nothing - that should take care of another potential bug.
-It will now always restart ASGS when turning monitoring on, so if you $#@!ed with ASGS launch settings meanwhile, it won't cause a problem any longer.
-Other minor stuff..

Linky:
https://dl.dropbox.com/u/21458077/AllAlert1.0.zip

TangoVictor · Post by **TangoVictor** » Tue Sep 04, 2012 8:05 pm

So Alleg has to be running for the program to work right? Not just asgs?

Spunkmeyer · Post by **Spunkmeyer** » Tue Sep 04, 2012 10:14 pm

Alleg is not involved. ASGS doesn't have to be running to begin with, but it will launch ASGS "to do its thing" which you shouldn't close.