Starbound Workshop Mods Not Showing Up

Starbound Workshop Mods Not Showing Up

1Quick Navigation1.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
Starbound Workshop Mods Not Showing Up Online
Starbound Workshop Mods Not Showing Up Fortnite
Starbound Workshop Mods
Starbound Workshop Folder
Modding
Mods not working - posted in General Starbound Discussion: I installed my mods using nexus mod manager but the mods are not showing up in game. Im using the steam to run the game. Do have to enable the mods like in skyrim or am i doing something wrong? REMOVE ALL MODS If you do have any mods installed, you should be able to find them in 'Subscribed Items' on Steam or in a folder called 'mods' in your Starbound Directory. Steps: 1# In Steam go to Starbound's Workshop. 2# Then go to Subscribed Items (hidden in the Browse tab) and unsubscribe all the mods there. I've had some complaints about my little autosave mod not properly being placed in the mods folder in My DocumentsOriginally Posted By: People on Steam Dunno if it's just me but this mod doesn't actually do anything. Doesn't show up in game in the mod menu. Even the.pak file where the mod. Feb 16, 2012 The mods folder is for manual installs - From SBs website. Workshop mods are stored in Steam steamapps workshop content 211820. Mods are unnamed though, so you'll have to match them up by file sizes and download dates. Jul 25, 2019 An URL that links to the mod. (Steam Workshop URL, Chucklefish Forum, Github, yourwebsite.net, etc) steamContentId: Each Steam workshop item has a unique ID. The Mod Uploader Tool available with Starbound's Steam version will fill this in automatically. Can be quoted (string) or not (number).

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.

Starbound workshop mods not showing up 2017

Step 1 - Unpacking AssetsFurious 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).
WindowsCurrent as of Version 1.4.3, June 27th, 2019
 Open up the main directory folder for Starbound.
 Shift + right-click within the folder and select Open Command Prompt/Windows Powershell or equivalent (depends on Windows version).
 Type the following into Command Prompt/Windows Powershell: .win32asset_unpacker.exe '.assetspacked.pak' '.assetspacked'
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.
 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.
Notes
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: The location of asset_unpacker.exe, which is the program that does all of the unpacking.
 The location of Starbound assets, or Mod assets, to be unpacked.
 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. http://community.playstarbound.com/resources/unofficial-modding-ebook-2-0.2930/
MacCurrent 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.
 Open Terminal.app in OS X (hopefully you have 10.7 or higher)
 Type cd ~/Library/Application Support/Steam/steamapps/common/Starbound/assets Now you are in the assets folder.
 You need to create a new folder here where you want your unpacked assets to end up. Type mkdir unpacked
 Now you need to navigate to the asset_unpacker. Type cd ../osx
 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 Terminal.app and start over. If retrying doesn't work, then you have an issue external to the asset_unpacker.)
 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:
 Type ./asset_packer ../assets/unpacked ../assets/packed.pak
LinuxCurrent as of version 1.2.3b, May 26th, 2017
 Open the main directory of starbound in your shell (i.e. ~/.steam/steam/steamapps/common/Starbound if purchased on steam)
 Type the following into your shell: linux/asset_unpacker assets/packed.pak unpacked_assets
linux/asset_unpacker is the path to the executable
 assets/packed.pak is the path to the packed assets
 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.
 There is no progress bar while unpacking, but after completion, it'll print something like this: Unpacked assets to unpacked_assets in 70.0567s
 After that message appears, you can close the shell and start creating mods.
Step 2 - ModdingTutorialsReference PagesIf 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 fileFull Article: Metadata fileThe 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 modBefore publishing your mod, it is recommended to pack it as a single .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.
Starbound Workshop Mods Not Showing Up OnlineSteamThe 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.
GeneralStarbound Workshop Mods Not Showing Up FortniteTo 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 Create a metadata file for your mod if you intend to include one.
 For ease of use, ensure your mod folder is in ..Starboundmods
 Open a command prompt as described in Unpacking assets.
 Run the following command: .win32asset_packer.exe .mods .mods.pak (substitute  with your mod's folder and  with whatever you wish)
 Once finished, your .pak will be in the ..Starboundmods folder and is ready to publish.
PAK GUI Create a metadata file for your mod if you intend to include one.
 Extract PAK GUI anywhere and run it.
 Point the 'Path to Starbound' to the base Starbound folder.
 Either click 'Pack...' or drop your mod's folder onto PAK GUI and follow the prompts.
Windows/Linux with ModPackHelper Unpack ModPackHelper directly into ..Starboundmods and run it.
 When script is launched, choose action 1.
 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).
 Press Enter. The mod is available in the Starbound/mods/ folder as .pak.

Step 5 - Publishing

Step 1 - Unpacking AssetsFurious 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).
WindowsCurrent as of Version 1.4.3, June 27th, 2019
 Open up the main directory folder for Starbound.
 Shift + right-click within the folder and select Open Command Prompt/Windows Powershell or equivalent (depends on Windows version).
 Type the following into Command Prompt/Windows Powershell: .win32asset_unpacker.exe '.assetspacked.pak' '.assetspacked'
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.
 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.
Notes
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: The location of asset_unpacker.exe, which is the program that does all of the unpacking.
 The location of Starbound assets, or Mod assets, to be unpacked.
 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. http://community.playstarbound.com/resources/unofficial-modding-ebook-2-0.2930/
MacCurrent 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.
 Open Terminal.app in OS X (hopefully you have 10.7 or higher)
 Type cd ~/Library/Application Support/Steam/steamapps/common/Starbound/assets Now you are in the assets folder.
 You need to create a new folder here where you want your unpacked assets to end up. Type mkdir unpacked
 Now you need to navigate to the asset_unpacker. Type cd ../osx
 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 Terminal.app and start over. If retrying doesn't work, then you have an issue external to the asset_unpacker.)
 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:
 Type ./asset_packer ../assets/unpacked ../assets/packed.pak
LinuxCurrent as of version 1.2.3b, May 26th, 2017
 Open the main directory of starbound in your shell (i.e. ~/.steam/steam/steamapps/common/Starbound if purchased on steam)
 Type the following into your shell: linux/asset_unpacker assets/packed.pak unpacked_assets
linux/asset_unpacker is the path to the executable
 assets/packed.pak is the path to the packed assets
 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.
 There is no progress bar while unpacking, but after completion, it'll print something like this: Unpacked assets to unpacked_assets in 70.0567s
 After that message appears, you can close the shell and start creating mods.
Step 2 - ModdingTutorialsReference PagesIf 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 fileFull Article: Metadata fileThe 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 modBefore publishing your mod, it is recommended to pack it as a single .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.
Starbound Workshop Mods Not Showing Up OnlineSteamThe 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.
GeneralStarbound Workshop Mods Not Showing Up FortniteTo 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 Create a metadata file for your mod if you intend to include one.
 For ease of use, ensure your mod folder is in ..Starboundmods
 Open a command prompt as described in Unpacking assets.
 Run the following command: .win32asset_packer.exe .mods .mods.pak (substitute  with your mod's folder and  with whatever you wish)
 Once finished, your .pak will be in the ..Starboundmods folder and is ready to publish.
PAK GUI Create a metadata file for your mod if you intend to include one.
 Extract PAK GUI anywhere and run it.
 Point the 'Path to Starbound' to the base Starbound folder.
 Either click 'Pack...' or drop your mod's folder onto PAK GUI and follow the prompts.
Windows/Linux with ModPackHelper Unpack ModPackHelper directly into ..Starboundmods and run it.
 When script is launched, choose action 1.
 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).
 Press Enter. The mod is available in the Starbound/mods/ folder as .pak.
Step 5 - PublishingOnly one thing left to do - publish your mod!
SteamOnce you have all desired fields filled in the uploader, hit 'Upload to Steam'. When the status bar vanishes, you're done!
ChucklefishGo 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 ServicesPublishing 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.
Starbound Workshop ModsExternal 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
Starbound Workshop Folder Retrieved from 'https://starbounder.org/mediawiki/index.php?title=Modding:Modding_Basics&oldid=187823' 