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

[Release] Demonbuddy - Friday partay build (#176)

Status
Not open for further replies.
siferxxx said:
Wow thanks, still would be awesome with random dungeon. I just want a little info/update thats all.
Click to expand...

I think today if you make stupid posts like this all day. I have a new friend.

They have already told you and everyone else, asking every 6 to 12 hours about random dungeons... IT WILL NOT SPEED IT UP
 
Last edited:
siferxxx said:
Days hours weeks progress
Click to expand...


Let me put it like this. When it is done or close, they will post information. Until then try to hold your break until they respond with a release date.


You do realize that A LOT of other things had to be working correctly before the Dev team could really focus on this?

We need a stable release before they start trying to add in benefits like this.
 
Last edited:
Nesox said:
It's done when it's done.
Click to expand...
Thanks for the changes on the stuck timer. It allows other plugins to be used in place for somethings.

Also pathing for the most part seems to be improved as well.

.176 was a pretty decent release.
 
OK. I have a question. Why is nagivation logic / behavior seemingly changing drastically each release? When 173 came out I had to rework zultun kulle to get it to not get stuck trying to get to the soulstone after killing ZK.. No biggy, profile reworked still worked. Looked a little wierd cause the workaround is a new waypoint up near the top of the map so it kickstarts it in the right direction instead of forcible trying to go right through the center (where theres no walkway). But it worked. Now 176 comes out and suddenly after the second cutscene the bot wants to go back to the middle where the stone was. and just sit there.... forever. I've reworked it (even more this time) shifting stuff around and adding / increasing wait timers and it's sort of working... Still trying to go to the middle but figures it out after some backtracking.... This is pretty strange that each release profiles that worked 100% for days prior are breaking out of nowhere. (Has nothing to do with removed tags of 171).

i'm running again now so all is well. just curious. maybe there is a simple explanation about something internally thats been tinkered with with the bot core.
 
It is possible to avoid for DB closing Diablo 3 window when used with "runcount" ?
 
Where can I find previous version? Cause this build stucks during running to salvage?
 
Please help fresh installed D3 after that bot won't work.
thank you.

***got it to work nvm.
 
Last edited:
When will we see something that makes the bot avoiding fires lasers and so? :D
 
swolbyn said:
OK. I have a question. Why is nagivation logic / behavior seemingly changing drastically each release? When 173 came out I had to rework zultun kulle to get it to not get stuck trying to get to the soulstone after killing ZK.. No biggy, profile reworked still worked. Looked a little wierd cause the workaround is a new waypoint up near the top of the map so it kickstarts it in the right direction instead of forcible trying to go right through the center (where theres no walkway). But it worked. Now 176 comes out and suddenly after the second cutscene the bot wants to go back to the middle where the stone was. and just sit there.... forever. I've reworked it (even more this time) shifting stuff around and adding / increasing wait timers and it's sort of working... Still trying to go to the middle but figures it out after some backtracking.... This is pretty strange that each release profiles that worked 100% for days prior are breaking out of nowhere. (Has nothing to do with removed tags of 171).

i'm running again now so all is well. just curious. maybe there is a simple explanation about something internally thats been tinkered with with the bot core.
Click to expand...

this is just a guess but I assume random dungeons and other things are going to require constant work in the navigation/movement code until they are working.
 
DB seems to have a hard time hitting moving targets as a Melee class, it stutter moves towards it (because player speed is faster than mob) but never hits it.

This causes a lot of rubberbanding issues and causes DB to abandon the mob target due to kill radius.

edit:
also, if the character is blocked by other mobs and DB chooses another mob to attack, it will stay there and take hits until it dies.
 
Last edited:
alot of probs today yesterday it run smooth and today i cant get sarkoth running , i guess its waiting for a update ^^
 
Status
Not open for further replies.
Back
Top