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 options for ending encounters after wipes and out of game combat #134

Merged
merged 2 commits into from
Jul 25, 2020

Conversation

quisquous
Copy link

This adds common OverlayPlugin logic for the Network6D wipe lines, that is already implemented in both cactbot and Triggernometry.

This also reimplements the work from @KattTails in this cactbot branch to end encounters after a set amount of time.

It's not clear that "EnmityMemory" is the best place for this, but it
seemed better to put it with code that was roughly similar and already
doing the same sort of memory polling, rather than create separate
memory classes for this one off signature.
This adds two opt-in event settings for ending encounters, one on wipe
and one five seconds (non-configurable) after game combat ends.

This is already implemented in both cactbot and Triggernometry, and so
it makes some sense to consolidate these options in one place where
they can be useful to everybody.

The "five seconds" combat option is intended for the use cases of
older fights (such as ARR/HW where the Network6D line is not sent)
and dungeons (to split before a boss).
@ngld ngld merged commit c4e90f3 into ngld:master Jul 25, 2020
@ngld
Copy link
Owner

ngld commented Jul 25, 2020

Thanks a lot (and to @KattTails, too)! I'm sorry it took so long for me to get around to merging this. RL kept me busy.

sandtechnology pushed a commit to sandtechnology/OverlayPlugin that referenced this pull request Dec 18, 2022
)

Update MapEffect and CEDirector opcodes for 6.28h
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.

2 participants