Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
One of the potential causes for that error is if FU somehow loads after this mod.
Weirdly enough, I didn't put FU in my mod's includes list and left the priority value set to 0, probably forgot to do so, as the FU flashlights were late additions.
I just updated the mod and its addons to have a higher priority and to load after FU.
Unsub and resub to the mod to force steam to download the latest version and tell me if the error is still there.
I will need your game log of a session where the crash/error happens to be able to fix anything.
You can find it by going into your game files, entering the storage folder and opening a text file named starbound.log .
If you see multiple files with that exact same name and are using Windows, then press the button View at the top of the window and tick the File name extensions option to show the full file names.
Then, copy the file's contents into a file sharing site, like pastebin and post a link to it here.
Some extra info on the nature of the issue will be helpful, like at what screen a crash happens, what the symptoms of a script error are, etc.
Though the way the game is loading the mods is very odd, it's not registering any mod IDs and all source paths look like folders rather than pak files.
Just to to make sure, you did copy the pak file within each workshop mod's folder into your mods folder rather than the entire workshop folder as is, right?
Because in the latter case, SB doesn't load the mods properly.