gurete

The experimental project contains its own quester, own combat engine and own fightclasses using that combat engine. It was developed with 3.3.5a in mind and I tried to move it to Legion+ and 64 bit. None of it works in its current form. Git history may help. This also has a modified version of Reapler's WowDB.
The fightclasses zip contains everything ever posted on here. It has HMP, my fightclasses etc. This works 100%, you just need to put your own WRobot binaries into the projects.

I can't maintain the code anymore and at the moment it just costs me money. Everything has officially been abandoned. Servers will go down in June or July whenever my contract runs out.
 
Feel free to do with this code whatever you want and do as you please. This does NOT include turning it into paid products. 
I had a good run here on WRobot and hope at least the Wholesome team can make use of some of this.
wrobot-experimental.zip wrobot-fightclasses.zip

Happy New Year to all !

I'm excited to start another year and look forward to continuing to serve you with WRobot.

This year marks a special milestone for us as we celebrate the 10-year anniversary of WRobot. 
I'm grateful for your support and look forward to many more years of success together. 

Thank you for choosing WRobot, and I hope you have a happy, healthy, and prosperous new year!

View full article

You get black screen (mainly when you use remote desktop software or when you try to record or take screenshot)
Since WRobot 2.0 you can get a completely black WRobot window when viewing with remote software like TeamViewer, to resolve it:
Close WRobot Open and edit with notepad file "WRobot\Settings \RobotManagerGlobalSetting.xml" Replace <CanProtectAgainstScreenshots>true</CanProtectAgainstScreenshots>  by <CanProtectAgainstScreenshots>false</CanProtectAgainstScreenshots>  (if you don't found first line, add second line before "</robotManagerGlobalSetting>") Save file and you can relaunch WRobot.

There have been multiple banwaves  in the past 2 weeks. 
Everyone is hopeful there is a work around, but as far as i know this is the only public bot available all eyes on us.
If we can't even make it 2 weeks it wont pay for itself the bot has to make it atleast 30 days to be profitable. 
But even then who wants to be banned every 30 days.
 But like i said 30 days is 50/50  blizzards get half the gold you get the other half.
 
Will see.   3/8 the bans started this time. If you don't see another wave in 30 days then maybe its a fluke :) 
 

Oki Gurete i use what you said to find a way to launch relogger. 
You need a file named ReloggerGeneralSetting from setting folder that you can find in any of your old install add it in your new one.
Then you need Relogger.exe.config from wrobot folder. Do as before take it from old install and put it on new one.
 
 

ich botte seit nem jahr und hab keinen bann erhalten.