V1.3.2+1.20.1-patch.1 (Fabric 1.20.1)
on Mar 19, 2025V1.3.2+1.20.1-patch.1 (Forge 1.20.1)
on Mar 19, 2025Fix config crash.
V1.3.2+1.20.1 (Forge 1.20.1)
on Mar 18, 2025V1.3.2+1.20.1 (Fabric 1.20.1)
on Mar 18, 2025Fix crash on dedicated servers.
V1.3.1+1.20.1 (Fabric 1.20.1)
on Mar 18, 2025V1.3.1+1.20.1 (Forge 1.20.1)
on Mar 18, 2025- Backport post-1.0.0 JamLib to 1.20.1
- Should still be compatible with mods that use pre-1.0.0 JamLib, as functionality from that is included.
V1.3.2+1.21.1 (NeoForge 1.21.1)
on Feb 26, 2025V1.3.2+1.21.1 (Fabric 1.21.1)
on Feb 26, 2025V1.3.2+1.21.3 (NeoForge 1.21.3)
on Feb 26, 2025V1.3.2+1.21.3 (Fabric 1.21.3)
on Feb 26, 2025V1.3.2+1.21.4 (NeoForge 1.21.4)
on Feb 26, 2025V1.3.2+1.21.4 (Fabric 1.21.4)
on Feb 26, 2025Fix crash on dedicated servers.
V1.3.1+1.21.1 (NeoForge 1.21.1)
on Feb 26, 2025V1.3.1+1.21.1 (Fabric 1.21.1)
on Feb 26, 2025- Ensure inherited fields are present in config GUIs (closes #13).
- When both a mod ID and config file name are specified, the config file is now saved under
config/{mod id}/{config name}.json5(closes #12).- This should not be a breaking change as I am not aware of any mods registering multiple configs currently.
- Switch to fabric-api mod ID in dependencies block (closes #10).
- Enable split source sets (closes #14).
- Identify config managers by
(MOD_ID, CONFIG_NAME)rather than by just(CONFIG_NAME)(closes #15). - Allow
List<?>config fields (closes #11). - The reset button next to each config field now resets to the default value, rather than the value the field had when the config screen was opened.
V1.3.1+1.21.4 (Fabric 1.21.4)
on Feb 26, 2025V1.3.1+1.21.4 (NeoForge 1.21.4)
on Feb 26, 2025- Undo accidentally API breakage of client lifecycle events.
V1.3.1+1.21.3 (Fabric 1.21.3)
on Feb 26, 2025V1.3.1+1.21.3 (NeoForge 1.21.3)
on Feb 26, 2025- Ensure inherited fields are present in config GUIs (closes #13).
- When both a mod ID and config file name are specified, the config file is now saved under
config/{mod id}/{config name}.json5(closes #12).- This should not be a breaking change as I am not aware of any mods registering multiple configs currently.
- Switch to fabric-api mod ID in dependencies block (closes #10).
- Enable split source sets (closes #14).
- Identify config managers by
(MOD_ID, CONFIG_NAME)rather than by just(CONFIG_NAME)(closes #15). - Allow
List<?>config fields (closes #11). - The reset button next to each config field now resets to the default value, rather than the value the field had when the config screen was opened.
V1.3.0+1.21.4 (Fabric 1.21.4)
on Feb 26, 2025V1.3.0+1.21.4 (NeoForge 1.21.4)
on Feb 26, 2025- Ensure inherited fields are present in config GUIs (closes #13).
- When both a mod ID and config file name are specified, the config file is now saved under
config/{mod id}/{config name}.json5(closes #12).- This should not be a breaking change as I am not aware of any mods registering multiple configs currently.
- Switch to fabric-api mod ID in dependencies block (closes #10).
- Enable split source sets (closes #14).
- Identify config managers by
(MOD_ID, CONFIG_NAME)rather than by just(CONFIG_NAME)(closes #15). - Allow
List<?>config fields (closes #11). - The reset button next to each config field now resets to the default value, rather than the value the field had when the config screen was opened.