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

[Plugin] Giles World Object Handler

Giles is 30 the max that DB can detect a chest or is that just the max to keep on the path or ?
I was asking if it could be increased. I know distance to the eye is not game distance but he opens chest when they are close but he sure passes up a lot of them.
They are visible on screen, I don't know game distance very well.
 
Last edited:
[10:00:08.307 D] Generating path to S-Highlands #11 - <2478.01, 4467.682, 0.1>
[10:00:08.313 D] Raycast path generated.
[10:00:08.313 D] Generated path to <2478.01, 4467.682, 0.1> (S-Highlands #11) with 1 hops.
[10:00:08.746 D] [WorldObjectHandler] Blacklisting a container [LootType2_Adventurer_B_Corpse_02-21187] because we never want to open it.
[10:00:08.746 V] Blacklisting C8AB0073 for 00:10:00
[10:00:10.144 N] Closing error dialog
[10:00:10.176 D] [BotEvents] EventChecker  threw exception Object reference not set to an instance of an object. in check

Just got, fresh install, root patch, last plugins (only yours actually combat/world/stash). Is it still db offset error?
 
arielmz said:
[10:00:08.307 D] Generating path to S-Highlands #11 - <2478.01, 4467.682, 0.1>
[10:00:08.313 D] Raycast path generated.
[10:00:08.313 D] Generated path to <2478.01, 4467.682, 0.1> (S-Highlands #11) with 1 hops.
[10:00:08.746 D] [WorldObjectHandler] Blacklisting a container [LootType2_Adventurer_B_Corpse_02-21187] because we never want to open it.
[10:00:08.746 V] Blacklisting C8AB0073 for 00:10:00
[10:00:10.144 N] Closing error dialog
[10:00:10.176 D] [BotEvents] EventChecker threw exception Object reference not set to an instance of an object. in check

Just got, fresh install, root patch, last plugins (only yours actually combat/world/stash). Is it still db offset error?
Click to expand...

That just looks like a random DB error - nothing to do with world object handler. Just DB internals I believe.

The newest DemonBuddy's (all three new ones for Diablo patch 1.04) seem to be causing a lot of memory read errors all over the place - both in core DB functions and plugins.
 
Devilize said:
i seem to get stuck at every log i run into in A1 with this
Click to expand...

Try setting the destructible attack range higher in the config - what do you currently have your settings at? Also make sure you have a spammable attack on your LMB, since that's what DemonBuddy uses to attack stuff like that.
 
GilesSmith said:
Try setting the destructible attack range higher in the config - what do you currently have your settings at? Also make sure you have a spammable attack on your LMB, since that's what DemonBuddy uses to attack stuff like that.
Click to expand...

it was at 7, and LMB is frenzy like most barbs.

i made it 9, ill let you know if i catch it do that again... but 7 was the default so idk why that would be an issue
 
Devilize said:
it was at 7, and LMB is frenzy like most barbs.

i made it 9, ill let you know if i catch it do that again... but 7 was the default so idk why that would be an issue
Click to expand...

happens with 9 and 11... not sure what to do?
 
Devilize said:
happens with 9 and 11... not sure what to do?
Click to expand...

Try 30? :P Just for crazy test. If it still gets stuck on a log in a particular place then you can rule out world object handler as the issue, and rule in DemonBuddy not detecting it needs to "attack" a destructible.
 
hmm im noticing the minimum gold pile pickup is no longer working, i set it down to 50 and it never goes to grab piles even at 1k piles, had DB loot radius default (60) then raised it to 80 and still doesnt run to get it. my PR itself is 54 so it should only take a few steps. In DB 204, was working flawlessly.
 
v1.7 uploaded:
-- Few new items added to the blacklist.
-- Now removed minimum gold stack option - this is now set by either your DB Settings & Loot Rules, or Giles Stash Replacer 1.9.9+
 
I want to report a bug with the version 1.7, it is blacklisting loot (for example iLVL 61+ rares) because of unknown object type.

See screenshot:
blacklistingloot.webp
snip from Dump RActors:
[00:11:24.437 N] [2EC410A0] Type: Player Name: Barbarian_Male-5 ActorSNO: 3301, Distance: 0
[00:11:24.453 N] [2EC480D8] Type: Item Name: Gloves_norm_base_flippy-7724 ActorSNO: 4264
[00:11:24.470 N] [2EC5C0E0] Type: Item Name: Bracers_norm_base_06-7728 ActorSNO: 56328
[00:11:24.486 N] [2EC48928] Type: Item Name: shoulderPads_norm_base_flippy-7737 ActorSNO: 5288
[00:11:24.503 N] [2EC47460] Type: Unit Name: Hireling_Enchantress-39 ActorSNO: 4482, Distance: 9.216996
[00:11:24.519 N] [2EC52718] Type: Unit Name: FallenGrunt_C-5073 ActorSNO: 4084, Distance: 9.958313
[00:11:24.536 N] [2EC52B40] Type: Unit Name: FallenGrunt_C-5075 ActorSNO: 4084, Distance: 10.04665
 
lypnn said:
I want to report a bug with the version 1.7, it is blacklisting loot (for example iLVL 61+ rares) because of unknown object type.

See screenshot:
View attachment 52730
snip from Dump RActors:
[00:11:24.437 N] [2EC410A0] Type: Player Name: Barbarian_Male-5 ActorSNO: 3301, Distance: 0
[00:11:24.453 N] [2EC480D8] Type: Item Name: Gloves_norm_base_flippy-7724 ActorSNO: 4264
[00:11:24.470 N] [2EC5C0E0] Type: Item Name: Bracers_norm_base_06-7728 ActorSNO: 56328
[00:11:24.486 N] [2EC48928] Type: Item Name: shoulderPads_norm_base_flippy-7737 ActorSNO: 5288
[00:11:24.503 N] [2EC47460] Type: Unit Name: Hireling_Enchantress-39 ActorSNO: 4482, Distance: 9.216996
[00:11:24.519 N] [2EC52718] Type: Unit Name: FallenGrunt_C-5073 ActorSNO: 4084, Distance: 9.958313
[00:11:24.536 N] [2EC52B40] Type: Unit Name: FallenGrunt_C-5075 ActorSNO: 4084, Distance: 10.04665
Click to expand...


wow we must be loosing a lot of items this way
 
You must log in or register to reply here.
Back
Top