Add custom Seal Order handling to Diablo and DiabloHelper #2129
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There are two scenarios where a custom seal order comes in handy, that I've found:
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 tofalse
(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 evenif 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
, and3==infector