What's new
  • Visit Rebornbuddy
  • Visit Resources
  • Visit API Documentation
  • Visit Downloads
  • Visit Portal
  • Visit Panda Profiles
  • Visit LLamamMagic

I think all the crashing is on blizzards end. I would move all gear.

dreams81

Member
Joined
Aug 5, 2012
Messages
194
Reaction score
0
I apologize for posting something this stupid.

Learned my lesson.
 
Last edited:
a2 inferno champion hunting w/ death support

giles combat replacer 0.4.1.2
giles stash replacer 1.9.7.2
giles world object handler 1.6
profile switcher

if you want your bot to work, dont be lazy. Listen to the authors of the profiles/plugins and wait for updates
 
Even if the it doesnt look like your plugins were updated, re-dl the files anyway. just copy the actual plugin files and keep your config files the same. Fixed all my crashes. The only thing that seems to be happening now is the after a grid reset the bot sometimes does not resume which I think is a bot error.
 
Fresh install DB only one plugin RadsProfileManager and DB crash every ~15 minutes :/ Yesterday full stable.
 
a2 inferno champion hunting w/ death support

giles combat replacer 0.4.1.2
giles stash replacer 1.9.7.2
giles world object handler 1.6
profile switcher

if you want your bot to work, dont be lazy. Listen to the authors of the profiles/plugins and wait for updates


setup just like you so far so good.

i take that back crash 5mins into run.
 
Last edited:
a2 inferno champion hunting w/ death support

giles combat replacer 0.4.1.2
giles stash replacer 1.9.7.2
giles world object handler 1.6
profile switcher

if you want your bot to work, dont be lazy. Listen to the authors of the profiles/plugins and wait for updates

also which profile switcher are u using?
 
Nothing gets sent to Blizz unless you tell it to. It asks you when D3 crashes. Just click cancel.
 
Nothing gets sent to Blizz unless you tell it to. It asks you when D3 crashes. Just click cancel.


New build.

Changelog .217

XP shrines are now enabled again to work with the new Paragon level system.
Very big memory issue fixed. ( should no longer consume up to 1Gb after a few hours )
Bot logs are now separated even further, using the current bot's process ID. This alleviates some file I/O read/write lock issues, and should increase performance a bit on heavy logging.
File log level set back to diagnostics.

new build out.

also to all the tin foil comments you guys owned me.
 
Back
Top