Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add custom Seal Order handling to Diablo and DiabloHelper #2129

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

jmichelsen
Copy link

There are two scenarios where a custom seal order comes in handy, that I've found:

  1. You want to clear the seals as fast as possible and just get to Diablo (for mf). With multiple bots, they can each take a seal or two, and meet up at Diablo when the seals have been finished.
  2. Your bot struggles with a specific seal boss and you want to do things in a certain order. You can put the boss the bot struggles on last in the order and if it does end up chickening, the run won't end too quickly and cause realmdown.

Additional config vars added in this change:
Config.DiabloHelper.OpenSeals // This allows you to control whether or not a helper will open seals. Useful for if your helper is assign seal x and the main bot is assigned seal y, z. (default: false)
Config.DiabloHelper.SafePrecast // Previously, helpers would always warp to a random WP and precast, but they'd also precast during their run. If you want to disable their safe precast, set this to false (default: true)

Implementation details:
SealOrder is checked to see if a specific order has been defined. The default order is the old order, viz/seis/infector. If a user defined order is in place, that order is followed. The order is respected even
if less than three seals are listed. If Diablo is not found, all the seals are checked in the default a second time.

SealOrder can contain seal bosses by name, or number. 1==vizier, 2==seis, and 3==infector

SealOrder is checked to see if a specific order has been defined. The
default order is the old order, viz/seis/infector. If a user defined
order is in place, that order is followed. The order is respected even
if less than three seals are listed. If Diablo is not found, all the
seals are checked in the default order.
This follows the same design as the SealOrder processing in Diablo.js
@jmichelsen jmichelsen changed the title Add custom Sear Order handling to Diablo and DiabloHelper Add custom Seal Order handling to Diablo and DiabloHelper Jan 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant