The thing about the packaging is - steam doesn't package my folders. somwhow? They had separate IDs and pages and all that, but only whichever one was last downloaded would show at once. modpak info or dirty edits, but when they were distributed through steam they would conflict with eachother. Meaning they worked in concert fiine when using the old. This should be done from a Terminal window.Ĭlick to expand.Yeah I get that, I meant I moved them to the mod folder so I could test them working outside of the steam/steamapps/workshop/content/21180/ blah blah folders.
To do the last step in one command, run it like so (replace the things in with the appropriate things).This is not mentioned anywhere in the guide, but steamcmd will refuse to upload the mod if you don't save it with a vdf extension. The text file has to be saved with a vdf extension.Additionally, I suggest replacing that one entirely with a simple replace path to the image file, as Steam also supports the superior PNG and GIF formats. The preview.jpg link is broken due to this. OS X and Linux don't use backslashses (\) in their path, but forward slashes (/).Here are links for the other system versions (including linux, because there are more distros than Ubuntu). You only linked the windows version (which isn't even required for this guide). steamcmd is in the default Ubuntu repositories from 16.04+.I'm sorry, but the guide is incomplete and seems to be written for Windows, rather than for Linux and Mac. Now run Steam CMD and let it finish its initial unpacking and if the window closed run it again. Next you should pak your mod.and rename it contents.pakĬreate a new folder and place only the contents.pak inside. It does not need to be in the mod folder. Once everything is set - save the file some where. Preview File: For OSX and Linux use forward slashes to list the directory.AppID is the Starbound AppID - which is already provided above.
0 kommentar(er)
