Add a State Handler base node #101
Merged
Conversation
This file contains 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.
Introduces a new base node, the StateHandler. The StateHandler is a node that can handle and control events from a state machine. It provides a base class for custom nodes that need to react to state machine events.
The StateHandler is designed to be used in conjunction with the existing NodotCharacter3D class. It can be used to add custom logic to the character's state machine.
This change includes a refactoring of the existing CharacterExtensionBase3D class to inherit from the new StateHandler node. The CharacterExtensionBase3D class is now a more specialized class that can be used to add custom logic to the character's state machine.
Overall, this change will make it easier to add custom logic to the character's state machine, and will improve the overall flexibility and extensibility of the project.
Closes #100 and #62