The stand-alone mod S.T.A.L.K.E.R. Anomaly aims to be the most stable and customizable experience for fans of the S.T.A.L.K.E.R. games. It's powered by the Monolith 64-bit engine, a custom fork of the X-Ray engine.
This gives the user an option to set configurations for MCM settings in a file that persist through MCM, no matter what gets changed. More useful for those that use Modpacks.
Less f***ing-around to get the setup you want.
2. DLTX.
3. Some understanding on how MCM stores configurations from addons and what those configurations are.
I'm going to over-explain here, for everyones benefit; so bare with me.
This file on its own, without any customizaition does almost nothing.
There are a few lines included in the file as an example, which will toggle the settings listed in the file if you add this addon to your game. This is to show how it works.
This page/addon therefore, serves really as a how-to and guidance more than anything.
Only the vales you add in the .ltx of this addon will be affected. This is basically a 'whitelist' of what gets persisted. So if you don't want it changed from the 'default' then don't have it in the file (So that other changes by addons or updates can flow-through to other configs that arent in this file.)
You need some knowledge of what the setting is and what the variable you want to set it to, is. This is obtained via your arx_options.ltx if the addon or setting exists in there. (Which it probably does)
The specific case why i made this:
I use GAMMA modpack, and every time it got updated i had to go back through and re-change my configuration in MCM to my own settings. I could just use a pre-changed file that i'd saved, but the problem is it won't update certain changes and variables changed by updates and additional addons to the modpack, through MCM settings.
Long story short, i knew what i wanted to keep, regardless of updates/config changes, but wanted everything else that was changed/updated to flow through to the MCM config.
Quick example of how this works:
> I change ZCP Stalker population from default 1.0 to 1.5
>For some reason, A modpack update sets it to 1.2
> This addon will keep it at 1.5, regardless of what gets changed elsewhere.
Specifically, it does this because in this DLTX's persistent mcm's axr_options.ltx, i have set:
SMR/smr_amain/monster_pop_factor = 1.5
Again; Anything set in the file, will persist, and over-ride anything else that touches/changes that config setting.
Note about OPTIONS persisting:
Some 'options' settings do seem to work when set in this addon. For example, i don't like getting 'Random' PDA messages, so i turn this off every time. In the file, i set
alife/dynamic_news/random_msg_news = false
This means i'll never get this setting reset, and it's always disabled no matter what gets changed, if i update, or if i do a re-install of my entire game. As long as i use this addon and load it last.
Not all options persist (I haven't tested them all), i don't think graphics options persist, but weather settings do.
Here's an example of me setting the period for Weather so that Cloudy period is 6 hours (1), partly cloudy occurence is 'rare' (2) and the partly cloud period is 6 hours (3).
(1)
video/weather/cloudy_period = 6
(2)
video/weather/partly_occurrence = 2
(3)
video/weather/partly_period = 6
In summary, the best way to get the most out of this addon, is to Investigate what variables correlate with which MCM addon settings you use, that aren't the default, and add your lines to the .ltx file provided in this addon i've uploaded. Load it last in MO2.
I have included some sample lines in the .ltx for context as examples.
An attempt to visualise what this does:
Larger version here: I.imgur.com
Should be compatible with everything as it doesn't edit any pre-existing files.
I use this with GAMMA modpack and it works fine, because i ONLY set the lines i want to persist across updates.
Q: Where do i start?
A: Go to your axr_options.ltx and compare it to the default axr_options.ltx of the modpack you use. If anything in there is a different value, you've likely ticked a box, changed a setting, moved a slider, which has altered that config. Get THOSE LINES that are different, which you want to be saved and set to that value no matter what, and put only those lines into the .ltx file, under the relevant headers in there. Don't put any lines that you don't need to, because if the addon is ever updated and the config ever changed, you won't get the change to that config because you've needlessly added it to this DLTX'd .ltx file, thus over-writing it.
Average
8.77 votes submitted.
Sticky:
Sticky:
Sticky:
Sticky:
Sticky:
This does sound like a good idea. To make a dump of the values from axr_options.ltx elsewhere for use as soon as a modpack updates, now even better is that these values can be consistent without worrying about messing with options again.
Can see this being useful for other things at the same time as well.