Your own organization approach may vary, but I recommend keeping “things I’m making” separate from “things I’m extracting”. My Mods/ is where I put works-in-progress. workfolder/ is where I put extracted paks that I’m working with. Once that’s done, I recommend organization. Make sure to read the Guide on the site for installation and basic functionality instructions it’s not hard, but you’ll need to point it at a few specific files. While Starbound does technically come with a tool for that, a lot of people – myself among them – prefer something with a graphical interface. paks, and to create them if you want to release the mod.
How to use steam workshop mods with starbound how to#
The “name” is the one you need here, as that’s the internal name used for an “includes” section, used to make sure it loads after the race in question so it overrides the original ship.Got a race that you like and a ship that you don’t? Yet no one on the Workshop has made a mod to give it the ship you want? Here’s how to do it yourself.įirst, you’ll need a way to extract. "friendlyName" : "The Moogles of Ivalice"Īs you can see, there’s both a “name” and a “friendlyName”. "description" : "FF12/Tactics (Ivalician) Moogles in Starbound.", Check the race you want to use to see how their objects are named, and – if you want to use the race’s original objects – correct the ship’s nfig to match for those specific parts before you copy it over. You’ll see that this ship points at Apex resources. I’m using Sublime, but Notepad works just fine too. That’d crash because the furniture doesn’t exist, so, let’s open that up before copying it over. For example, maybe you want that nice black-and-white Soma but you don’t use the Ningen. This, however, would leave you with the new ship’s SAIL, locker, etc – which is a problem if it’s a ship for a race you don’t have installed. Now, the easiest way to do this is simply to copy that from the new ship as-is and leave it alone. There’s just one more thing to address, and that’s the nfig. This way, you don’t have to mess around with JSON. structure files still have the original name, the race will already be pointing to those. structure files you copy will point to the names of the pngs used by the new ship, without any further editing. structure files to match what the race currently has. The easiest way to do this is to copy everything except nfig from the ship you want over the current ship, and rename the. Now, this is a lot of files! The good news for you is, this is way easier than it looks. Lastly, if you’re replacing the ship of a modded race you want to play as, copy that race’s _metadata file, and set that aside for later. If you’re working with a ship that has those, make sure you copy those folders too (and keep the folder structure intact!), or you’ll crash. Certain ships also have additional blocks in other folders, the Soma being the main one that comes to mind. That is to say, don’t take /floran/ out of /ships/, move the entire /ships/ folder. When you have that, copy the /ships/ folders to separate locations, keeping the structure intact. If you’ve gotten a ship this way that you don’t intend to use in its original mod, you can unsubscribe now you’ll still have to be subscribed to the race you’re playing, of course. pak elsewhere, wherever you intend to work with it at. It will, usually pretty quickly, find a folder with that number as its name. Hit enter, and it will search for the mod for you. See in the top right, above all those numbers? That is where you put the Workshop ID. Next, go to your Steam Library on the same drive Starbound is installed to. You can also get this number by right-clicking on the workshop page and selecting Copy Page URL, but you’ll have to paste it somewhere to just get the number. Copy that entire number, that’s the Workshop ID. Look in the pink rectangle there and you’ll see a number. The easiest way to find them is to middle-click on the mod in question in the workshop, to pop it out in a new window. If you’re working with a vanilla race or ship, you’ll find their content in /assets/packed.pak.
0 kommentar(er)
