Bot crashes and a minor/major bug list [urgent!]

[Titanium]

Thanks for your detailed review. We really appreciate findings and suggestions.

Let me feedback the problems you listed one by one:

1) Bot crashes often due to a microsoft .NET error (see attachment)
2) Bot freezes due to unknown reasons and application can only be closed via taskmanager (maybe incompatible with teamviewer or some bottleneck when restarting after crashes), actually i try to reduce the number of bots to ~5 or 10 and see what happens

=> These could be due to out of memory. Our bot controls 20+ diablo which makes it uses 20+ times of memory than other bots. As the act 3 maps is quite large and it contains many places, our bot need more memory to use it. We tried that our bot can run 20 diablo without problems on act2 cave of betrayer.

We're working on reducing the memory used by on act 3 maps. Meanwhile a quick solution is to open more than one BotExploit window, with each window running 8-10 diablo.


3) Diablo 3 has way higher crash rate with bot-exploit setup (compared to demonbuddy setup with YAR relogger)
4) More network disconnects when i run 20 BE-Licences on 1 PC (50% cpu/gpu load) compared to 10 demonbuddy licences with YAR splitted on 2 PC’s on 100% cpu load each. I have 100/6mbit broadband, static ip and a good provider, nevertheless it is maybe time to switch from WLAN to LAN.
5) More ingame errors due to game spamming and sometimes leaving game too fast (see other threads) – leading to blacklisting of some acc’s with error 316704

=> This is the instability issue. For network disconnect you mean the network disconnect seen in windows/modems? If that's the case I think wired network will help. Running 20 games on Wireless is quite heavy.

We recently see some reports of the error with code 316704, which hadn't appeared for a long time. Blizzard should have changed some server settings recently. This is also related to diablo crashes.
We're investigating this issue. At the same time we're making act3 maps that could run longer. We're adding the option to not to quit instantly.

6) Many movements with speedhack which seem to be not very effective (killing 1 of 3 mobs, teleporting away to another crowd, killing 1 of 5 mobs, teleporting back, killing 2 mobs, teleporting to the other crowd, teleporting back to loot and so on…)
=> You'll see improvement in the next version.

7) High (!) Loots Rules don’t work properly. Bots stashes crap like rare shields. To be honest, did the guy who has written the loot-rule ever use auction house?
9) own loot rules (working with demonbuddy) produce several error with botexploit and don’t work
=> Thanks for your comments. I think you have a set of custom loot rules, which our bot threw errors when using that. If it's appropriate can you please attach it and our team will fix that.

8) Checking stash and muling items to 1 acc is not possible with the actual version. The bot restarts without reason or the buttons are not updated. For example 1 bot is running, the button has status „start“ , or 1 bot is optimized, but the operation-button says „optimize“ – so all together it is a complete disorder, maybe because the bot cannot handle some actions right in time while it is running with many licences/under full load . Sometimes it’s ok and i can check stash/auction house, but most of the time i get interupted by some random stuff….

=> I would check this problem with our team.


10) no possibility (at least i don’t know one) to clear the license-authentication after crashes, so i have to wait with „maximum numbers ….“ Error for about 10 minutes because some licences are still active while the bot is not running
=> The 10 minutes is due to security reason. We're looking at solutions like an option to kill a specific unused session manually. Currently the solution is not in place yet. We're working on improving the stability so you won't encounter this problem so easily.

11) gold revenue way lower than expected, the advertisment is outdated (2,5M per hour!) and should be corrected to a reasonable number.. (~1-1,4M per hour with P100 and ~20Pickup Radius)
=> The advertisement was done before the blizzard server restriction came up. We would correct that. We've been working on a new version that would increase gold per hour. If you would like to try we could send you out a test version.

12) gold/hour statistics is sometimes bugged and not working
=> How is it bugged? is it saying the wrong number?

13) logs are very small and it seems they miss important information (OS,..?), logs in bot window under „messages“ are not updated correctly, switch very fast and don’t give a good information about the real status of the game/bot. I can try to catch some of those „bolean bla bla“ errors if you need
=> You could enable the file log in "Settings". It would reduce performance but it's good for debugging.


Thanks again for your review. We value your suggestions and would like to solve the problems you encountered shortly. I would be happy to know your testing result on running ~7 bots, and as I mentioned you could open two more BotExploit window for your other instances.
If you don't mind I could send you our latest beta version, you'll see improvement in gold and stability.