You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is basically a Java properties file (expect the semicolons, that would have to be removed when reading the values).
Currently, all mods are in the same folder as the server, which isn't really nice. A workaround for this would be to use the -mod=ABOSULTE_PATH_MOD1;ABSOLUTE_PATH_MOD2;etc... argument to individually point to each mod directory which does not work really well according to testing by users.
The workshop mods are originally located in INSERT_DRIVE\SteamLibrary\steamapps\Common\DayZ\!Workshop. The question is if these should be moved into the server's directory or only symlinks should be provided to the original folders / wanted mods.
The actual updating can be done via SteamCMD by providing the app-id/workshop-id of the mod.
The text was updated successfully, but these errors were encountered:
The Steam workshop id of a mod can be found in:
./@INSERT_MOD_NAME/meta.cpp
which looks something like this:This is basically a Java properties file (expect the semicolons, that would have to be removed when reading the values).
Currently, all mods are in the same folder as the server, which isn't really nice. A workaround for this would be to use the
-mod=ABOSULTE_PATH_MOD1;ABSOLUTE_PATH_MOD2;etc...
argument to individually point to each mod directory which does not work really well according to testing by users.The workshop mods are originally located in
INSERT_DRIVE\SteamLibrary\steamapps\Common\DayZ\!Workshop
. The question is if these should be moved into the server's directory or only symlinks should be provided to the original folders / wanted mods.The actual updating can be done via SteamCMD by providing the app-id/workshop-id of the mod.
The text was updated successfully, but these errors were encountered: