Tentacular wrote:the problem seems to occur once I unzip it and rezip it, and rename to .ftl again.
it's a file structure issue
the file structure that's needed is: mod.ftl -> data -> blueprints.xml.append
your file structure instead looks like: mod.ftl -> mod -> data -> blueprints.xml.append
when rezipping, you should select the data folder and send it to a compressed zipped folder (if using 7zip or winrar, add to .zip archive), then rename to .ftl (alternatively you can enable the allow_zip setting in slipstream preferences to see .zip files as mod files, but keep in mind that you should release your mods as .ftl so people can use your mod easily).
patching the mod file you uploaded results in the unexpected innerpath warning, because there is an extra folder level before the core folders (data, img, etc.)
you may not be able to see this difference because the windows default view may be skipping single folders in the path when extracting/unzipping and rezipping.
in any case, again, to fix the error you should zip up the data folder, not the ships.rebalance.testing2 folder.
--------------as a sidenote, slipstream can create mod boilerplate for you (File -> New Mod...) which I've found useful when zipping only because when zipping a selection of multiple folders the name of the parent directory will take the name of the new .zip file. you can thereafter remember that you need to select folder
s when creating a .zip. though, the real point of the mod boilerplate is that it will give you the template required for setting up the slipstream description.
as another sidenote, slipstream can zip up folders for you through running the exe/jar on command line with arguments, enabling much faster testing. read the Commandline section in readme_modders.txt for the possible arguments. if you don't know what that means, we're using slipstream to patch folders, mods, and/or run ftl, but without directly opening modman.exe with its user interface. instead we'll specify it through text, i.e. command line arguments.
this is what I typically do: go to file explorer and go into the folder with slipstream's exe. go File -> Open Windows Powershell. here's an example usage:
Code: Select all
./modman.exe --patch "my mod" hello.ftl --runftlthe different parts of this are:
./modman.exe ~~> runs the executable
--patch "my mod" hello.ftl ~~> patches the mod folder named "my mod", then the mod file named hello.ftl. you need quotation marks if the file/folder has spaces in its name
--runftl ~~> runs ftl
also if you've never used command prompt or any kind of shell before, up-arrow will cycle through previously entered commands, and more importantly don't use commands you don't know the usage of; some safeties like recycle bin are off.
