You also can't open a box you don't have, so a subscription to the target mod is required.

1. Go to the steam page of the mod you want to investigate.
   
2. At the top of the page there should be a number after ?id=
   
3. This number is the [mod id], copy it.
   
4. In your library, right-click Starbound > Manage > Browse local files.
   
5. Replace the matching section at the top of your file manager with the path listed below.
   
6. Replace the [mod id] section with your number and press enter, your target is the .pak within.

Windows: \SteamApps\workshop\content\211820\[mod id]
Linux: /SteamApps/workshop/content/211820/[mod id]

1. Copy the contents.pak file.
   
2. Open the Starbound folder again.
   
3. Open the mods folder, or create a new folder for safety's sake, and place the .pak within.
   
4. Go back to the Starbound folder.
   
5. Create a new file, and rename it to end with a .bat for Windows.
   
6. Open the file with a text editor and paste into it:
   
   "win32\asset_unpacker.exe" "mods\contents.pak" "mods\unpack"
   
   (Inverted syntax:)
   "win32\asset_packer.exe" "mods\unpack" "mods\contents.pak"
   
   
7. Adjust to taste, or as necessary, and save the file.

1. Run the .bat (or equivalent).
   
2. Wait until the resulting window closes.
   
3. In a folder named unpack, within the target folder, should be everything that was in the .pak.
   
4. If not, run the file again as administrator. If unable, ask your administrator.
   
5. Done!

1. Crashing will occur if the same mod is both subscribed and in the mods folder at the same time.
   
2. Yes, any folder or .pak in the mods folder will be loaded as a mod.
   
3. Yes, the .bat needs to be in the Starbound folder, anywhere else will require changes to the .bat.
   
4. No, you don't have to have a mod in a .pak to run it, but it may load faster as a single file.
   
5. When uploading a mod to the workshop, the .pak will be made automatically, which is why downloading a workshop mod always results in a .pak.
   
6. Whether it's for forums or friends, manual packaging can be accomplished with the packer, found next to the unpacker, and a .bat with the inverted syntax found at your local software store in Step Two. - You can also get it by applying Step One to your own mod.

Looking for the base game's .pak? It's in the assets folder with the name packed.pak.
Never put it (or the folder it makes) in the mods folder; something will break.
Rename the .pak or adjust your .bat for the different name.

---

Does someone need this How-To? Well just send them this!
[url=http://steamoss.com/sharedfiles/filedetails/?id=745239455]A Basic How-To on Unpacking Mods[/url]

Did this help? If so, please rate the guide so that others can find it!

Credits:
AcidaliaPlanitia - Provided the inverted .bat syntax.