Via Command Line - The Way It Was Intended It may come in handy in more ways than one.Īnother handy window to have around would be the win32 folder mentioned above. Create it, open it up, and keep the window around for later. In this specific case, it would be best to create a separate “workspace” folder somewhere to tinker around with the mods. Good preparation can save a lot of hassle down the line. Otherwise, there is a “Drag And Drop” section, using a rather hidden Windows feature to make things simpler. If you are comfortable with a little typing, check out the “Via Command Line” section. But they are written as command line tools, so just starting them like that will be no good. These two programs, asset_packer.exe and asset_unpacker.exe are all we need for packing and unpacking.
For Windows users, they are located in the win32 subfolder of your installation, right next to your storage, mods and other folders. Thankfully, every Starbound installation comes with all the tools necessary for packing and unpacking the asset files. pak's from other games have no relevance here whatsoever. pak files is valid for Starbound mods, and. Therefore, only information specifically for Starbound. The problem is that these files are not all created equally, and Starbound is all alone with its type of. Unpacking should only be done if you’re that curious about in game assets or maybe want to work to make your own addons. As all you have to do is drag the pak file into the mods folder and it works. The pak file is the recommended format for it to be in. If you’re under the assumption you have to unpack the pak file to use the mod.