-
Notifications
You must be signed in to change notification settings - Fork 31
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
Add support for loading unpacked ZIPs #10
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looked thru it quickly and tested the provided build on discord, everything seems to be working correctly.
Compiled PCK for Brotato: ZIP of a few Brotato mods for testing (ContentLoader, Invasion, VersionString): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Amazing stuff 👍
I will test it with my mods real quick and merge it 👍
This is a major update:
.import
folder, and matches the file system structure in the editor.I've also updated the docs to recommend putting extender scripts in a dir named "extensions". This helps keep your mod folder tidy, as all extender scripts are separate from your mod's core files (eg
ModMain.gd
).Breaking Changes
This update changes the way mod ZIPs are structured. I've updated the README.md to describe their new structure. In short, the zip's filename is now arbitrary, and the contents of the ZIP are loaded into the root. A mod's own files should be included in a folder called "mods-unpacked", and internal references to your mod's files should follow that path, eg:
res://mods-unpacked/Author-ModName/ModMain.gd
Here's an example ZIP:
Brotato-VersionString.zip
And here's how it looks when editing a Brotato project: