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

[Plugin] Giles World Object Handler

Giles would adding using health pools when under a certain health be beyond the scope of this plugin?
 
Giles would adding using health pools when under a certain health be beyond the scope of this plugin?

Yes, this would have to be something Belphegor introduced, similar to their introduction of going for health-globes. This is because I'm trying not to put any actual actions (eg clicking things, moving places) into this or the monster priority changer, as they are meant to just be "target providers" that provide a list of either monsters, or objects, from Diablo 3 into DemonBuddy for DB/Combat routine/stash replacer to then do the actual actions to. I think it's best not to blur those lines!
 
Yes, this would have to be something Belphegor introduced, similar to their introduction of going for health-globes. This is because I'm trying not to put any actual actions (eg clicking things, moving places) into this or the monster priority changer, as they are meant to just be "target providers" that provide a list of either monsters, or objects, from Diablo 3 into DemonBuddy for DB/Combat routine/stash replacer to then do the actual actions to. I think it's best not to blur those lines!

Nuok already has something experimental ready for the next release :)
 
v1.5.2 uploaded:
-- Many more objects added to the blacklist and whitelist, including many destructibles in act 1 dungeons that gained no benefit for destroying (eg chairs etc.).
-- Removed the "Ignore Exp Shrine" option - now automatically ignores any exp shrines for level 60 characters.
-- Various minor optimizations/tweaks throughout.
 
When using your world object handler, should we enable or disable "DestroyEnvironment" in belpgegor character settings? Or does it not matter?
 
When using your world object handler, should we enable or disable "DestroyEnvironment" in belpgegor character settings? Or does it not matter?

You should enable destroying environment in Belphegor - as far as I understand it, Belphegor simply decided whether or not to actually attack whatever objects it receives from the object provider. My world object handler decides what those targets are that it receives (and is designed around doing an intelligent job of deciding what to attack, what not to attack, and at what range). I would imagine that setting to disable destroying is only useful for people that don't use my plugin, and is just a simple "all-or-nothing" option :D
 
Hey Giles, i just wanted to tell you thanks for sharing your plugins with us. For someone who proclaims not having done any of this before, i sure am amazed at how quickly you've caught on. They are amazing. Again, truly appreciate your work. :)
 
should I click or unlick the box if i wanted to use your filtered loot rule with yr replacer plugin
 
should I click or unlick the box if i wanted to use your filtered loot rule with yr replacer plugin

Tick it - it will disable DB from trying to match your .xml loot-rules files within the "loot targeting provider" (which is what world object handler replaces). While this isn't strictly necessary if you use the loot rules from stash replacer , it can help reduce the chance of problems.

I personally always recommend you use BOTH world object handler to disable filter *AND* use the loot-rules atatched to post #1 of stash replacer - in theory you only need to do one or the other... but both definitely won't do any harm! :D Just make sure you have "Use Giles Filters" ticked in Stash Replacer if you do either of these things, otherwise your bot will pick everything up (literally everything!) :D
 
ugh new db version broke the plugin as well as your other plugins =(
 
ugh new db version broke the plugin as well as your other plugins =(
Yeah... Updates plugins please! :I

Are you guys sure there is a problem? I'm running with new DB and my plugins absolutely fine. I only have my three plugins, and of course I did what everybody should always do - which is a fresh clean install of DB in a new empty folder when updating, never rely on the auto-updater or copying files into old folder. This does mean plugins will go to default settings again if you don't back up the plugin config files from the "settings" folder - so be sure to check the plugin settings when you run it again.

What problems have you actually encountered with the new version? I need details because at the moment, all seems to be running just fine (but I have only been testing the new Db out for maybe 15 minutes so far).
 
Compiled/worked fine for me as well Giles.
 
I did clean install with new folder...will try again and let you know
 
ok yours seem to be showing up. Looks like its db enhancements that is causing the issue and I had to load the profile before yours would show up in the plugins list.
 
actually looks like db enhancements was killing all other plugins to load as well. So removed db enhancements and all other plugins I was using loaded. Just had to do an edit on the profile I was using so db enhancements wasnt needed for now
 
Back
Top