I will be busy

Due to some unexpected development on my part, I am now the cook in my house hold, and have volunteered to teach some kids on weekends. The teaching part is rather nerve breaking, took up the entire weekend, and the kids has an age gap that will make it rather difficult.

For that reason I will not be able to do much to WOW anymore, for at least 3 month.

The only good part is I know I am doing this for the better good of this world, so the sacrifice is well deserved.

0.8.3.22 Test release

This one has AB and Eye of storm battle field bot. This release requires BG addons, such as SSPVP or SmartQueue.

More test still required on AV, and I don't have time for wsg scripts yet.

Next target: BG bots

I will soon start work on BG bots, thanks to some people who helped me understand how SSPVP and QuickQueue works. It will be much easier to use an queue addon instead than recognize the state of battle field via pre-recorded images, which doesn't scale and hard to port to other languages.

Others are copying my security steps now

Yep, just saw the first bot (I will not name it) copying my run under less privileged user security :-) Too bad the other bot is attacking mobs by TYPING actual /script commands into WOW, which could be a dead give away. The upside for that is you don't need to depend on your key bindings, but since no player will do that, it will take Blizzard little time to crack that up :-)

The good news is Blizzard is busying with WOTLK right now, and after the release they will have to put all their resources on bug fixing, that will give most public bots with little security some time to survive.

Two Years of ZoloFighter

Just noticed I have zolo fighter released to public for 2 years now! From my own fighter history, fighter was released to public 2 years ago. I used it for myself for a while too. This is amazing. I remember when I first created the bot, I have to add way points one by one, it won't loot either. I was happy to have something just to kill the mob.

Now the bot is totally different than the old one, with all the security, javascript, Orbiter pathing.

Here are some statics that might be of interest:
Total number of different IP addresses that used the bot: 20000+
Total number of users that has paid: 300+
Total number of payments: 400+

Total $ amount I got in my paypal account: $200+ (because paypal take about 40% out of the dollar).

And because every year I just use the total dollar amount as my income from the bot, I am paying duplicated taxes on those (each year I will pay tax on the total amount, because I don't have time to deduct the amount that I already paid tax on from previous years, not much either). All income is donated of course, so this is just a money loser.

Google Chrome second try

Well I like the speed of the Chrome browser (It feels snappy), so much that I downloaded the browser twice, reinstalled it 3 times and trying to get it to work. I submitted bug reports etc, and finally decided to try google it.

Sure enough, problem found. It is a common problem, and to fix it, I need to add a " -no-sandbox" startup parameter to Chrome.

Now I am witting this blog in Chrome. Chrome is so fast and light weight (only 25mb in memory, a new tab is 12mb), and it has very cool tools (for developers). I can perpend viewsource: to anything and view their source, a build in javascript debug engine :-)

I love it. There is not status bar, but I am sure it can be brought out with something.

zoloFighter 0.8.3.15 released

Hastily released yesterday night with some testing. Small changes, the one that pushed me for the release is the z Compatibility mode was broken. The bot was matching z positions even when it is set to false in settings.txt.

The big reason for z position matching is the bot can pick the correct roads when falls a 1000 yard down on that bridge in AV. All the normal waypoint don't need that, especially the glider profiles which don't have z position.

Another fix is the bot will try to optimize key pressings, which matches closer to human behavior.