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

DominusFight Plugin Example

pushedx

Well-Known Member
Joined
Sep 24, 2013
Messages
4,252
Reaction score
290
This plugin provides some example logic of triggering the Dominus fight, and staying in the area so the CR can kill it. After Dominus is dead and all loot is picked up, a town run is triggered so BasicGrindBot starts a new run.

This plugin could be extended for other bosses as well with minor adjustments. The only thing users need to do, is configure their CR to stop attacking Miscreations that endlessly spawn if they don't have enough DPS to kill them before the next wave spawns, so the bot can make its way to the final phase of the Dominus fight. Also, you might want to handle his totems differently so the CR doesn't focus on them too much. It's the CR's job to avoid the Corrupted Rain and stuff, but the bot pretty much stays within range unless the CR pulls it away to attack another target.

This plugin is being provided as an example for users, so any tweaks or changes to make it work different is up to users.

To use:
1. Exit the bot.
2. Create a folder in "Plugins" called "DominusFight".
3. Create the 3 following files inside the DominusFight folder.
4. Launch EB, and enable the "DominusFight" plugin.
5. Make sure your GrindZone is set to Upper Sceptre of God.

Warning: If you use the StuckDetection plugin, it might trigger in the middle of the boss fight, because there are times where you just stand in place killing everything on screen. The ideal solution would be to modify the StuckDetection plugin to not run when you're in boss fights, but that logic cannot be added to the generic version. A boss fight specific stuck detection plugin is pretty much needed.

Edit: This plugin is now included with Exilebuddy for reference.
 
Last edited:
THANKS A LOT PUSHEDX, that will increase our currency a lot while using the bot, its REALLY appreciated, im going to test it right now, enven if patch come in a few hrs
 
5 run so far and no bug at all, im more than happy with that plugin!!! thanks :)
 
Good to hear, thanks for leaving feedback on it. :)
 
In one instance, the script got confused by the entrance to the corrupted area, which looks like the entrance to the boss area, and got stuck.
 
yes that happenned to me to, but 99% of the time it work very well, i did over 50run (i think, cuz we dont know our numer of run anymore)
 
I makes Da post in da wrong section soz
https://www.thebuddyforum.com/exilebuddy-forum/177385-dominus-run-question.html#post1633185

I run a heavy duty hack and slash build with 4 insta heal 960 hp heal flasks. He mows them down and leech is ok but it aint great. I am always out of charges by the time dom goes into his 2nd phase, how can I edit a file somewhere in bot that will tell it to do a quick TP then come right back, no stashing nothing just filling pots.

Please help ty
 
In one instance, the script got confused by the entrance to the corrupted area, which looks like the entrance to the boss area, and got stuck.

Yeap, that's mentioned in the #907 thread. It's not this plugin, but rather the logic for trying to traverse though the boss area.
 

I'll make an example later, but basically, you'll need to add a new task that implements this specific logic, that only triggers when you set it to. Otherwise, if you go to town, a town run will trigger, but the bot will make its way back to the portal and fight before the instance expires.

The easy way would be to detect when you need a town run, and then set:
Code:
BasicGrindBotSettings.Instance.NeedsTownRun = 1;

When the task logic executes the next tick, it'll do a town run, and take the portal back.
 
Would probably work better for Vaal Oversoul and its an easy fight I guess. And its 60+ so items work for Chaos Recipes.
 
any idea why sometimes when the bot dies fighting dominus (lightning OP against melee RF marauder).. the bot respawns in town, and then doesnt finish killing dom?
Sometimes it respawns at checkpoint though and will finish killing dom.
Obviously if it restarts the run, the entire 5 minutes before that was wasted. What causes it to do this?
 
any idea why sometimes when the bot dies fighting dominus (lightning OP against melee RF marauder).. the bot respawns in town, and then doesnt finish killing dom?
Sometimes it respawns at checkpoint though and will finish killing dom.
Obviously if it restarts the run, the entire 5 minutes before that was wasted. What causes it to do this?

DeathsBeforeNewInstance in BasicGrindBotSettings would make the bot respawn to town and start again. It defaults to 5. You should be able to a log entry when this happens as well: "[ResurrectTask] Now adding a new instance override for the current area ..."
 
DeathsBeforeNewInstance in BasicGrindBotSettings would make the bot respawn to town and start again. It defaults to 5. You should be able to a log entry when this happens as well: "[ResurrectTask] Now adding a new instance override for the current area ..."

alright i'll just bump it up to 10, the whole fight is cake except for when my melee char decides to sit in one spot while he lightning blasts me 3 times in a row.. idk how to build to survive that crap.
 
so is this still working?

That navigation issue has not been fixed yet. The logic for traveling though a boss area needs to change for this area to fix the issue, and it's not related to the plugin itself. I'm hoping to make some changes to it "soon".
 
i havent had any problems with the plugin getting to dominus and killing him except for that small death before new instance thing I fixed.
Is there any way to make this ignore all monsters on the way to dom and JUST kill the bosses + dominus? For more speedy runs
 
There still seem to be problems with the corrupted area. When the plugin is enabled, the bot does not know how to leave the corrupted area since the "ExplorationComplete" is blocked. If I disable going to corrupted areas, the bot will still get stuck at the entrance to the corrupted zone like before.
 
Back
Top