Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto-Update DayZ mods #215

Open
Osiris-Team opened this issue May 15, 2023 · 0 comments
Open

Auto-Update DayZ mods #215

Osiris-Team opened this issue May 15, 2023 · 0 comments

Comments

@Osiris-Team
Copy link
Owner

Osiris-Team commented May 15, 2023

The Steam workshop id of a mod can be found in: ./@INSERT_MOD_NAME/meta.cpp which looks something like this:

protocol = 1;
publishedid = 1559212036;
name = "CF";
timestamp = 5249804932187309401;

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.

@github-actions github-actions bot added this to 🔍 Evaluating... in AutoPlug-Client-Development May 15, 2023
@Osiris-Team Osiris-Team moved this from 🔍 Evaluating... to ⭐️ Enhancements in AutoPlug-Client-Development Jan 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
AutoPlug-Client-Development
  
⭐️ Enhancements
Development

No branches or pull requests

1 participant