Add support for loading unpacked ZIPs #10
Merged
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 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:https://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: