Set ACL

While searching for a way to open WOW's directory to guest access and protect bot's directory from been poked by guests, I found SetACL, by Helge klein's

So I reused his program, and wrote my own to generate scripts to add guest access to WOW's directory, and remove guest access to bot's directory.

http://www.zolohouse.com/wow/wowFighter/tutorials/troubleshoot.html

German guest account name

Today another user on mmowned posted about can't use zolofighter to start WOW.
Since there are quit a few people complaining about it, I decided to try it myself. Doing it over lunch, what I did is add a guest user named Gast, and set GUEST:guest in settings.txt to GUEST:gast.
Surely enough I got the "Can't start WOW" message.

What happened is, a few month ago I switch the entire program to UNICODE based, so Asian players can see the correct outputs. But since settings.txt is still ascii, I used a windows api to convert it to Unicode. The problem is I specified the type to be UTF8 instead of ascii. So while it converts all ordinary ascii chars correctly, Gast is not one of them. It got converted into "gst".

So, another release.

busy days

I was so busy recently that I had to do something I recommended my users not to do: bot AFK. Start from morning till I got home at noon, so 4 hours each day is not that bad, generate some extra cash :-).

I have been doing this for 2 weeks now, with some days I don't even have time to start the bot. Well that is not exactly bad, because it generate some randomness on my bot patterns.

0.7.9.29

0.7.9.29 is released. Since I am so busy this is a temp release. Covers fixes for looting and typing issues (LOOTDELAY and KEYDELAY configuration added for config util). Some computer have problems looting because the cursor moves too fast for the game to react.

Also configUtil had exe rename config on global section. It will ask new name for zoloFighter.exe and zoloConfigUtil.exe, when you save it copies those files to the new name, and add a entry in settings.txt to specify the new name.

zoloFighter will use the name in the config file to launch configuration utility, so the process name will be different.

WOW blogger's forum

Found this from Full time WOW addict:

http://www.blogazeroth.com/

Found I saw most of them already :-)

Native Vista support added

I got sometime tonight and 0.7.9.24 is released, it has vista support, you can either right click zoloFighter and run as admin, or you can use startInVista.bat, which will prompt for admin privilege.

And after that you can use the "Start Wow" button to start WOW. No longer do you have to launch WOW yourself :-)

So far vista give me a good impression than my first time, it is secure! If WOW want to do something stupid, vista will prompt you and all you need to do is decline Of course you need to click the accept thing a lot, but that is life.

The best is zoloRunAs.exe is no longer needed. It gives a warning by one of the scanner at virus total. Now it is clean!
http://www.virustotal.com/analisis/4a654ff1c91d76be5bab109a9120c758

Fixes and worms

Yesterday I did a new release, add the ability in define action statements to pass a javascript string to wowApproach. The string can be a function, if returns false, the approach is aborted.

This is used to abort the initial approach of a mob. For example if you are a warrior, you must approach the mob to range before you can fight. But in the mean time if mob is tagged by another player, you need to abort the fight.
While doing that some minor loot and print problems are also fixed.

And today I found a strange issue. My new release is classified as a worm (feeds) by eSafe when I did a virus total scan.
After break everything apart, individually scanned all exes and later txt files, I found it is the AVBot.txt that is causing the problem.
Still not sure what triggered it (only eSafe reported it among 32 scanners), so I am going to assume it is a eSafe problem.