Bot Exploit

Full Version: Bot crash and restart forever
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Code:
2013-07-01 03:11:30 Start at 2013-07-01 03:11:30 - stXXXXXX@XXXXXXXXX EU
2013-07-01 03:11:30 Bot Version 0.9.110
2013-07-01 03:11:30 Profile - Act 3 , Arreat Crater-Keep Depths 2-Fields of Slaughter 3-7-3.xml
2013-07-01 03:11:30 Start botting
2013-07-01 03:11:31 Prepare to start game
2013-07-01 03:11:34 Executing Order
2013-07-01 03:11:34 Executing MaxDeaths
2013-07-01 03:11:34 Executing ForceTownRun, 1
2013-07-01 03:11:34 Executing ToggleTargeting, 101758, 1
2013-07-01 03:11:34 Executing While, Me.IsInTown
2013-07-01 03:11:34 Executing UseWaypoint, 1, 6442
2013-07-01 03:11:34 Use Waypoint 7
2013-07-01 03:11:34 Exception System.Exception: Invalid Grid, size in X and Y must be power of 2
   at ...ctor(Byte[,] grid)
   at ...ctor(Byte[,] worldWalkGrid, Int32 gridOffsetX, Int32 gridOffsetY)
   at ..( worldSID, Int32 )
   at ..( destination,  nearDistance, Int32 attackMode, Boolean attackRange, Int32 attackRangeCaster, Int32 attackRangeElite, Int32 bath, Boolean loot, Boolean nearest, Boolean executeCheck,  breakDistance, Int32 openItems, Boolean maxStuck, Int32 maxTryTimes, Int32 willCheckStuck, Boolean )
   at ..(Int32 actor,  waypointNumber,  useWaypointTimes, UInt32 )
   at ..( snoId, UInt32 waypointNumber, UInt32 desiredPos,  useWaypointTimes, Int32 )
   at ..( attr, Dictionary`2 )
   at ..(XmlNode node, Boolean& parseChildren, Boolean& parseAgain, Boolean& breakOrder)
   at ..(XmlNode node,  )
   at ..(XmlNode node,  )
   at ..(XmlNode node,  )
   at ..( )
   at ..(Int32 maxTryTimes)


- Diablo 3 crashed (no idea why)
- BotExploit restarted D3

- Resumes game, leaves after 1 sec with the error above.

And continues to resume+leave directly until i restarted BotExploit.

Hopefully you can fix it. If you need any more info let me know.





Log of the session that crashes attached.
It was actually 130 mb large.. lol. Had to zip it.

There is some crazy spam in there..

Code:
2013-07-01 02:45:26 error Corrupted scene id_sno = 115976, snoAddr = 867581952
2013-07-01 02:45:26 still corrupted after trying for three times
2013-07-01 02:45:26 error Corrupted scene id_sno = 115976, snoAddr = 867581952
2013-07-01 02:45:26 still corrupted after trying for three times
2013-07-01 02:45:26 error Corrupted scene id_sno = 115976, snoAddr = 867581952
2013-07-01 02:45:26 still corrupted after trying for three times
2013-07-01 02:45:26 error Corrupted scene id_sno = 115976, snoAddr = 867581952
2013-07-01 02:45:26 still corrupted after trying for three times
2013-07-01 02:45:26 error Corrupted scene id_sno = 115976, snoAddr = 867581952
2013-07-01 02:45:26 still corrupted after trying for three times
2013-07-01 02:45:26 error Corrupted scene id_sno = 115976, snoAddr = 867581952
2013-07-01 02:45:26 still corrupted after trying for three times
2013-07-01 02:45:26 error Corrupted scene id_sno = 115976, snoAddr = 867581952
2013-07-01 02:45:26 still corrupted after trying for three times
2013-07-01 02:45:26 error Corrupted scene id_sno = 115976, snoAddr = 867581952
2013-07-01 02:45:26 still corrupted after trying for three times
2013-07-01 02:45:26 error Corrupted scene id_sno = 115976, snoAddr = 867581952
2013-07-01 02:45:26 still corrupted after trying for three times
2013-07-01 02:45:26 error Corrupted scene id_sno = 115976, snoAddr = 867581952
2013-07-01 02:45:26 still corrupted after trying for three times
2013-07-01 02:45:26 error Corrupted scene id_sno = 115976, snoAddr = 867581952
2013-07-01 02:45:26 still corrupted after trying for three times
2013-07-01 02:45:26 error Corrupted scene id_sno = 115976, snoAddr = 867581952
2013-07-01 02:45:26 still corrupted after trying for three times
2013-07-01 02:45:26 error Corrupted scene id_sno = 115976, snoAddr = 867581952
2013-07-01 02:45:26 still corrupted after trying for three times
2013-07-01 02:45:26 error Corrupted scene id_sno = 115976, snoAddr = 867581952
2013-07-01 02:45:26 still corrupted after trying for three times
Niga2K

Can you give us more information:

1) What Windows version and language you were using? 

2) Were you running on 32bits or 64bits window?

3) Were you using a VM?

4) What is the language of your Diablo 3 client ?

5) Which game server did you use?

6) Which class did you use?

7) What is the level of your class?

8) Which map did you use?

9) Which profile did you use?

10) What version of our bot your were using ?

11) Did you enable speedhack?

12) Any other information you think that may give us more clue to your problem?
(07-01-2013 03:56 AM)SuperBot Wrote: [ -> ]Niga2K

Can you give us more information:

1) What Windows version and language you were using? 

2) Were you running on 32bits or 64bits window?

3) Were you using a VM?

4) What is the language of your Diablo 3 client ?

5) Which game server did you use?

6) Which class did you use?

7) What is the level of your class?

8) Which map did you use?

9) Which profile did you use?

10) What version of our bot your were using ?

11) Did you enable speedhack?

12) Any other information you think that may give us more clue to your problem?

you remind me of "Tony" from thebuddyforum
he usually trolls the board 24/7 and pastes some generic response to anyones problem

anyway.. win 7 x64, english d3, no vm, speedhack enabled, newest botexploit, what's profile? if you mean map, it can be seen in the log. used a monk 60(100). server can be seen in log.
Hi nigga2k,
This could be due to a bug in version 0.9.110 that populates the log to a very large size.
This is fixed in the 0.9.115(just released), please download the latest version here:
http://botexploit.com/latest

If you still experience this problem please let us know. Thanks.
Reference URL's