What's new
By:
  • Visit Rebornbuddy
  • Visit Panda Profiles
  • Visit LLamamMagic
  • Visit Resources
  • Visit Downloads
  • Visit Portal

[Beta] Demonbuddy daily beta builds

Status
Not open for further replies.
bombastic said:
#52 is the first afk'able version pos 1.0.5.

No random crashes, bot don't stop itself. First time botting for 6+ hours without a single intervention.

The only remain problem is the inactivity timer being incompatible with Rads, but this is a work for ciggarc team (or use my fixed version I posted in beta thread).

Good job so far.
Click to expand...

which version of rads are u runnig?
 
was that teleport idea implemented? The one where you would move within 10 seconds because I saw one of my guys stuck in the failed animation trying to teleport home for 20 seconds or so without trying to move. Just wondering if that was ever implemented into this version.
 
why does bot still missing about 5-10% of loot? it that giles plugin problems, or DB memory reading issues?
 
Xelation said:
what's your giles set at and what type of items do you see it missing?
Click to expand...
Actually it's tottaly random I've also noticed that after last diablo patch. It could be anything Legendary or rare any ilvl, and sometimes bot picks up WHITE and blue random items.
 
build 52 is fine and all, but the new patch 1.05a is coming out to fuck everything up again :D
 
Erson said:
Actually it's tottaly random I've also noticed that after last diablo patch. It could be anything Legendary or rare any ilvl, and sometimes bot picks up WHITE and blue random items.
Click to expand...

PEBKAC
Your loot rules are screwed or your running a bad combo of filters either way not a DB issue
 
Again same problem after a few hours with latest beta build (#52): bot idle after path request, until inactivity timer kick in, then exit game, do not create a new game...

I tried different settings for DB and Rads inactivity timers (using only DB's, then rads', then only DB with rads' "fixed" 1.5.1 version) , but it doesn't solve the problem...

Here is my latest log:

View attachment 13872 2012-10-25 09.44.zip


I have also posted a full log for the same problem with non beta release #281 in the support section.

I must add that i never had this problem 7-10 days ago, but multiple times a day since release #279 i think.
 
Last edited:
shagar said:
Again same problem after a few hours with latest beta build (#52): bot idle after path request, until inactivity timer kick in, then exit game, do not create a new game...

I tried different settings for DB and Rads inactivity timers (using only DB's, then rads', then only DB with rads' "fixed" 1.5.1 version) , but it doesn't solve the problem...


Here is my latest log:

View attachment 62576


I have also posted a full log for the same problem with non beta release #281 in the support section.

I must add that i never had this problem 7-10 days ago, but multiple times a day since release #279 i think.
Click to expand...
Same issue here .. sits in menus
 
new offsets for new patch.. i'm sure nesox is onto it allready
 
shagar said:
Again same problem after a few hours with latest beta build (#52): bot idle after path request, until inactivity timer kick in, then exit game, do not create a new game...

I tried different settings for DB and Rads inactivity timers (using only DB's, then rads', then only DB with rads' "fixed" 1.5.1 version) , but it doesn't solve the problem...

Here is my latest log:

View attachment 62576


I have also posted a full log for the same problem with non beta release #281 in the support section.

I must add that i never had this problem 7-10 days ago, but multiple times a day since release #279 i think.
Click to expand...


Okay I had this problem with only 1 of my scripts and i figured out what is causing it, if you have more than like 150-200 yards/meters/demonbuddy distance between two nodes the bot wont properly path between them, i just added in a extra node between the exact spot it got hung up and the next travel node it fixed this problem

I've been able to run TWO bots 18+ hrs on build #52 without them stopping once with only checking the DB logs every 3-4 hours and that's after i fixed my one profile.

However since the 1.05 to 1.05a I've been getting this "Could not read from bytes 00000000 [299]" Error Mentioned above and cant Connect to DB anymore
 
Last edited:
Changelog

  • Updated for 1.0.5.12811
  • Added most of the aspect ghosts to the ignore targets list in the combat targeting.
  • AdvanceConversation tag added, let's just advance in a conversation. example: when talking to Tyrael before doing iskatu, <AdvanceConversation questId="1" numTimes="5" />
  • When using the ExploreArea tag the bot should no longer get stuck trying to move to nodes it can't navigate to, this is hopefully the last issue regarding stuck issues with the dungeon explorer.
 
Last edited:
Status
Not open for further replies.
Back
Top