Shadow

suggestion for the bot, is to add target id's to blacklist, an example would be to not attack a random elite or rare spawn that will most likely kill you while leveling or grinding.

Not sure if this is a bug or not, but I'm submitting it, Ive used Grinder for 1-30 so far, and converted a profile from mmolazy for 30-35 in southern barrens, then added the mob ids, The bot is attempting to run pet battles on a bunch of lvl1 adders and the toon doesnt even have pet battling trained, its giving me an error saying "Pet Journel is locked by another user on this account" I am multiboxing, but this should be irrelevant. I havnt noticed any settings in grinder that do petbattles while grinding, and I have looked. Im not trying to do pet battles, just wanna grind. I think I remember a setting for this in an earlier beta, but it was removed when the petbattle product was introduced. Curious to whats happening here, someone enlighten me? :) Bug report: *edit* I found a quick and dirty fix, if you change the min target level to 2 or something higher than the wild battlepets, then your ok. This doesnt really fix whatever is going on, but it works.

Anyone else notice combo points is missing? when working with a rogue or feral druid, some abilities require combo points, works just like runes or soul shards.

@Rarrrrrrrrrrrr can you confirm or deny that you still have this bug please?

Could you tell me if this update has solved any problems, also Creative and I will both be offering remote desktop assistance as a free service to anyone still having problems setting up the bot. PM either of us for more details on this, it is not a permanent service as of yet, but we are both willing to help iron out the last of the release bugs.

Just a quick update, After some other testing, it has been proven that reinstalling the base admin package through the installer corrects some bugs found in wrobot, whether installed with my installer or the .zip package. Truth be told, my installer is just a very fancy self extracting archive. What I do is run the zip on my computer in a separate directory, fully patch it, and then package those files. The installer then extracts them to the path chosen by the user, defaults to %ProgramFilesFolder%\WRobot. Most of the coding I did in the installer is to check for dependencies installed on the target computer. Example is .net 4.5 installed and c++ runtimes, and it installs them if not. I then added a page to verify internet connectivity checking download.wrobot.eu, and from there silently run a batch cmd that also silently runs update.exe to make sure all of the files in my archive are up to date. This does not currently check for package updates, but that in theory should not be a problem as the archive was created with the most recent base package. As soon as i collaborate with droidz, I will add the check that redownloads the base admin package, and slipstream any updates again. So I should have a new beta out in a few days. But as I have said before, this installer is mostly complete as I does everything it is supposed to be doing.

Got a report from a guildie yesterday that after reinstalling the admin base, both this fishing problem and the archy bug being found were corrected. tested with .zip and .exe installers. Per PM to Droidz, i will be rereleasing the installer in a day or two with changes to the way it updates.

i know gex personally, ive checked all his settings, what do you think is happening creative? Im with droidz, i think its a bug.

try and run the updater, click on packages, then admin, and reinstall.

i use pqr myself, so long as your 90 theres no problems, on my druid i created a fight class that only casts (cat form) and thats it, if you dont need anything done manually, you can not select a fight class. last thing, run the updater and click on packages, click on admin, and do a reinstall. Someone reported to me this fixed most issues they had.

also using the same mount for ground and flying can cause issues, I ended up finding that out the hard way. Make sure its spelled case sensetive.

Upload your log file too please.

I had a guildie report this same error to me, when I went to check if the bot was updated (even though install was ran through my installer) it errored out. Still checking to see whats causing it. I think it was c++ related.

you need to click on the wow process (character) you want to run the bot with, then click launch, are you multiboxing?

email it to me and ill put it on dropbox. Or if you have a dropbox account, link it.

you can try to use the profile converter built into the bot if you find a profile for a different bot that fits your needs, but other than that, I would say creative is the best at making profiles here, Ill give it a go when i get some time, but no promises, im working on the archy bug.

i connected to him through teamviewer to run the base update for him, i saw the error first hand, and experienced it once myself, but it also corrected itself, another user in my guild is reporting the same thing too

I went over this with gex personally, and have also seen this happen before, I can assure he had the product and general settings correct and he has all required files installed. I have also seen this bug before, but casting fishing manually one time corrects this. I was not able to get a bug report. What happens here is when clicking start, the bot spams casting () and its missing the fishing skill. Ive seen this on some occasions, but have yet to narrow down what causes it.

thanks guys, I worked hard on it :)

depends on the server, fishing doesnt sell so much for me, even cooking mats

a vpn can be but is not always a bad idea, not to endorse any particular service or program, but a vpn changes your ip address on its own unlike your isp, blizzard can and will detect your account logging in from these various ips and that will draw more attention to yourself. For that reason a vpn is not a good idea, but as creative said, we have warden scanning. And for the accounts thing, just like droidz stated, they will only ban the account caught botting, and if its your first offense and you havnt done anything severe or malicious you will most likely get a warning with a suspension over a ban.

Which profile are u using? And if you can post the debug log

Beta 1 is up, There is still one bug I am working out, but its real basic, when the uninstaller runs the only thing left behind is an empty folder in the start menu titled WRobot. You can obviously delete this manually, As soon as I figure out how to remove this I will reupload as beta1a. But other than that, I will only be releasing updates if bugs are reported to me and to rebase the installer if package files get updated. Ill retag this as a final release in a few weeks just in case anyone reports other bugs I missed.

HAHA my installer does work... But yea, C++2012 has be updated by microsoft to U1. ya need to make sure all files are up to date. and @Droidz, I am working on The beta release of my installer now, I will remove all of the testing notes and perhaps you could upload the finished version under http://wrobot.eu/files/category/3-wrobot/ or if you could change my permissions to upload to that directory.