| 1000 sectors |
| 3000 sectors |
| 4000 sectors |
| 6000 sectors |
.win32asset_unpacker.exe '.assetspacked.pak' '.assetspacked'
SteamsteamappscommonStarbound
cd ~/Library/Application Support/Steam/steamapps/common/Starbound/assets
Now you are in the assets folder.mkdir unpacked
cd ./osx
./asset_unpacker ./assets/packed.pak ./assets/unpacked
(The asset_unpacker should finish anywhere from 1 to 500 seconds depending on your computer, so let it work. If it takes longer than 20 minutes, quit Terminal.app and start over. If retrying doesn't work, then you have an issue external to the asset_unpacker.)./asset_packer ./assets/unpacked ./assets/packed.pak
linux/asset_unpacker assets/packed.pak unpacked_assets
Unpacked assets to unpacked_assets in 70.0567s
_metadata
) is a completely optional file that contains your mod's name, description, and more. If using the Steam Uploader Tool, a basic metadata file will be generated for you. While optional, it is recommended to have at least have a name set in the metadata in case a companion mod ever needs to require or include your mod, and to make your mod more easily identifiable within the game log should any errors occur.<modname>.pak
file. This simplifies installation (drop the file in the Starbound/mods/ folder). The alternative is to just put all the files into an archive for distribution which will need to be unpacked by end users to install..win32asset_packer.exe .mods<mod folder name> .mods<modname>.pak
(substitute <mod folder name> with your mod's folder and <modname> with whatever you wish)