Skip to content

chore: load Swiftly signatures from the gamedata file the validator checks - #215

Merged
lukepolo merged 2 commits into
mainfrom
chore/swiftly-plugin-gamedata
Oct 5, 2026
Merged

lukepolo merged 2 commits into
mainfrom
chore/swiftly-plugin-gamedata

Conversation

@lukepolo

@lukepolo lukepolo commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor
  • ConnectClient and SetClan patterns were hard-coded in four Swiftly source files, while the validator checked a copy in shared/gamedata/fivestack.gamedata.json that no plugin loaded
  • each Swiftly plugin now ships that same file and reads its patterns from it, so what a plugin scans for is what the validator checked
  • the scan itself is unchanged (Core.Memory.GetAddressBySignature); only where the pattern comes from moved
  • the validator, its sets and its result JSON are untouched
  • tests assert every signature a plugin asks for is in the shipped file for Linux and Windows
  • not yet run on a live server

@lukepolo
lukepolo merged commit 03eb8f7 into main Oct 5, 2026
6 checks passed
@lukepolo
lukepolo deleted the chore/swiftly-plugin-gamedata branch October 5, 2026 18:03
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.

1 participant