So make sure there are no version mismatches. Each folder in that location will be named after the mod ID for the mod you subscribed to. Now, in your computers files, go to this location: /Program Files (x86)/Steam/steamapps/workshop/content/211820/ All Starbound workshop mods will be installed at this location in your Steam files.

If both path and workshopid are set, then the server will load the mod from the given path, but will tell clients the workshop id so they can download and enable them. This is required to allow the workshop mods to install within your Steam files.

Without ID conflicts you won't have to worry about this, so make sure there are none!

Server will prefer workshop mods over 'path' mods.

If you want to disable a mod, comment out the corresponding part of the lua file.

Server always enables all loaded mods.

In order to get the id of a workshop mod, go to its workshop site, and look at the last number of its URL. Using only workshop IDs is highly recommended for public servers. Mods are unnamed though, so youll have to match them up by file sizes and download dates. Workshop mods are stored in Steamsteamappsworkshopcontent211820.

If both are set, the server will load the mod from the path, and tell clients the workshop ID so they can download it. The mods folder is for manual installs - From SBs website.

pack files are downloaded and renamed, you will now need to install those mod files to your Starbound game on your computer. pack files at a safe location on your computer. pack file of each mod you would like to install on your server and paste those mod.

If a workshop ID is set and no path, the server will download the mod from the workshop and tell clients about workshop mod IDs so they can download and enable them before connecting to the server. pack file, copy the Starbound workshop mod.

If a path is set and no workshop ID, then the server will load the mod from the path and connecting players will have to install the mod themselves.

mods configures mods that are running on the server, either by workshop ID or path.

allowed configures mods that are allowed, but not required on clients.

Only recommended for people who know what they're doing. Prints errors, but enables mods nevertheless. hello good afternoon, I would like you to help me with something, it happens that normally one with subscribe to an object of the workshop installs the mod and already, as in the case of starbound, or other games, but in the SR4 the opposite happens, I subscribe and the mods do not appear to me, even downloading them from the web, I install them in the corresponding folders and as I have seen.

forceEnabling mods will be enabled by force.

If that is nil as well, it will default back to /workshop/ If nil, it will download to the folder configured in server.ini. If empty, it will download to /workshop/.

modLocation configures the location the server to download workshop mods into.

1 modLocation = '' 2 forceEnabling = false 3 4 local prefix = '/home/sid_1549528/avorionStable/galaxies/avorion_galaxy/mods/' 5 mods = 6

Starbound workshop mods location