[Plugin] Giles Monster Priority Changer

[Moose]

1.4.2 seems to be a lot faster, granted the last version i tested was 1.1 but it seems to do the trick, thanks giles.

 

[griovejas]

Any plans of making this work for Act2/Act3?

 

[tesslerc]

trying out 1.4.2 looks good.
had one problem b4 he was surrounded by melee chars and had a tree monster in his attack radius, he didnt attack the melee as he was top prioritizing the tree but until the tree got into melee range and he can attack it - it did nothing!

 

[GilesSmith]

Any plans of making this work for Act2/Act3?

It already will work and should improve things for ALL acts - but for custom, specific monsters that need extra priority from those acts, I'll need some details (location/name/description) so I can go track them down and get their internal names to add to any priority lists (eg other creatures that should have priority). But no reason you can't start using it now and see an improvement!

trying out 1.4.2 looks good.
had one problem b4 he was surrounded by melee chars and had a tree monster in his attack radius, he didnt attack the melee as he was top prioritizing the tree but until the tree got into melee range and he can attack it - it did nothing!

Cheers, I'm trying to improve this in newer versions by adding checks if it detects you are surrounded by more than XX mobs, in which case prioritize on clearing those out of the way first if you don't have ranged abilities. I'll have to do a little more tweaking to let it over-come those "priority mobs" like trees when surrounded!

happens with second instance of DB.

How are you launching the 2nd instance? I just have one copy of DB in one folder, and launch the same DB client one at a time for each D3 client. Are you using some sort of auto-laoder (like batch restarter) that might mess with pathing? Was the path listed in the error "C:\Users\x\Desktop\DB\Plugins\GilesMonsterPriorityChanger\GilesMonsterPriority.xaml" correct? (does that file exist in that folder?). Failing all else, could have just been because it tried to load 2 copies too quickly, and one copy had "locked" the file briefly while the other DB copy was trying to also read from it. If that's the case I can look into some error catching for this!

 

[griovejas]

It already will work and should improve things for ALL acts - but for custom, specific monsters that need extra priority from those acts, I'll need some details (location/name/description) so I can go track them down and get their internal names to add to any priority lists (eg other creatures that should have priority). But no reason you can't start using it now and see an improvement!

I just launched it in Act2 and all the bot does is stand in town and spam Mouse1 ability (Frenzy in my case). No other plugins available, basic profile. Once I turn off this plugin, the bot stops spamming Mouse1 and starts moving.
Try it yourself, Act2-Quest8-1

 

[GilesSmith]

1.4.3 attached. Should give a bit more priority to close-up mobs if you have no ranged abilities and are surrounded by mobs at close range.

Should also fix the attempted attacking of Zultan Kulle ghost in Act 2 (let me know if there's other places it gets stuck trying to attack invisible things, will probably be quest NPC markers DemonBuddy is returning and need blacklisting).

I just launched it in Act2 and all the bot does is stand in town and spam Mouse1 ability (Frenzy in my case). No other plugins available, basic profile. Once I turn off this plugin, the bot stops spamming Mouse1 and starts moving.
Try it yourself, Act2-Quest8-1

 

[tesslerc]

1.4.3 is amazing!
just watched it run and its attacking super fast, no stucks nothing at all.

 

[Hajkfas]

How are you launching the 2nd instance? I just have one copy of DB in one folder, and launch the same DB client one at a time for each D3 client. Are you using some sort of auto-laoder (like batch restarter) that might mess with pathing? Was the path listed in the error "C:\Users\x\Desktop\DB\Plugins\GilesMonsterPriorityChanger\GilesMonsterPriority.xaml" correct? (does that file exist in that folder?). Failing all else, could have just been because it tried to load 2 copies too quickly, and one copy had "locked" the file briefly while the other DB copy was trying to also read from it. If that's the case I can look into some error catching for this!

Sorry, user error; didn't realize there's a new XAML file with the newer versions

Have you noticed that the newer versions of db/belph seems to "delay" when surronded by mobs and it blocks/dodges attacks? Almost as if it has really low "faster hit recovery" in D2 terms.
Also happens after using a different skill than the one it was spamming.

 

[GilesSmith]

Have you noticed that the newer versions of db seems to "delay" when surronded by mobs and it blocks/dodges attacks? Almost as if it has really low "faster hit recovery" in D2 terms.

DB definitely has various issues when your character is surrounded by mobs - I think something in DB is trying to run path-finding, and failing, and getting a bit stuck, I'm not entirely certain yet. I'm working on trying to correct this, at least for characters that can't attack at range (eg monks for the most part and barbarians without leap) - try that test version 1.4.3 two or three posts up (and you still need the XAML! ) and let me know if you feel that improves speed when mobs are at close range a bit?

 

[xzhenx]

Tested it, seems an improvement over the past versions, but I can never get close to equal efficiency as controlling the hero myself. Might be limitations with DB like you said.

At times I can't even figure out if the bot's intention is to ignore/hit/move, it seems to want to do a little bit of everything :/

 

[GilesSmith]

Tested it, seems an improvement over the past versions, but I can never get close to equal efficiency as controlling the hero myself. Might be limitations with DB like you said.
At times I can't even figure out if the bot's intention is to ignore/hit/move, it seems to want to do a little bit of everything :/

Hah, don't try to compare it to human ability! I just don't think it has the capacity to do the equivalent of holding LMB down - I think it's always "check targets" "do 1 ability" "check targets" "do 1 ability" and rinse-repeat until there are no more targets. My plugin changes (improves!?) DemonBuddy's default check-targets section. And it's down to the combat routine (eg Belphegor test versions with lots of additions) to change (also improve!?) the "do 1 ability" bit in picking the abilities etc. - no idea if they will be able to do something like hold LMB for 2 attacks in a row for certain abilities, if they can it'd really speed things up.

Anyway as long as monks find that attacking with the latest test version of my plugin is at least AS FAST AS default DemonBuddy, if not faster, then I'm happy. There definitely shouldn't have been any slow-down! I know barbarians-with-leap have found it actually speeds DB up with lots of targets, as well as provides more intelligent target decision making.

I'll be updating the main plugin tomorrow with a version that has the potential to improve speeds further still when you are surrounded by a lot of melee mobs, too, so watch out for full release 1.4.4 of this plugin sometime tomorrow!

 

[xzhenx]

Yup, that's what it feels like

1) Perform 1 attack
2) Check situations and parameters
3) Perform 1 attack
4) Check situations and parameters

I checked my processor load during botting and it ain't anywhere close to max, in fact, it even looks pretty relaxed. Think this is an issue with the default DB program :/

 

[GilesSmith]

v1.4.4 uploaded:
-- Various optimizations and tweaks to help speed up target selection for melee characters, particularly with lots of targets.
-- Further optimizations and more intelligent decision making if a character with no range abilities is surrounded by mobs.
-- Melee characters can now sometimes ignore point-blank monsters in favor of nearby summoners/priority monsters, as long as they aren't heavily surrounded.


Important note to people that use any DemonBuddy command-line loaders, eg batch-restarters
DemonBuddy currently starts running a routine before all plugins have been loaded into memory if loaded from command-line. This can cause random problems, bugs, and outright failures from any complex plugins that take more than a millisecond to load or plugins that need to load from external data-files (config files & windows). Please avoid using any command-line DemonBuddy launchers if you have many plugins or are using any of my plugins, until DemonBuddy updates to either allow a forced-delay in command-line before starting, or has safety checks to ensure all plugins are compiled and loaded before it can start a routine.

 

[xzhenx]

Can this be coded in a manner such that the detection range only covers the path in front of your hero is heading to? E.g will ignore white mobs approaching you from the side as long as you have enough room to manoeuvre forward.

 

[GilesSmith]

Can this be coded in a manner such that the detection range only covers the path in front of your hero is heading to? E.g will ignore white mobs approaching you from the side as long as you have enough room to manoeuvre forward.

At the moment I can't see any good way of doing this without a huge optimization hit. It would probably depend on DemonBuddy providing some better API functionality, which they may do with all the random dungeon pathing and elite affix handling but we'd have to see!

 

[Nadd]

For some reason my demonbuddy bugs around and stops working if I use this plugin with Fan of Knives(Demon Hunter) in my bars, any idea why? Using Beph routine.
My other issue is, at some point it stops chasing the goblins and returns back to the latest profile waypoint.

 

[GilesSmith]

For some reason my demonbuddy bugs around and stops working if I use this plugin with Fan of Knives(Demon Hunter) in my bars, any idea why? Using Beph routine.
My other issue is, at some point it stops chasing the goblins and returns back to the latest profile waypoint.

I don't have a DH to test this with atm but it sounds like more of an issue with Belph than the plugin - have you tried using the latest test version of Belphegor? If it remains a major issue, I'll take a look at Belphegor and fan of knives and see if I can see why it's upset, but there's no real reason it should be - it just alters what targets are provided, it doesn't interfere with telling DB how to attack or not.

As for goblins - try setting them to "Prioritize" in the config - they'll be chased harder and for longer then. Also note that if they go out of your kill radius, they will get ignored (this was always the case even without the plugin) - if you have a routine that sets your kill radius very low, this could stop DB "seeing" them when they run far enough away from you.

 

[teivovo]

v1.4.4 uploaded:
-- Various optimizations and tweaks to help speed up target selection for melee characters, particularly with lots of targets.
-- Further optimizations and more intelligent decision making if a character with no range abilities is surrounded by mobs.
-- Melee characters can now sometimes ignore point-blank monsters in favor of nearby summoners/priority monsters, as long as they aren't heavily surrounded.


Important note to people that use any DemonBuddy command-line loaders, eg batch-restarters
DemonBuddy currently starts running a routine before all plugins have been loaded into memory if loaded from command-line. This can cause random problems, bugs, and outright failures from any complex plugins that take more than a millisecond to load or plugins that need to load from external data-files (config files & windows). Please avoid using any command-line DemonBuddy launchers if you have many plugins or are using any of my plugins, until DemonBuddy updates to either allow a forced-delay in command-line before starting, or has safety checks to ensure all plugins are compiled and loaded before it can start a routine.

Hey bud,

I managed to do up a work around in DB run v2.0d. It should work fine with this workaround.

Cheers!

 

[Nadd]

I don't have a DH to test this with atm but it sounds like more of an issue with Belph than the plugin - have you tried using the latest test version of Belphegor? If it remains a major issue, I'll take a look at Belphegor and fan of knives and see if I can see why it's upset, but there's no real reason it should be - it just alters what targets are provided, it doesn't interfere with telling DB how to attack or not.

Yes, sry did some more tests, seems to be a general problem with Demon Hunter + Beph, sometimes (very often) stops moving and just spamms some abilities until I uncheck the plugin.

 

[cdmichaelb]

on shielding/fast ranged mobs when your plugin tells it attack something else, it's sending it too far out of its way, and eventuallythe profile can't continue running because it's "stuck"