Starbound How To Install Mods On Server

Starbound has received a positive response from fans with a review score of 9/10 on Steam and 84% on PC Gamer. Highlights of the game include its modifications, content and graphics, however some players have commented on its poor revival mechanics and bugs.

  1. Starbound How To Install Mods On Server Settings
  2. Starbound Install Mods On Server
  3. Starbound How To Install Mods On Server Minecraft
  4. How To Use Starbound Mods
  5. Best Starbound Mods
  6. Starbound Mod Folder
  7. Mods For Starbound

Running windows 95 in dosbox. The game is set in space following the destruction of earth, where players have the opportunity to travel and explore a number of different planets, defeating enemies and earning new weapons and miscellaneous items. As a sandbox game, there are a number of missions that players can complete along the way.

After renaming each mod.pack file, copy the Starbound workshop mod.pack file of each mod you would like to install on your server and paste those mod.pack files at a safe location on your computer. Once those mod.pack files are downloaded and renamed, you will now need to install those mod files to your Starbound game on your computer. In order to run mods on your client, you will need to install Forge client side. How to Install Mods on a Minecraft Server. Downloading mods. You need to get the mods from CurseForge or the mod authors official site. Doing this ensures that you won’t get corrupted files or viruses. Once you decide on a mod you want, click the name to open the. Launch starbound.exe as many times you need. Resize the windows however you like. Start a world on one instance. Make sure IP joinable is enabled in the pause menu options. On the others, go to Join game - Choose a (different) character - Set as the server address and leave the port, account and password boxes empty. Tips before you. / starboundserver RAW Paste Data #!/bin/bash # Added rmdir line as apparently when you unsubscribe from mods steam workshop leaves behind an empty mod folder echo 'Updating Starbound.'

Starbound was developed and published by Chucklefish, also known for games such as Wargroove, Risk of Rain and Wanderlust. Users can currently access the game on the following platforms: Microsoft Windows, OS X, Linux, PlayStation 4, PlayStation Vita and Xbox One.

Starbound Save File Location

Your Starbound save files hold all of your game data. Having access to them is handy in case you ever want to create a backup, move them to another computer, modify them, or share your save with a friend. Find out how to find them on your operating system below.


On Windows, your Starbound save files will be in this folder:

To access that folder:

  1. Open up File Explorer - do this by right clicking the start menu button and clicking File Explorer
  2. Click the address bar at the top and paste in C:Program Files (x86)SteamSteamAppscommonStarboundstorageplayer
  3. Hit ENTER

If that folder doesn't exist, follow this guide to locate your Starbound files location, then go into the player folder.


If you're playing Starbound on a Mac, your save files will be located at:

To access that path:

  1. Open a Finder window
  2. Press COMMAND + SHIFT + G on your keyboard
  3. Paste ~/Library/Application Support/Steam/SteamApps/common/Starbound/storage/player into the text field
  4. Click Go


Linux-based operating systems running Starbound create save files in this directory:

Starbound Mods Folder

Find where your Starbound mods folder is located below (it varies based on your operating system).

Starbound How To Install Mods On Server Settings

IMPORTANT NOTE: Your Starbound mods folder doesn't exist by default. The below locations are where it can be found based on the assumption that it has already been created by yourself or third party software.


On Windows, your Starbound mods folder is located at:

If that doesn't exist, follow this guide to locate your Starbound folder, which is the folder that the mods folder is within.


On Mac, your Starbound mods folder is located at:

Starbound Install Mods On Server

To open that path, open a Finder window, press COMMAND + SHIFT + G, paste ~/Library/Application Support/Steam/SteamApps/common/Starbound/mods into the text field, and then click Go.

If that doesn't exist, follow this guide to locate your Starbound folder, which is the folder that the mods folder is within.


On Linux-based operating systems, your Starbound mods folder is located at:

If that doesn't exist, follow this guide to locate your Starbound folder, which is the folder that the mods folder is within.

Starbound Config FIle

You can find your Starbound config file (starbound.config) at the one of following paths:






If the directory for your operating system doesn't exist, follow this guide to locate your Starbound folder, then go into the storage folder from there.

  • 1Quick Navigation
    • 1.1Step 1 - Unpacking Assets
    • 1.2Step 2 - Modding
    • 1.3Step 3 - Setting Up Your First Mod
    • 1.4Step 4 - Packing your mod
    • 1.5Step 5 - Publishing

This article will show you the steps you need to take before you can start actually modding, and also the steps you can take after you are done modding, to pack and publish your mod.

You will need a text editor that is not the Windows included notepad.exe, as it does not support UNIX line endings. Do not use a word processor such as MS Word instead of a text editor. Only UTF-8 is supported, other encodings are likely to cause crashes. Optionally, for easier packing and unpacking of mods and assets, you may use ModPackHelper (available for Windows and Linux) or PAK GUI.

Step 1 - Unpacking Assets

Furious Koala introduced a .pak format which improves loading times and eases mod distribution. This means we need to unpack the assets before we can start modding.

Note - This step will not remove or change your packed.pak file, but simply extract its content for use as reference material. Unpacked assets may be safely left in .assets and changes you make to the unpacked assets will have no effect on your game as Starbound will prioritize the use of assets.pak (unless the unpacked _metadata is deleted).


Current as of Version 1.4.3, June 27th, 2019

  1. Open up the main directory folder for Starbound.
  2. Shift + right-click within the folder and select Open Command Prompt/Windows Powershell or equivalent (depends on Windows version).
  3. Type the following into Command Prompt/Windows Powershell: .win32asset_unpacker.exe '.assetspacked.pak' '.assetspacked'
  4. Command Prompt/Windows Powershell will do nothing until asset_unpacker.exe has finished, this will take a while on most computers.. There are no progress updates.
  5. Once Command Prompt displays a message equivalent to this, 'Unpacked assets to Packed in 250.063s,' you can close the program and move on to creating mods.


  • If purchased from Steam, the location of the main Starbound directory folder typically looks like this: SteamsteamappscommonStarbound
  • The text typed into Command Prompt are three directory locations:
    1. The location of asset_unpacker.exe, which is the program that does all of the unpacking.
    2. The location of Starbound assets, or Mod assets, to be unpacked.
    3. Where you want the unpacked assets to be dumped. This third string can be changed to whichever location or name you prefer. However, dumping into .assetspacked will make assets more readily available to Tiled.
  • The command can be stored as a batch file for faster unpacking whenever a new game version is released.

It is advised to read the Unofficial Modding E-book instead, available on Chucklefish Forums.


Current as of version 1.3.0, June 13th, 2017

If you have purchased Starbound from Steam, then these instructions will work. Otherwise you will have to find your Starbound assets folder and apply the file paths to these instructions.

  1. Open in OS X (hopefully you have 10.7 or higher)
  2. Type cd ~/Library/Application Support/Steam/steamapps/common/Starbound/assets Now you are in the assets folder.
  3. You need to create a new folder here where you want your unpacked assets to end up. Type mkdir unpacked
  4. Now you need to navigate to the asset_unpacker. Type cd ./osx
  5. Type ./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 and start over. If retrying doesn't work, then you have an issue external to the asset_unpacker.)
  6. In Finder browse to your unpacked folder by clicking on 'Go' on the menu bar, holding the [alt/option] key on your keyboard (this will show Library, which is usually hidden), clicking on Library, then browsing to -> Application Support -> Steam -> steamapps -> common -> Starbound -> assets -> unpacked (sound familiar?).

It is highly recommended that you make a backup copy of your original, working packed.pak before you mod and pack.

To pack, do exactly the same steps as mentioned above (minus making a new folder 'unpacked'), but when you get to step 5, where you actually unpack the packed.pak file:

Starbound How To Install Mods On Server Minecraft

  • Type ./asset_packer ./assets/unpacked ./assets/packed.pak


Current as of version 1.2.3b, May 26th, 2017

  1. Open the main directory of starbound in your shell (i.e. ~/.steam/steam/steamapps/common/Starbound if purchased on steam)
  2. Type the following into your shell: linux/asset_unpacker assets/packed.pak unpacked_assets
  3. linux/asset_unpacker is the path to the executable
  4. assets/packed.pak is the path to the packed assets
  5. unpacked_assets is the name of the directory, where it'll extract the files in. If the directory doesn't exist, it'll be created.
  6. There is no progress bar while unpacking, but after completion, it'll print something like this: Unpacked assets to unpacked_assets in 70.0567s
  7. After that message appears, you can close the shell and start creating mods.

Step 2 - Modding


Reference Pages

If you did everything right, Starbound should load your new mod the next time you run it. If the game crashes, or your changes are not found in the game, check your starbound.log file.

Step 3 - Setting Up Your First Mod

_metadata file

Full Article: Metadata file

The metadata file (usually named _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.

Step 4 - Packing your mod

Before publishing your mod, it is recommended to pack it as a single <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.


The mod uploader included with the Steam version of Starbound will automatically pack your mod into a pak file when it uploads to the workshop. If you subscribe to your own mod, you may copy this pak from the workshop folder for redistribution through other channels, or you may follow standard packing methods. Linux users may use Proton to launch the mod uploader.

Alternately, all users may use the SteamCMD method as per this guide by The Suit. This is the only reliable option for Mac users.


To pack your mod into a pak file, you may either manually use asset_packer.exe as included with Starbound, or you can automate it with PAK GUI or ModPackHelper.

Manual Method

  1. Create a metadata file for your mod if you intend to include one.
  2. For ease of use, ensure your mod folder is in .Starboundmods
  3. Open a command prompt as described in Unpacking assets.
  4. Run the following command: .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)
  5. Once finished, your .pak will be in the .Starboundmods folder and is ready to publish.


  1. Create a metadata file for your mod if you intend to include one.
  2. Extract PAK GUI anywhere and run it.
  3. Point the 'Path to Starbound' to the base Starbound folder.
  4. Either click 'Pack..' or drop your mod's folder onto PAK GUI and follow the prompts.

Windows/Linux with ModPackHelper

  1. Unpack ModPackHelper directly into .Starboundmods and run it.
  2. When script is launched, choose action 1.
  3. Then select the mod you want to pack (If your mod folder does not contain a _metadata or legacy .modinfo file, it will not show as a choice).
  4. Press Enter. The mod is available in the Starbound/mods/ folder as <modname>.pak.

Step 5 - Publishing

How To Use Starbound Mods

Only one thing left to do - publish your mod!


Best Starbound Mods

Once you have all desired fields filled in the uploader, hit 'Upload to Steam'. When the status bar vanishes, you're done!


Go to the official modding forums, select 'add mod' in the upper right hand section, select the category of your mod, fill out the information form and hit save. It is that easy.

Other Services

Starbound Mod Folder

Publishing methods for other services, such as NexusMods, may vary. Please refer to the individual service for more information. Otherwise, your mod's folder or pak file may be distributed as you choose.

Mods For Starbound

External links

  • Chucklefish Forums: How to successfully pack and unpack .pak files
  • Chucklefish Forums: Getting started in making mods for Starbound
  • Chucklefish Forums: Unofficial Modding Ebook 2.0
  • Chucklefish Forums: ModPackHelper
Retrieved from ''