Repository navigation
Engine/refactor - #124
Merged
Merged
Engine/refactor#124
Conversation
other default states don't work yet, will do refactor first
r0liveir
approved these changes
Oct 24, 2026
r0liveir
left a comment
Contributor
There was a problem hiding this comment.
Parece bom superficialmente
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This refactors the engine to use a proper state machine, it uses an Object Oriented aproach to store and define the states.
TODO:
Currently, to not break the frontend, most state variables are being stored outside of the state object. This will need to change, as this makes the states unable to record changes to themselves, this breaks any return_state variables.