Create release script to automate release and make the process less error-prone
NeunEinser opened this issue ยท 0 comments
The release script should
- Place the release name in files where needed
- Update the resource pack hash
- Be able to comment and uncomment in mcfunction files
- Minify json files and remove comments and empty lines from function files
- Make all needed files (world file, resource pack file and datapack file)
- For the resourcepack, there needs to be a way to define dependencies to download
- Nothing that is done for the release script must interfere with Minecraft. Minecraft still needs to be able to run everything from the pack normally when loading it in an unreleased format
Place Release name in files where needed
I think it would make sense to store those as variables in the repository so the script can find and replace them. For example the script could look for something like {NEUN_SCRIPT:release_code}
and replace that with the version indicator.
Ability to comment and uncomment in mcfunction files
The usecase we currently have for this is the resourcepack check which has a version that is only active on release and a version that is only active during development.
The most sensible solution I see here is have a special comment e.g. #NEUN_SCRIPT uncomment