Secure Hooking system for mods#49
Draft
Saxashitter wants to merge 8 commits into
Draft
Conversation
added 8 commits
June 9, 2026 18:07
… into secure-hooking-system
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
1 participant
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.
Similar to vanilla SRB2, this is a simple hook system designed to work with Battle without changing 99% of it's codebase. On top of that, the way it's made allows for mods to ONLY add hooks, and not run the hooks that were added or make new ones. I would like for this to not be pulled untill hooks are added across all of SRB2 Battle and support is finalized, but I can't do it without proper help to ensure consistency and functionality, given how complex Battle is as a mod.