COMMON WORKSHOP ISSUES AND SOLUTIONS

Hey there! Since FBR has no official 'how-to' guide for Workshop issues that may crop up, me, as a community member (along with the agreement of a couple cohorts) has decided to create a thread detailing about the [i]common[/i] issues regarding workshop mods. I recently saw someone ask for this help, which adds to this thread being [b] L O N G [/b] overdue. By the way, if you don't have the modpack already, follow this link: [url]https://steamcommunity.com/sharedfiles/filedetails/?id=734142101[/url] I will try to cover as many common solutions to this as possible. [b][u]I installed all the mods, can't connect to the server![/b][/u] There's a couple fixes to this; check your options! There is an option called 'Allow mismatching mods'. A lot of people skip this, so don't feel like a fool or an idiot if you did. If this still doesn't work, sometimes, the workshop can corrupt mods upon installation. There's no easy way around this - reinstall the modpack again; twice, if you have to. Still not working? Well, here's one nuclear option. It rarely happens, but for some inexplicable reason, Starbound simply doesn't register Workshop mods; you can try reinstalling the game first, but usually this is quicker. Your Steam Workshop for starbound [i]should[/i] be this directory: C:Program Files (x86)Steamsteamappsworkshopcontent211820 If you have altered the place where Steam naturally installs, follow your own directories to it until you reach your Steam installation. Inside the various numbered folders, you may find a .pak file; all of them are going to be named [i]contents.pak[/i]. Once you are at that directory, install this: [url]https://github.com/nng68/StarPakBrowser[/url] This is going to be a long process, but you will need to use the above tool to check each [i]contents.pak[/i] files of each individual mod. The reason you want to do this, is so that you can name each pak file by mod name. Create a temporary folder; you will then sort through these files, name the .pak files according to the mod they come from and then cut & paste it into the temporary folder you have created. We are doing this because if you had mod issues later, we can name mods to you and thusly, you can find the target mod. Also because files of the same name and type [b]will[/b] overwrite each other. Once you are done with this, move this temporary folder into Starbound's inherent mods folder. If you do not know how to do this, go to: "Steam (the application) ---> Libraries ---> Right Click 'Starbound' ----> Properties ---> Local Files ---> Click 'Browse...'" Once you've done that, you should see the 'mods' folder within the root of Starbound's directory; place your mods into that. What this does, is instead of using the WorkshopData and that shenanigans, Starbound will read that mods folder instead; the content is the same, just when a mod updates, you will have to update the mod manually by doing this process [i]again[/i]. Blame CF for shakey and poorly written code in... well, almost everything about this game. [b][u]What if none of these work?[/b][/u] Leave a thread asking for support, or reply to this thread. People should check in here occassionally, and we'll try to help you the best we can; be sure to check in frequently!