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

Global CombatController #218

Open
orkaboy opened this issue Nov 17, 2023 · 0 comments
Open

Global CombatController #218

orkaboy opened this issue Nov 17, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@orkaboy
Copy link
Collaborator

orkaboy commented Nov 17, 2023

It would be neat if we could detect that we've entered combat or the level up sequence "globally" - ie in the scope of the Sequencer. This way we could avoid desynching and having to explicitly declare when we are expecting combat like we do now.

There are a bunch of caveats and potential issues:

  • How to handle Cutscene->Combat->Cutscene sequences?
  • How to handle recovery path sequences? Will these need to move to SeqMove instead?
@orkaboy orkaboy added the enhancement New feature or request label Nov 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant