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

[Release] Demonbuddy - Jolly monday build (#180)

Can you make DB stop blinking the window ?
Its a real mess when you have multiple widows and everything is blinking , you have to click each widndows for it to calm down.

We already have the process name selection its enough .

This blinking really piss me off .
 
This build seems to run pretty good. It's certainly been an improvement over the last one for me.
 
When the bot is "stuck", say surrounded by elites, and there is a weak non elite monster outside of the surround, the bot is indefinitely looping and trying to reach the unreachable non-elite (because it has less hp/weaker), causing it to just sit there and creating horrible lag, possibly due to indefinite amount of work done to trying to path to it.

Also, nav server bugs out sometimes trying to navigate into blocks of trees in Festering woods. Sometimes it would miss the orange portal to say, warrior's nest and will think that it has already clicked into it.
 
Last edited:
Nesox said:
Changelog .180
  • Added FollowerSpecial to ItemType
  • Added CraftingPlan item type.
  • Added support for the missing item types. Daibo, MightyWeapon, CraftingPage etc.
Click to expand...


  • There's definite improvements to item handling, but there's still some things that have been overlooked with the new item recognitions. Following lists displays the "Internalname" of the item in Diablo 3, followed by what DB thinks is the "ItemBaseType", and then what DB thinks is the "ItemType".


    [19:23:08.264 N] [GilesItemInternals 1.0] voodooMask_norm_base_04-160 | Misc | VoodooMask
    [19:23:08.264 N] [GilesItemInternals 1.0] voodooMask_norm_base_03-161 | Misc | VoodooMask
    [19:23:08.261 N] [GilesItemInternals 1.0] voodooMask_norm_base_04-155 | Misc | VoodooMask
    ^^ Witch Doctor voodoo masks considered as Misc, not Armor.

    [19:17:40.212 N] [GilesItemInternals 1.0] FollowerItem_Enchantress_norm_base_01-106 | Misc | Unknown
    [19:17:40.214 N] [GilesItemInternals 1.0] FollowerItem_Enchantress_norm_base_01-111 | Misc | Unknown
    [19:17:40.224 N] [GilesItemInternals 1.0] FollowerItem_Enchantress_norm_base_04-153 | Misc | Unknown
    [19:17:40.213 N] [GilesItemInternals 1.0] FollowerItem_Templar_norm_base_01-110 | Misc | Unknown
    [19:17:40.216 N] [GilesItemInternals 1.0] FollowerItem_Templar_norm_base_01-122 | Misc | Unknown
    [19:17:40.225 N] [GilesItemInternals 1.0] FollowerItem_Templar_norm_base_04-154 | Misc | Unknown
    [19:17:40.212 N] [GilesItemInternals 1.0] FollowerItem_Scoundrel_norm_base_02-109 | Misc | FollowerSpecial
    [19:17:40.214 N] [GilesItemInternals 1.0] FollowerItem_Scoundrel_norm_base_02-114 | Misc | FollowerSpecial
    [19:17:40.224 N] [GilesItemInternals 1.0] FollowerItem_Scoundrel_norm_base_04-150 | Misc | FollowerSpecial
    ^^ Only scoundrel follower items are recognised. Templar and enchantress follower items are not.

    [19:17:40.211 N] [GilesItemInternals 1.0] Wand_norm_base_07-105 | Misc | Wand
    [19:17:40.220 N] [GilesItemInternals 1.0] Wand_norm_base_07-138 | Misc | Wand
    [19:17:40.222 N] [GilesItemInternals 1.0] Wand_norm_base_06-146 | Misc | Wand
    ^^ Wizard Wands considered as Misc, not Weapons.

    [19:17:40.217 N] [GilesItemInternals 1.0] mightyWeapon_1H_norm_base_01-125 | Misc | MightyWeapon
    [19:17:40.219 N] [GilesItemInternals 1.0] mightyWeapon_1H_norm_base_04-133 | Misc | MightyWeapon
    [19:23:08.261 N] [GilesItemInternals 1.0] mightyWeapon_2H_norm_base_02-152 | Misc | MightyWeapon
    [19:23:08.262 N] [GilesItemInternals 1.0] mightyWeapon_2H_norm_base_01-157 | Misc | MightyWeapon
    ^^ Mighty 1h and 2h considered as Misc, not Weapon.

    [19:23:08.254 N] [GilesItemInternals 1.0] handXbow_norm_base_02-105 | Misc | HandCrossbow
    [19:23:08.257 N] [GilesItemInternals 1.0] handXbow_norm_base_02-111 | Misc | HandCrossbow
    ^^ Demon Hunter 1-hand crossbows considered as Misc, not Weapon.

    [19:23:08.260 N] [GilesItemInternals 1.0] combatStaff_norm_base_01-151 | Misc | Daibo
    [19:23:08.258 N] [GilesItemInternals 1.0] combatStaff_norm_base_03-113 | Misc | Daibo
    ^^ Monk Daibos considered as Misc, not Weapon.

    [19:23:08.253 N] [GilesItemInternals 1.0] Cloak_norm_base_04-103 | Misc | Cloak
    [19:23:08.259 N] [GilesItemInternals 1.0] Cloak_norm_base_02-115 | Misc | Cloak
    [19:23:08.262 N] [GilesItemInternals 1.0] Cloak_norm_base_03-156 | Misc | Cloak
    ^^ DH Cloaks considered as Misc, not Armor.

    [19:23:08.255 N] [GilesItemInternals 1.0] spiritStone_norm_base_03-109 | Misc | SpiritStone
    [19:23:08.263 N] [GilesItemInternals 1.0] spiritStone_norm_base_01-158 | Misc | SpiritStone
    [19:23:08.258 N] [GilesItemInternals 1.0] spiritStone_norm_base_02-114 | Misc | SpiritStone
    ^^ Monk Spirit Stones considered as Misc, not Armor.

    [19:23:08.257 N] [GilesItemInternals 1.0] BarbBelt_norm_base_04-112 | Misc | MightyBelt
    [19:23:08.255 N] [GilesItemInternals 1.0] BarbBelt_norm_base_03-107 | Misc | MightyBelt
    [19:23:08.259 N] [GilesItemInternals 1.0] BarbBelt_norm_base_02-120 | Misc | MightyBelt
    ^^ Barbarian mighty belts considered as Misc, not Armor.

    Just looks like you forgot about templar and enchantress follower items, and forgot the ItemBaseType of all the new items.
 
Nesox said:
Changelog .180
[*]Re-worked and re-enabled the stuck handler
Click to expand...

The built-in unstucker is, quite frankly, useless. It walks little to no distance at all, and will walk backwards and forwards over and over again without trying different movements - so if there is a "moveto" point around a corner (because the bot chased a monster around a corner and is now trying to get back), it will walk up against the barrier, and stay stuck there, moving from side to side over and over again, forever. If it tried to randomise it's movements a little, and tried to move increasing distances away, it would unstuck itself easily. Instead it picks one extremely short-distanced movement and repeats it forever.

It also needs a backup - if it fails to unstuck for X amount of attempts, it needs to try to teleport back to town, and then exit the game (as an option for people to enable) and restart the routine. Otherwise you can end up with 12 hours of repeated movements in exactly the same place which wouldn't be difficult to recognise as bot activity server-side.
 
Last edited:
Also "Death Handling" seems to (always/sometimes?) get stuck on the revive screen. Doesn't revive, and doesn't logout or restart the routine.
 
GilesSmith said:
There's definite improvements to item handling, but there's still some things that have been overlooked with the new item recognitions. Following lists displays the "Internalname" of the item in Diablo 3, followed by what DB thinks is the "ItemBaseType", and then what DB thinks is the "ItemType".


[19:23:08.264 N] [GilesItemInternals 1.0] voodooMask_norm_base_04-160 | Misc | VoodooMask
[19:23:08.264 N] [GilesItemInternals 1.0] voodooMask_norm_base_03-161 | Misc | VoodooMask
[19:23:08.261 N] [GilesItemInternals 1.0] voodooMask_norm_base_04-155 | Misc | VoodooMask
^^ Witch Doctor voodoo masks considered as Misc, not Armor.

[19:17:40.212 N] [GilesItemInternals 1.0] FollowerItem_Enchantress_norm_base_01-106 | Misc | Unknown
[19:17:40.214 N] [GilesItemInternals 1.0] FollowerItem_Enchantress_norm_base_01-111 | Misc | Unknown
[19:17:40.224 N] [GilesItemInternals 1.0] FollowerItem_Enchantress_norm_base_04-153 | Misc | Unknown
[19:17:40.213 N] [GilesItemInternals 1.0] FollowerItem_Templar_norm_base_01-110 | Misc | Unknown
[19:17:40.216 N] [GilesItemInternals 1.0] FollowerItem_Templar_norm_base_01-122 | Misc | Unknown
[19:17:40.225 N] [GilesItemInternals 1.0] FollowerItem_Templar_norm_base_04-154 | Misc | Unknown
[19:17:40.212 N] [GilesItemInternals 1.0] FollowerItem_Scoundrel_norm_base_02-109 | Misc | FollowerSpecial
[19:17:40.214 N] [GilesItemInternals 1.0] FollowerItem_Scoundrel_norm_base_02-114 | Misc | FollowerSpecial
[19:17:40.224 N] [GilesItemInternals 1.0] FollowerItem_Scoundrel_norm_base_04-150 | Misc | FollowerSpecial
^^ Only scoundrel follower items are recognised. Templar and enchantress follower items are not.

[19:17:40.211 N] [GilesItemInternals 1.0] Wand_norm_base_07-105 | Misc | Wand
[19:17:40.220 N] [GilesItemInternals 1.0] Wand_norm_base_07-138 | Misc | Wand
[19:17:40.222 N] [GilesItemInternals 1.0] Wand_norm_base_06-146 | Misc | Wand
^^ Wizard Wands considered as Misc, not Weapons.

[19:17:40.217 N] [GilesItemInternals 1.0] mightyWeapon_1H_norm_base_01-125 | Misc | MightyWeapon
[19:17:40.219 N] [GilesItemInternals 1.0] mightyWeapon_1H_norm_base_04-133 | Misc | MightyWeapon
[19:23:08.261 N] [GilesItemInternals 1.0] mightyWeapon_2H_norm_base_02-152 | Misc | MightyWeapon
[19:23:08.262 N] [GilesItemInternals 1.0] mightyWeapon_2H_norm_base_01-157 | Misc | MightyWeapon
^^ Mighty 1h and 2h considered as Misc, not Weapon.

[19:23:08.254 N] [GilesItemInternals 1.0] handXbow_norm_base_02-105 | Misc | HandCrossbow
[19:23:08.257 N] [GilesItemInternals 1.0] handXbow_norm_base_02-111 | Misc | HandCrossbow
^^ Demon Hunter 1-hand crossbows considered as Misc, not Weapon.

[19:23:08.260 N] [GilesItemInternals 1.0] combatStaff_norm_base_01-151 | Misc | Daibo
[19:23:08.258 N] [GilesItemInternals 1.0] combatStaff_norm_base_03-113 | Misc | Daibo
^^ Monk Daibos considered as Misc, not Weapon.

[19:23:08.253 N] [GilesItemInternals 1.0] Cloak_norm_base_04-103 | Misc | Cloak
[19:23:08.259 N] [GilesItemInternals 1.0] Cloak_norm_base_02-115 | Misc | Cloak
[19:23:08.262 N] [GilesItemInternals 1.0] Cloak_norm_base_03-156 | Misc | Cloak
^^ DH Cloaks considered as Misc, not Armor.

[19:23:08.255 N] [GilesItemInternals 1.0] spiritStone_norm_base_03-109 | Misc | SpiritStone
[19:23:08.263 N] [GilesItemInternals 1.0] spiritStone_norm_base_01-158 | Misc | SpiritStone
[19:23:08.258 N] [GilesItemInternals 1.0] spiritStone_norm_base_02-114 | Misc | SpiritStone
^^ Monk Spirit Stones considered as Misc, not Armor.

[19:23:08.257 N] [GilesItemInternals 1.0] BarbBelt_norm_base_04-112 | Misc | MightyBelt
[19:23:08.255 N] [GilesItemInternals 1.0] BarbBelt_norm_base_03-107 | Misc | MightyBelt
[19:23:08.259 N] [GilesItemInternals 1.0] BarbBelt_norm_base_02-120 | Misc | MightyBelt
^^ Barbarian mighty belts considered as Misc, not Armor.

Just looks like you forgot about templar and enchantress follower items, and forgot the ItemBaseType of all the new items.
Click to expand...

Thanks, I was thinking I forgot something, but couldn't put my finger on it.

I've fixed all of them. (I didn't realize that Blizzard flagged each follower token with something different, they're all supported now.)
 
Last edited:
Bot suddenly stopped working, it no longer attacks :-( anyone know what's up?
 
dunno, there must be a bug or something.
i'm running

2plugins
Inrego Sarkoth Farmer r50
NotificationOkClick

sometimes my guy just runs to the dank cellar and stands there to die.
respawns and stands there to die.

[15:54:04.485 Q] [SarkothFarmer] Cellar found in 341/657 games, that's 51.9%.
[15:54:04.485 Q] [SarkothFarmer] This run with cellar took 69.2 seconds.
[15:54:04.485 Q] [SarkothFarmer] Run with cellar - Avg: 23.7s Min: 15.7s Max 851.3s.
[15:54:04.485 Q] [SarkothFarmer] Run without cellar - Avg: 9.4s Min: 8.6s Max 26.1s.

i don't even know why it ran for 851 seconds. i thought it has a 50 second max timer to leave the game.
im at 148k GPH w/ 92 deaths per hour.

ever heard of a bot that loses you gold. well, u just saw one right here.
 
Hellobada24 said:
dunno, there must be a bug or something.
i'm running

2plugins
Inrego Sarkoth Farmer r50
NotificationOkClick

sometimes my guy just runs to the dank cellar and stands there to die.
respawns and stands there to die.

[15:54:04.485 Q] [SarkothFarmer] Cellar found in 341/657 games, that's 51.9%.
[15:54:04.485 Q] [SarkothFarmer] This run with cellar took 69.2 seconds.
[15:54:04.485 Q] [SarkothFarmer] Run with cellar - Avg: 23.7s Min: 15.7s Max 851.3s.
[15:54:04.485 Q] [SarkothFarmer] Run without cellar - Avg: 9.4s Min: 8.6s Max 26.1s.

i don't even know why it ran for 851 seconds. i thought it has a 50 second max timer to leave the game.
im at 148k GPH w/ 92 deaths per hour.

ever heard of a bot that loses you gold. well, u just saw one right here.
Click to expand...

with this version you don't need NotificationOkClick.
maybe it goes in conflict with something else.

I'm playing with monk, 0 death since this morning (only inrego sarkoth plugin and only setted with "15" pickupgold, I didn't changed anything else).

what class are you running?
 
CCCComboBreaker said:
with this version you don't need NotificationOkClick.
maybe it goes in conflict with something else.

I'm playing with monk, 0 death since this morning (only inrego sarkoth plugin and only setted with "15" pickupgold, I didn't changed anything else).

what class are you running?
Click to expand...

hmmm i came home from the store to find one of my bots with a join error message that it didnt click off. So ive turned Okclicker back on.
 
Jackie1234 said:
hmmm i came home from the store to find one of my bots with a join error message that it didnt click off. So ive turned Okclicker back on.
Click to expand...

Yep. the built in clicker has never worked properly for me. always use notifcationclicker
 
gWT5i.jpg


Here's an example of where the built-in unstucker is rendered not just useless, but dangerous. There is a moveto waypoint on the green dot. However a shrine, and sometimes a monster, spawns at the character's current location, and so the character runs down the stairs towards the monster/shrine first. After dealing with the monster/shrine, it tries to go back to that moveto waypoint - but it gets stuck where you see it now. DB's built in unstucker simply runs backwards and forwards over that green-line, over and over, forever - never unstucking - it can do this for hours. If I manually run about half way up the stairs, the bot continues ok.

It seems like there is no path-finding at all in the unstucker. It simply tries to run in a straight line, which somewhat defeats the point of an unstucker?
 
GilesSmith said:
Here's an example of where the built-in unstucker is rendered not just useless, but dangerous. There is a moveto waypoint on the green dot. However a shrine, and sometimes a monster, spawns at the character's current location, and so the character runs down the stairs towards the monster/shrine first. After dealing with the monster/shrine, it tries to go back to that moveto waypoint - but it gets stuck where you see it now. DB's built in unstucker simply runs backwards and forwards over that green-line, over and over, forever - never unstucking - it can do this for hours. If I manually run about half way up the stairs, the bot continues ok.

It seems like there is no path-finding at all in the unstucker. It simply tries to run in a straight line, which somewhat defeats the point of an unstucker?
Click to expand...

That's what I've been telling them since .160.. The unstucker does not work properly. That's why it was disabled in prior releases, so that we could at least use the Unstucker plugin that would make you leave the game .. with the current built in unstucker you can't even use the plugin version, because it never stands still long enough for the plugin to kick in.
 
also is anyone getting stuck at the stash. My guy is getting stuck in the corner of the stash before opening it.
 
Loot rules like this no longer working for me.



<ItemRule> <StatRules>
<Rule quality="Magic1" stat="level" minValue="61"/>
</StatRules>
</ItemRule>
Click to expand...
 
Yes, I'm also getting stuck at the stash box in Sarkath runs. He stands between the portal and the stash box and thats the end until I manually move him out some. I just went back to .173 till this one also gets fixed.
 
You must log in or register to reply here.
Back
Top