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

Domination mission parameters configurable by properties file #63

Closed
longtimegamer opened this issue Jul 14, 2019 · 2 comments
Closed

Comments

@longtimegamer
Copy link
Collaborator

Is it possible for the mission parameters to be driven by file-based properties?

As an admin I use "#missions" to select the mission and then set the many, many mission parameters. As an example, my "taste" in Domination requires perhaps 20+ changes to the default parameters. So many clicks! (Or arrow keys!) Also the desired mission parameters are lost if the mission is stopped for any reason (because only "#restart" will remember mission settings). For this reason, many admins choose to download the code here to make changes and create custom PBOs for each update.

If there was a way to read defaults from a properties file then server admins would be able to use the "vanilla" Domination release PBOs and leave a properties file with the desired server tweaks in mpmissions folder (or wherever seems best). There are many properties that would be more accessible for tweaks, specifically the properties defined in description.ext, initcommon.sqf and fn_changeskill.sqf. It would be great to just create a few overrides in a text file once and after that each Domination release is just drop-and-replace for the new PBO.

What do you think? I could try to implement this myself too. Happy to try if you don't mind cleaning up my mistakes. :)

@Xeno69
Copy link
Owner

Xeno69 commented Jul 14, 2019

Simply use a SQL database and start the server with extDB3 and you can change all params in CfgParams in a database table and many other settings in the settings table.

The mission will then allways use the database values

@longtimegamer
Copy link
Collaborator Author

That's perfect, thanks.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants