RimWorld

RimWorld

Work Tab
Mr Andersson Nov 19, 2022 @ 4:57am
Bug(?) Mod-Settings MaxPriority/DefaultPriority does not persist
Hello, and first of, thanx for all the great mods :)

I have searched to see if anyone else have reported this issue but I find no other mention of it.
Is this reproducible, or am I the only one affected?

This described behavior is not a new in 1.4, but was present for me all throughout 1.3 also, regardless of DLC/Expansion.
I cannot speak for earlier versions as I did not play 1.2 or earlier.
  • Reinstalling or repairing Rimworld has no effect.
  • Removing the mod and mod settings and reapplying the mod has no effect.
  • The issue has persisted over several reinstalls of the computer.

List of active Mods for me to reproduce the issue:
  1. Harmony (Required dependency for Work tab)
  2. Core
  3. Work Tab

Bug-report:
The Work Tab mod-settings for Max & Default-priority stored in .\Config\Mod_725219116_Controller.xml file is not re-applied when starting/re-starting Rimworld.
All other mod-settings are applied correctly from the settings file between sessions:

Affected attributes:
  • MaxPriority
  • DefaultPriority

Unaffected attributes:
  • TwentyFourHourMode
  • PlaySounds
  • PlayCrunch
  • DisableScrollwheel
  • VerticalLabels
  • FontFix

Observed handling of persistent settings:
All settings are saved correctly in the .\Config\Mod_725219116_Controller.xml file, including MaxPriority and DefaultPriority.
Example:
<SettingsBlock> <ModSettings Class="WorkTab.Settings"> <MaxPriority>6</MaxPriority> <DefaultPriority>5</DefaultPriority> </ModSettings> </SettingsBlock>


The In-Session settings always revert to 9 & 3 respectively upon restarting Rimworld, regardless of what the settings file contains.
Starting a new session of Rimworld will NOT revert the settings file to the default values, only the in-session settings.
any custom values in the settings file are retained but are also ignored and will only change in the file if the player make manual adjustments in the mod-settings GUI..
All other Work Tab mod settings are re-applied correctly from the config file bewteen sessions.

Manually changing the settings MaxPriority/DefaultPriority in the current session works fine both before starting a new game and loading a saved game.
Changning the settings while playing a saved games also works.
All Work Tab changes are applied within the current session and stored in the config-file correctly.

A new session will once again ignore the config file for these two attributes and show 9 & 3 respectively for the two attributes in the GUI.
The defaults are always used for new games and new pawns when loading a saved game.
However, all pawn-priorities from within a saved game for existing pawns will reapply correctly and adhere to the player custom settings from previous sessions
Within a loaded game, any new pawn will still follow the mod-default settings (9 & 3) for their work priorities, unless the Mod-settings are first adjusted before a new pawn is added to the colony in the current session.