LethalConfig Changelog

What's new in LethalConfig 1.4.1

Apr 19, 2024
  • Exposing BaseConfigItem#ApplyChanges, BaseConfigItem#CancelChanges, and BaseConfigItem#ChangeToDefault (@AinaVT)
  • Added optional Assembly argument for LethalConfigManager#AddConfigItem (@FerusGrim)
  • Marking dynamically loaded mod icons as non-readable to improve memory usage. (@AinaVT)

New in LethalConfig 1.4.0 (Apr 3, 2024)

  • Updating config appearances whenever a ConfigEntry is modified directly.
  • Added QueueCustomConfigFileForAutoGeneration method, allowing the auto generation of configs for manually created config files.
  • Added new options to TextInputFieldOptions:
  • NumberOfLines Sets how many lines a text field can have. Setting it to 0 means no limit.
  • TrimText When true, automatically removes empty space from the start and end of the text.
  • Added new component TextDropDownConfigItem, which allows you to make a dropdown selector for strings (including configs with AcceptableValueList) (thank you @kittenji) (#29)
  • Adjusted colors of the menu to be darker. (#28)
  • Added "Hide Lethal Config" config to disable LethalConfig in-game. This setting is only visible on the r2modman's config editor and is false by default. (#13)
  • Fixed issue where a mod couldn't have more than one generic button (comparison would always think they're the same). (#38)
  • Attempt to fix issue where configs would not be generated if a plugin's instance was null at the time of the generation. (#40 #31 #30)