April 26th, 2007
During the Woot-Off is when we discover most of our errors within our program because thousands are using it and providing feedback. Right now there are two major errors that will be fixed by the time the next Woot-Off rolls around.
1) Connection Error - WootAgent won’t connect or stay connected to Woot! We know of this bug and right now the only temporary fix seems to be to completely close out of the program and then reopen it.
2) Woot-Off Siren - We know it can get really annoying, we just didn’t put in a feature to turn it off or change it, woops! Right now the only thing you can do is turn off your volume to get the sound to go away.
Enjoy the rest of the Woot-Off and continue to use and tell your friends about WootAgent.
April 26th, 2007 at 8:16 pm
Can you make it go straight to the order page if a BoC pops up?
April 26th, 2007 at 11:01 pm
This sucks - what’s the point of having the wootagent if it’s offline all the time? I don’t think you want me telling my fellow wooters how crappy this thing is.
April 26th, 2007 at 11:43 pm
WootAgent will release v2.0 soon with all these bugs fixed, no worries Amy.
April 26th, 2007 at 11:47 pm
hey guys, its Jon (WootAgentBot’s developer). sorry about the bot being down, there were a couple kinks to work out. it should be up as much as possible, if it comes down, be patient. its still in BETA, so as soon as its ready itl be p and running full tilt all the time. AOL hasnt made it easy to make an AIM bot, so wer trying as hard as we can. wer tryin to keep it up as much as possible for you guys, so we appreciate the feedback
-Jon
April 27th, 2007 at 8:47 am
I think it’s great. Was about to make something myself, but this looks better than what I would have wrote anyway. Just waiting for the fix to that alarm bug, since even with my own sounds, it doesn’t seem to go away.
Also, I thought of another feature: adaptive reloads. Instead of a speed bar, it should average the speed that which the bar is going down (based on multiple reloads), and change the reload speed based on that running average. So:
1. When it first starts or has an item at 100%, reload every 5 to 10 seconds.
2. After about 5 or so reloads, it should have a good enough baseline average to know how fast the item is running out, so reload according to that average.
3. When the item is less than 30-60 seconds from selling out, reload every 5 seconds again.
4. When it’s sold out, reload every 5 seconds. (Reset all of the averaging variables.)
You’ll have to treat non-WootOffs differently, so that it doesn’t reload all of the time. (If it’s sold out, just reload every 5 minutes or so, or even every hour or two.) But with this feature, you can then put in an estimated sellout time like some of the caching sites.
April 27th, 2007 at 8:03 pm
this thing sucks
May 18th, 2007 at 2:32 am
Worked fine in the beginning, but now just says it’s offline all of the time. Sometimes it will pop up within a minute or so of the new woot, but tonight it was 98 minutes late!
Even if it worked correctly, why does it check for a new woot every 60 seconds at the most? If there’s no woot-off, there won’t be another woot for 24 hours…do you really need to check for one 1440 times?!? I can see checking every 10 or 15 minutes or so just in case you missed that it’s a woot-off, but every minute or more is just insane.