
![]()
![]()
![]()
Forge Config API Port is a developer library that brings the Forge and NeoForge configuration systems to other mod loaders. It allows mods to use familiar Forge or NeoForge style configs across Fabric, Forge, and NeoForge without maintaining separate configuration implementations. 📦
This mod is intended for mod developers and as a dependency for supported mods. It does not allow Forge mods to run on Fabric, nor does it provide any form of general mod compatibility between loaders. 🔧
By preserving the original APIs, package names, and behavior as closely as possible, the mod makes it easier to maintain multiloader projects and share configuration code between platforms. This helps reduce platform-specific code and keeps configuration handling consistent across supported mod loaders. 🔄
![]()
![]()
![]()
![]()
⏩ INSTALLATION REQUIRED ON CLIENT & REQUIRED ON SERVER
⏩ REQUIRES FABRIC API TO BE INSTALLED (FABRIC)
![]()
![]()
🌟 Thanks to the Forge & NeoForge teams for creating and maintaining the configuration API this project is based on!
![]()
![]()
Optional
Optional
Условия использования, изменения и распространения этого товара.
21.06.2026 · Modrinth
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
Скриншоты и изображения из оригинальной страницы Modrinth.










Опубликованные версии и оригинальные файлы Modrinth.
21.06.2026 · 1 023 459 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
21.06.2026 · 3 961 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
21.06.2026 · 4 442 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
16.06.2026 · 167 361 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
16.06.2026 · 936 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
08.06.2026 · 862 861 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
accessWidener entry missing from fabric.mod.json (ArchLoom used to add that automatically lol)Common distribution that may arise from that08.06.2026 · 5 773 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
accessWidener entry missing from fabric.mod.json (ArchLoom used to add that automatically lol)Common distribution that may arise from that08.06.2026 · 5 595 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
accessWidener entry missing from fabric.mod.json (ArchLoom used to add that automatically lol)Common distribution that may arise from that26.04.2026 · 11 553 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
accessWidener entry missing from fabric.mod.json (ArchLoom used to add that automatically lol)Common distribution that may arise from that26.04.2026 · 1 192 041 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
accessWidener entry missing from fabric.mod.json (ArchLoom used to add that automatically lol)Common distribution that may arise from that26.04.2026 · 7 264 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
accessWidener entry missing from fabric.mod.json (ArchLoom used to add that automatically lol)Common distribution that may arise from that02.04.2026 · 545 024 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
accessWidener entry missing from fabric.mod.json (ArchLoom used to add that automatically lol)Common distribution that may arise from that02.04.2026 · 4 330 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
accessWidener entry missing from fabric.mod.json (ArchLoom used to add that automatically lol)Common distribution that may arise from that02.04.2026 · 3 282 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
accessWidener entry missing from fabric.mod.json (ArchLoom used to add that automatically lol)Common distribution that may arise from that28.03.2026 · 179 636 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
accessWidener entry missing from fabric.mod.json (ArchLoom used to add that automatically lol)Common distribution that may arise from that28.03.2026 · 1 220 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
accessWidener entry missing from fabric.mod.json (ArchLoom used to add that automatically lol)Common distribution that may arise from that28.03.2026 · 519 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
accessWidener entry missing from fabric.mod.json (ArchLoom used to add that automatically lol)Common distribution that may arise from that24.03.2026 · 102 181 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
accessWidener entry missing from fabric.mod.json (ArchLoom used to add that automatically lol)Common distribution that may arise from that24.03.2026 · 327 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
accessWidener entry missing from fabric.mod.json (ArchLoom used to add that automatically lol)Common distribution that may arise from that24.03.2026 · 3 179 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
Common distribution that may arise from that24.03.2026 · 177 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
Common distribution that may arise from that15.12.2025 · 5 954 605 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
15.12.2025 · 43 029 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
15.12.2025 · 42 183 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
11.12.2025 · 84 608 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
11.12.2025 · 2 301 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
25.11.2025 · 2 336 087 загрузки
All notable changes to this project will be documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/.
FileWatcher default instance on dedicated server exit12.11.2025 · 1 763 271 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.ParsingException when loading the internal mod config12.11.2025 · 15 266 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.ParsingException when loading the internal mod config12.11.2025 · 11 459 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.ParsingException when loading the internal mod config12.11.2025 · 5 482 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.ParsingException when loading the internal mod config12.11.2025 · 5 122 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.ParsingException when loading the internal mod config12.11.2025 · 2 070 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.ParsingException when loading the internal mod configcom.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config library/config command changes to be more inline with NeoForgeNeoForgeConfigRegistry & ForgeConfigRegistry into ConfigRegistry on FabricForgeModConfigEvents, use NeoForgeModConfigEvents instead which also works for Forge events on FabricNeoForgeConfigRegistry and ForgeConfigRegistry on Forge & NeoForge respectively12.11.2025 · 377 469 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.ParsingException when loading the internal mod config12.11.2025 · 2 171 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.ParsingException when loading the internal mod configcom.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config library/config command changes to be more inline with NeoForgeNeoForgeConfigRegistry & ForgeConfigRegistry into ConfigRegistry on FabricForgeModConfigEvents, use NeoForgeModConfigEvents instead which also works for Forge events on FabricNeoForgeConfigRegistry and ForgeConfigRegistry on Forge & NeoForge respectively12.11.2025 · 178 642 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.ParsingException when loading the internal mod configcom.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config library/config command changes to be more inline with NeoForgeNeoForgeConfigRegistry & ForgeConfigRegistry into ConfigRegistry on FabricForgeModConfigEvents, use NeoForgeModConfigEvents instead which also works for Forge events on FabricNeoForgeConfigRegistry and ForgeConfigRegistry on Forge & NeoForge respectively12.11.2025 · 10 043 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.ParsingException when loading the internal mod configcom.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config libraryFileWatcher default instance on dedicated server exit12.11.2025 · 13 575 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.ParsingException when loading the internal mod configcom.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config libraryFileWatcher default instance on dedicated server exit12.11.2025 · 520 740 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.ParsingException when loading the internal mod configcom.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config libraryFileWatcher default instance on dedicated server exit12.11.2025 · 1 043 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.ParsingException when loading the internal mod configcom.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config libraryFileWatcher default instance on dedicated server exitForgeConfigSpec::save12.11.2025 · 5 984 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.ParsingException when loading the internal mod configcom.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config libraryFileWatcher default instance on dedicated server exitForgeConfigSpec::save12.11.2025 · 36 104 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.ParsingException when loading the internal mod configcom.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config libraryFileWatcher default instance on dedicated server exitForgeConfigSpec::save12.11.2025 · 345 829 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.ParsingException when loading the internal mod configModConfigSpec from upstreamcom.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) inFileWatcher default instance on dedicated server exitForgeConfigSpec::save12.11.2025 · 69 368 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.ParsingException when loading the internal mod configModConfigSpec from upstreamcom.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) inFileWatcher default instance on dedicated server exitForgeConfigSpec::save12.11.2025 · 5 117 909 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.ParsingException when loading the internal mod configModConfigSpec from upstreamcom.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) inFileWatcher default instance on dedicated server exitForgeConfigSpec::save09.11.2025 · 4 404 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
ModConfigSpec from upstreamcom.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) inFileWatcher default instance on dedicated server exitForgeConfigSpec::save09.11.2025 · 833 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
ModConfigSpec from upstreamcom.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) inFileWatcher default instance on dedicated server exitForgeConfigSpec::save09.11.2025 · 50 882 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
ModConfigSpec from upstreamcom.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) inFileWatcher default instance on dedicated server exitForgeConfigSpec::save08.10.2025 · 812 248 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
08.10.2025 · 5 106 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
08.10.2025 · 5 768 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
04.10.2025 · 13 964 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
Failed to process jar when running jar processor: fabric-loom:access-widenerjar task instead of remapJar04.10.2025 · 183 789 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
Failed to process jar when running jar processor: fabric-loom:access-widenerjar task instead of remapJar04.10.2025 · 1 249 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
Failed to process jar when running jar processor: fabric-loom:access-widenerjar task instead of remapJar02.10.2025 · 57 467 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
Failed to process jar when running jar processor: fabric-loom:access-widenerjar task instead of remapJar02.10.2025 · 355 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
Failed to process jar when running jar processor: fabric-loom:access-widenerjar task instead of remapJar02.10.2025 · 341 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
Failed to process jar when running jar processor: fabric-loom:access-widenerjar task instead of remapJar01.10.2025 · 19 676 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
Failed to process jar when running jar processor: fabric-loom:access-widenerjar task instead of remapJar01.10.2025 · 204 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
Failed to process jar when running jar processor: fabric-loom:access-widenerjar task instead of remapJar29.08.2025 · 25 939 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
29.08.2025 · 7 770 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
29.08.2025 · 993 660 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
22.07.2025 · 11 949 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config libraryFileWatcher default instance on dedicated server exit22.07.2025 · 11 741 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config libraryFileWatcher default instance on dedicated server exit22.07.2025 · 263 808 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config libraryFileWatcher default instance on dedicated server exit22.07.2025 · 707 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config libraryFileWatcher default instance on dedicated server exitForgeConfigSpec::save22.07.2025 · 1 395 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config libraryFileWatcher default instance on dedicated server exitForgeConfigSpec::save22.07.2025 · 13 228 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config libraryFileWatcher default instance on dedicated server exitForgeConfigSpec::save22.07.2025 · 170 361 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config libraryFileWatcher default instance on dedicated server exitForgeConfigSpec::save 22.07.2025 · 30 043 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config libraryFileWatcher default instance on dedicated server exitForgeConfigSpec::save 22.07.2025 · 2 095 190 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config libraryFileWatcher default instance on dedicated server exitForgeConfigSpec::save 18.07.2025 · 6 756 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
18.07.2025 · 5 795 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
18.07.2025 · 849 155 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
01.07.2025 · 5 019 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
01.07.2025 · 3 024 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
01.07.2025 · 424 681 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
24.06.2025 · 4 335 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
MixinTargetAlreadyLoadedException for the previously introduced Night Config workaroundcom.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config library24.06.2025 · 2 471 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
MixinTargetAlreadyLoadedException for the previously introduced Night Config workaroundcom.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config library24.06.2025 · 381 981 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
MixinTargetAlreadyLoadedException for the previously introduced Night Config workaroundcom.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config library23.06.2025 · 123 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config library23.06.2025 · 136 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config library23.06.2025 · 3 885 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
com.electronwill.nightconfig.core.io.WritingException: Failed to write (REPLACE_ATOMIC) in the Night Config library18.06.2025 · 475 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
18.06.2025 · 504 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
18.06.2025 · 85 938 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
17.06.2025 · 158 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
17.06.2025 · 5 090 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
27.03.2025 · 24 972 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
/config command changes to be more inline with NeoForgeNeoForgeConfigRegistry & ForgeConfigRegistry into ConfigRegistry on FabricForgeModConfigEvents, use NeoForgeModConfigEvents instead which also works for Forge events on FabricNeoForgeConfigRegistry and ForgeConfigRegistry on Forge & NeoForge respectively27.03.2025 · 10 735 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
/config command changes to be more inline with NeoForgeNeoForgeConfigRegistry & ForgeConfigRegistry into ConfigRegistry on FabricForgeModConfigEvents, use NeoForgeModConfigEvents instead which also works for Forge events on FabricNeoForgeConfigRegistry and ForgeConfigRegistry on Forge & NeoForge respectively27.03.2025 · 1 690 120 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
/config command changes to be more inline with NeoForgeNeoForgeConfigRegistry & ForgeConfigRegistry into ConfigRegistry on FabricForgeModConfigEvents, use NeoForgeModConfigEvents instead which also works for Forge events on FabricNeoForgeConfigRegistry and ForgeConfigRegistry on Forge & NeoForge respectively25.03.2025 · 377 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
NeoForgeConfigRegistry & ForgeConfigRegistry into ConfigRegistry on FabricForgeModConfigEvents, use NeoForgeModConfigEvents instead which also works for Forge events on FabricNeoForgeConfigRegistry and ForgeConfigRegistry on Forge & NeoForge respectively25.03.2025 · 20 275 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
NeoForgeConfigRegistry & ForgeConfigRegistry into ConfigRegistry on FabricForgeModConfigEvents, use NeoForgeModConfigEvents instead which also works for Forge events on FabricNeoForgeConfigRegistry and ForgeConfigRegistry on Forge & NeoForge respectively20.03.2025 · 3 802 632 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
FileWatcher default instance on dedicated server exit11.12.2024 · 13 627 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
FileWatcher default instance on dedicated server exit11.12.2024 · 31 357 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
FileWatcher default instance on dedicated server exit11.12.2024 · 2 052 307 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
FileWatcher default instance on dedicated server exit11.12.2024 · 860 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
FileWatcher default instance on dedicated server exitForgeConfigSpec::save11.12.2024 · 2 977 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
FileWatcher default instance on dedicated server exitForgeConfigSpec::save11.12.2024 · 99 884 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
FileWatcher default instance on dedicated server exitForgeConfigSpec::save11.12.2024 · 294 697 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
FileWatcher default instance on dedicated server exitForgeConfigSpec::save 11.12.2024 · 33 033 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
FileWatcher default instance on dedicated server exitForgeConfigSpec::save 11.12.2024 · 2 908 174 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
FileWatcher default instance on dedicated server exitForgeConfigSpec::save 05.12.2024 · 756 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
05.12.2024 · 45 352 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
15.11.2024 · 968 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
ForgeConfigSpec::save15.11.2024 · 867 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
ForgeConfigSpec::save15.11.2024 · 112 290 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
ForgeConfigSpec::save15.11.2024 · 9 047 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
ForgeConfigSpec::save 15.11.2024 · 1 291 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
ForgeConfigSpec::save 15.11.2024 · 1 048 052 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
ForgeConfigSpec::save 14.11.2024 · 3 655 399 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
27.10.2024 · 555 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
27.10.2024 · 621 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
27.10.2024 · 44 273 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
24.10.2024 · 239 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
24.10.2024 · 2 795 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
30.09.2024 · 6 191 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
30.09.2024 · 3 653 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
30.09.2024 · 341 364 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
09.08.2024 · 5 329 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
09.08.2024 · 17 223 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
09.08.2024 · 108 762 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
07.08.2024 · 20 341 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
ConfigScreenFactoryRegistry::registernet.minecraftforge.fml.config.ModConfig::save to still be usablenet.minecraftforge.fml.config.ModConfig::getFullPath throwing a ClassCastExceptionModConfig as it is still used in config events, it now serves as an adapter to NeoForge's ModConfig for registered Forge configs07.08.2024 · 40 891 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
ConfigScreenFactoryRegistry::registernet.minecraftforge.fml.config.ModConfig::save to still be usablenet.minecraftforge.fml.config.ModConfig::getFullPath throwing a ClassCastExceptionModConfig as it is still used in config events, it now serves as an adapter to NeoForge's ModConfig for registered Forge configs07.08.2024 · 1 077 742 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
ConfigScreenFactoryRegistry::registernet.minecraftforge.fml.config.ModConfig::save to still be usablenet.minecraftforge.fml.config.ModConfig::getFullPath throwing a ClassCastExceptionModConfig as it is still used in config events, it now serves as an adapter to NeoForge's ModConfig for registered Forge configs29.07.2024 · 1 511 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
ConfigScreenFactoryRegistry::registernet.minecraftforge.fml.config.ModConfig::save to still be usablenet.minecraftforge.fml.config.ModConfig::getFullPath throwing a ClassCastExceptionModConfig as it is still used in config events, it now serves as an adapter to NeoForge's ModConfig for registered Forge configs29.07.2024 · 1 473 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
ConfigScreenFactoryRegistry::registernet.minecraftforge.fml.config.ModConfig::save to still be usablenet.minecraftforge.fml.config.ModConfig::getFullPath throwing a ClassCastExceptionModConfig as it is still used in config events, it now serves as an adapter to NeoForge's ModConfig for registered Forge configs29.07.2024 · 59 440 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
ConfigScreenFactoryRegistry::registernet.minecraftforge.fml.config.ModConfig::save to still be usablenet.minecraftforge.fml.config.ModConfig::getFullPath throwing a ClassCastExceptionModConfig as it is still used in config events, it now serves as an adapter to NeoForge's ModConfig for registered Forge configs26.07.2024 · 519 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
ConfigScreenFactoryRegistry::registernet.minecraftforge.fml.config.ModConfig::save to still be usablenet.minecraftforge.fml.config.ModConfig::getFullPath throwing a ClassCastExceptionModConfig as it is still used in config events, it now serves as an adapter to NeoForge's ModConfig for registered Forge configs26.07.2024 · 603 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
ConfigScreenFactoryRegistry::registernet.minecraftforge.fml.config.ModConfig::save to still be usablenet.minecraftforge.fml.config.ModConfig::getFullPath throwing a ClassCastExceptionModConfig as it is still used in config events, it now serves as an adapter to NeoForge's ModConfig for registered Forge configs26.07.2024 · 22 835 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
ConfigScreenFactoryRegistry::registernet.minecraftforge.fml.config.ModConfig::save to still be usablenet.minecraftforge.fml.config.ModConfig::getFullPath throwing a ClassCastExceptionModConfig as it is still used in config events, it now serves as an adapter to NeoForge's ModConfig for registered Forge configs15.07.2024 · 1 459 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
net.minecraftforge.fml.config.ModConfig::save to still be usablenet.minecraftforge.fml.config.ModConfig::getFullPath throwing a ClassCastExceptionModConfig as it is still used in config events, it now serves as an adapter to NeoForge's ModConfig for registered Forge configs15.07.2024 · 72 118 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
net.minecraftforge.fml.config.ModConfig::save to still be usablenet.minecraftforge.fml.config.ModConfig::getFullPath throwing a ClassCastExceptionModConfig as it is still used in config events, it now serves as an adapter to NeoForge's ModConfig for registered Forge configs15.07.2024 · 140 089 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
net.minecraftforge.fml.config.ModConfig::save to still be usablenet.minecraftforge.fml.config.ModConfig::getFullPath throwing a ClassCastExceptionModConfig as it is still used in config events, it now serves as an adapter to NeoForge's ModConfig for registered Forge configs15.07.2024 · 167 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
net.minecraftforge.fml.config.ModConfig::getFullPath throwing a ClassCastExceptionModConfig as it is still used in config events, it now serves as an adapter to NeoForge's ModConfig for registered Forge configs15.07.2024 · 189 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
net.minecraftforge.fml.config.ModConfig::getFullPath throwing a ClassCastExceptionModConfig as it is still used in config events, it now serves as an adapter to NeoForge's ModConfig for registered Forge configs15.07.2024 · 3 569 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
net.minecraftforge.fml.config.ModConfig::getFullPath throwing a ClassCastExceptionModConfig as it is still used in config events, it now serves as an adapter to NeoForge's ModConfig for registered Forge configs15.07.2024 · 518 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
ModConfig as it is still used in config events, it now serves as an adapter to NeoForge's ModConfig for registered Forge configs15.07.2024 · 276 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
ModConfig as it is still used in config events, it now serves as an adapter to NeoForge's ModConfig for registered Forge configs15.07.2024 · 7 662 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
ModConfig as it is still used in config events, it now serves as an adapter to NeoForge's ModConfig for registered Forge configs13.07.2024 · 346 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
13.07.2024 · 304 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
13.07.2024 · 9 890 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.
01.07.2024 · 1 051 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
01.07.2024 · 894 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
01.07.2024 · 49 188 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
14.06.2024 · 1 638 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
14.06.2024 · 167 882 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
04.06.2024 · 8 642 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
recreateConfigsWhenParsingFails and forceGlobalServerConfigs which are always enabled nowForgeConfigSpec and ModConfigSpec 04.06.2024 · 25 282 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
recreateConfigsWhenParsingFails and forceGlobalServerConfigs which are always enabled nowForgeConfigSpec and ModConfigSpec 04.06.2024 · 122 848 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
recreateConfigsWhenParsingFails and forceGlobalServerConfigs which are always enabled nowForgeConfigSpec and ModConfigSpec 01.05.2024 · 3 470 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
ForgeConfigSpec and ModConfigSpec 30.04.2024 · 395 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
ForgeConfigSpec and ModConfigSpec 30.04.2024 · 75 431 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
ForgeConfigSpec and ModConfigSpec 22.01.2024 · 15 924 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
mods.toml entries for NeoForgeUnmodifiableConfigWrapper for IConfigSpec adapters on NeoForge & Forgefuzs.forgeconfigapiport.api.config into fuzs.forgeconfigapiport.fabric.api.forge and fuzs.forgeconfigapiport.fabric.api.neoforgeforgeconfigapiport-common, instead there are now two common publications which are forgeconfigapiport-common-forgeapi and forgeconfigapiport-common-neoforgeapidisableConfigWatcher config option to both ForgeConfigSpec and ModConfigSpecFileWatcher hanging due to an invalid path when unloading server configs22.01.2024 · 43 143 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
mods.toml entries for NeoForgeUnmodifiableConfigWrapper for IConfigSpec adapters on NeoForge & Forgefuzs.forgeconfigapiport.api.config into fuzs.forgeconfigapiport.fabric.api.forge and fuzs.forgeconfigapiport.fabric.api.neoforgeforgeconfigapiport-common, instead there are now two common publications which are forgeconfigapiport-common-forgeapi and forgeconfigapiport-common-neoforgeapidisableConfigWatcher config option to both ForgeConfigSpec and ModConfigSpecFileWatcher hanging due to an invalid path when unloading server configs22.01.2024 · 754 292 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
mods.toml entries for NeoForgeUnmodifiableConfigWrapper for IConfigSpec adapters on NeoForge & Forgefuzs.forgeconfigapiport.api.config into fuzs.forgeconfigapiport.fabric.api.forge and fuzs.forgeconfigapiport.fabric.api.neoforgeforgeconfigapiport-common, instead there are now two common publications which are forgeconfigapiport-common-forgeapi and forgeconfigapiport-common-neoforgeapidisableConfigWatcher config option to both ForgeConfigSpec and ModConfigSpecFileWatcher hanging due to an invalid path when unloading server configs22.01.2024 · 32 467 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
mods.toml entries for NeoForgeUnmodifiableConfigWrapper for IConfigSpec adapters on NeoForge & Forgefuzs.forgeconfigapiport.api.config into fuzs.forgeconfigapiport.fabric.api.forge and fuzs.forgeconfigapiport.fabric.api.neoforgeforgeconfigapiport-common, instead there are now two common publications which are forgeconfigapiport-common-forgeapi and forgeconfigapiport-common-neoforgeapidisableConfigWatcher config option to both ForgeConfigSpec and ModConfigSpecFileWatcher hanging due to an invalid path when unloading server configs.minecraft/config directoryfuzs.forgeconfigapiport.api.config.v3.ForgeConfigPathsModConfigSpec using a wrong packageForgeConfigSpec still using the old name for NeoForgenet.neoforged namespace in addition to net.minecraftforge/config command which now only works for NeoForge configs22.01.2024 · 1 165 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
mods.toml entries for NeoForgeUnmodifiableConfigWrapper for IConfigSpec adapters on NeoForge & Forgefuzs.forgeconfigapiport.api.config into fuzs.forgeconfigapiport.fabric.api.forge and fuzs.forgeconfigapiport.fabric.api.neoforgeforgeconfigapiport-common, instead there are now two common publications which are forgeconfigapiport-common-forgeapi and forgeconfigapiport-common-neoforgeapidisableConfigWatcher config option to both ForgeConfigSpec and ModConfigSpecFileWatcher hanging due to an invalid path when unloading server configs.minecraft/config directoryfuzs.forgeconfigapiport.api.config.v3.ForgeConfigPathsModConfigSpec using a wrong packageForgeConfigSpec still using the old name for NeoForgenet.neoforged namespace in addition to net.minecraftforge/config command which now only works for NeoForge configs22.01.2024 · 105 894 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
mods.toml entries for NeoForgeUnmodifiableConfigWrapper for IConfigSpec adapters on NeoForge & Forgefuzs.forgeconfigapiport.api.config into fuzs.forgeconfigapiport.fabric.api.forge and fuzs.forgeconfigapiport.fabric.api.neoforgeforgeconfigapiport-common, instead there are now two common publications which are forgeconfigapiport-common-forgeapi and forgeconfigapiport-common-neoforgeapidisableConfigWatcher config option to both ForgeConfigSpec and ModConfigSpecFileWatcher hanging due to an invalid path when unloading server configs.minecraft/config directoryfuzs.forgeconfigapiport.api.config.v3.ForgeConfigPathsModConfigSpec using a wrong packageForgeConfigSpec still using the old name for NeoForgenet.neoforged namespace in addition to net.minecraftforge/config command which now only works for NeoForge configs13.01.2024 · 627 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
UnmodifiableConfigWrapper for IConfigSpec adapters on NeoForge & Forgefuzs.forgeconfigapiport.api.config into fuzs.forgeconfigapiport.fabric.api.forge and fuzs.forgeconfigapiport.fabric.api.neoforgeforgeconfigapiport-common, instead there are now two common publications which are forgeconfigapiport-common-forgeapi and forgeconfigapiport-common-neoforgeapidisableConfigWatcher config option to both ForgeConfigSpec and ModConfigSpecFileWatcher hanging due to an invalid path when unloading server configs13.01.2024 · 888 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
UnmodifiableConfigWrapper for IConfigSpec adapters on NeoForge & Forgefuzs.forgeconfigapiport.api.config into fuzs.forgeconfigapiport.fabric.api.forge and fuzs.forgeconfigapiport.fabric.api.neoforgeforgeconfigapiport-common, instead there are now two common publications which are forgeconfigapiport-common-forgeapi and forgeconfigapiport-common-neoforgeapidisableConfigWatcher config option to both ForgeConfigSpec and ModConfigSpecFileWatcher hanging due to an invalid path when unloading server configs13.01.2024 · 17 235 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
UnmodifiableConfigWrapper for IConfigSpec adapters on NeoForge & Forgefuzs.forgeconfigapiport.api.config into fuzs.forgeconfigapiport.fabric.api.forge and fuzs.forgeconfigapiport.fabric.api.neoforgeforgeconfigapiport-common, instead there are now two common publications which are forgeconfigapiport-common-forgeapi and forgeconfigapiport-common-neoforgeapidisableConfigWatcher config option to both ForgeConfigSpec and ModConfigSpecFileWatcher hanging due to an invalid path when unloading server configs13.01.2024 · 218 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
UnmodifiableConfigWrapper for IConfigSpec adapters on NeoForge & Forgefuzs.forgeconfigapiport.api.config into fuzs.forgeconfigapiport.fabric.api.forge and fuzs.forgeconfigapiport.fabric.api.neoforgeforgeconfigapiport-common, instead there are now two common publications which are forgeconfigapiport-common-forgeapi and forgeconfigapiport-common-neoforgeapidisableConfigWatcher config option to both ForgeConfigSpec and ModConfigSpecFileWatcher hanging due to an invalid path when unloading server configs.minecraft/config directoryfuzs.forgeconfigapiport.api.config.v3.ForgeConfigPathsModConfigSpec using a wrong packageForgeConfigSpec still using the old name for NeoForgenet.neoforged namespace in addition to net.minecraftforge/config command which now only works for NeoForge configs13.01.2024 · 1 754 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
UnmodifiableConfigWrapper for IConfigSpec adapters on NeoForge & Forgefuzs.forgeconfigapiport.api.config into fuzs.forgeconfigapiport.fabric.api.forge and fuzs.forgeconfigapiport.fabric.api.neoforgeforgeconfigapiport-common, instead there are now two common publications which are forgeconfigapiport-common-forgeapi and forgeconfigapiport-common-neoforgeapidisableConfigWatcher config option to both ForgeConfigSpec and ModConfigSpecFileWatcher hanging due to an invalid path when unloading server configs.minecraft/config directoryfuzs.forgeconfigapiport.api.config.v3.ForgeConfigPathsModConfigSpec using a wrong packageForgeConfigSpec still using the old name for NeoForgenet.neoforged namespace in addition to net.minecraftforge/config command which now only works for NeoForge configs13.01.2024 · 4 002 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
UnmodifiableConfigWrapper for IConfigSpec adapters on NeoForge & Forgefuzs.forgeconfigapiport.api.config into fuzs.forgeconfigapiport.fabric.api.forge and fuzs.forgeconfigapiport.fabric.api.neoforgeforgeconfigapiport-common, instead there are now two common publications which are forgeconfigapiport-common-forgeapi and forgeconfigapiport-common-neoforgeapidisableConfigWatcher config option to both ForgeConfigSpec and ModConfigSpecFileWatcher hanging due to an invalid path when unloading server configs.minecraft/config directoryfuzs.forgeconfigapiport.api.config.v3.ForgeConfigPathsModConfigSpec using a wrong packageForgeConfigSpec still using the old name for NeoForgenet.neoforged namespace in addition to net.minecraftforge/config command which now only works for NeoForge configs10.01.2024 · 195 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
fuzs.forgeconfigapiport.api.config into fuzs.forgeconfigapiport.fabric.api.forge and fuzs.forgeconfigapiport.fabric.api.neoforgeforgeconfigapiport-common, instead there are now two common publications which are forgeconfigapiport-common-forgeapi and forgeconfigapiport-common-neoforgeapidisableConfigWatcher config option to both ForgeConfigSpec and ModConfigSpecFileWatcher hanging due to an invalid path when unloading server configs.minecraft/config directoryfuzs.forgeconfigapiport.api.config.v3.ForgeConfigPathsModConfigSpec using a wrong packageForgeConfigSpec still using the old name for NeoForgenet.neoforged namespace in addition to net.minecraftforge/config command which now only works for NeoForge configs10.01.2024 · 3 450 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
fuzs.forgeconfigapiport.api.config into fuzs.forgeconfigapiport.fabric.api.forge and fuzs.forgeconfigapiport.fabric.api.neoforgeforgeconfigapiport-common, instead there are now two common publications which are forgeconfigapiport-common-forgeapi and forgeconfigapiport-common-neoforgeapidisableConfigWatcher config option to both ForgeConfigSpec and ModConfigSpecFileWatcher hanging due to an invalid path when unloading server configs.minecraft/config directoryfuzs.forgeconfigapiport.api.config.v3.ForgeConfigPathsModConfigSpec using a wrong packageForgeConfigSpec still using the old name for NeoForgenet.neoforged namespace in addition to net.minecraftforge/config command which now only works for NeoForge configs10.01.2024 · 1 710 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
fuzs.forgeconfigapiport.api.config into fuzs.forgeconfigapiport.fabric.api.forge and fuzs.forgeconfigapiport.fabric.api.neoforgeforgeconfigapiport-common, instead there are now two common publications which are forgeconfigapiport-common-forgeapi and forgeconfigapiport-common-neoforgeapidisableConfigWatcher config option to both ForgeConfigSpec and ModConfigSpecFileWatcher hanging due to an invalid path when unloading server configs.minecraft/config directoryfuzs.forgeconfigapiport.api.config.v3.ForgeConfigPathsModConfigSpec using a wrong packageForgeConfigSpec still using the old name for NeoForgenet.neoforged namespace in addition to net.minecraftforge/config command which now only works for NeoForge configs10.01.2024 · 323 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
fuzs.forgeconfigapiport.api.config into fuzs.forgeconfigapiport.fabric.api.forge and fuzs.forgeconfigapiport.fabric.api.neoforgeforgeconfigapiport-common, instead there are now two common publications which are forgeconfigapiport-common-forgeapi and forgeconfigapiport-common-neoforgeapidisableConfigWatcher config option to both ForgeConfigSpec and ModConfigSpecFileWatcher hanging due to an invalid path when unloading server configs10.01.2024 · 1 971 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
fuzs.forgeconfigapiport.api.config into fuzs.forgeconfigapiport.fabric.api.forge and fuzs.forgeconfigapiport.fabric.api.neoforgeforgeconfigapiport-common, instead there are now two common publications which are forgeconfigapiport-common-forgeapi and forgeconfigapiport-common-neoforgeapidisableConfigWatcher config option to both ForgeConfigSpec and ModConfigSpecFileWatcher hanging due to an invalid path when unloading server configs10.01.2024 · 5 791 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
fuzs.forgeconfigapiport.api.config into fuzs.forgeconfigapiport.fabric.api.forge and fuzs.forgeconfigapiport.fabric.api.neoforgeforgeconfigapiport-common, instead there are now two common publications which are forgeconfigapiport-common-forgeapi and forgeconfigapiport-common-neoforgeapidisableConfigWatcher config option to both ForgeConfigSpec and ModConfigSpecFileWatcher hanging due to an invalid path when unloading server configs21.12.2023 · 46 392 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
.minecraft/config directoryfuzs.forgeconfigapiport.api.config.v3.ForgeConfigPathsModConfigSpec using a wrong packageForgeConfigSpec still using the old name for NeoForgenet.neoforged namespace in addition to net.minecraftforge/config command which now only works for NeoForge configs02.12.2023 · 31 923 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
.minecraft/config directoryfuzs.forgeconfigapiport.api.config.v3.ForgeConfigPathsModConfigSpec using a wrong packageForgeConfigSpec still using the old name for NeoForgenet.neoforged namespace in addition to net.minecraftforge/config command which now only works for NeoForge configs01.12.2023 · 1 481 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
ForgeConfigSpec still using the old name for NeoForgenet.neoforged namespace in addition to net.minecraftforge/config command which now only works for NeoForge configs30.11.2023 · 573 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
net.neoforged namespace in addition to net.minecraftforge/config command which now only works for NeoForge configs21.09.2023 · 92 596 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
12.06.2023 · 7 788 609 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
fabric.mod.json, which was causing issues in developement environments when Night Config wasn't retrieved from the official Maven, but instead production jars were used, e.g. from the Curse Mavennet.minecraftforge.api package10.06.2023 · 107 231 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
fabric.mod.json, which was causing issues in developement environments when Night Config wasn't retrieved from the official Maven, but instead production jars were used, e.g. from the Curse Mavennet.minecraftforge.api package09.06.2023 · 740 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
fabric.mod.json, which was causing issues in developement environments when Night Config wasn't retrieved from the official Maven, but instead production jars were used, e.g. from the Curse Mavennet.minecraftforge.api package09.06.2023 · 337 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
fabric.mod.json, which was causing issues in developement environments when Night Config wasn't retrieved from the official Maven, but instead production jars were used, e.g. from the Curse Mavennet.minecraftforge.api package09.06.2023 · 4 181 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
fabric.mod.json, which was causing issues in developement environments when Night Config wasn't retrieved from the official Maven, but instead production jars were used, e.g. from the Curse Mavennet.minecraftforge.api package22.03.2023 · 154 946 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
javax.annotation.Nullable with org.jetbrains.annotations.Nullablefuzs.forgeconfigapiport.api.config.v2.ForgeConfigPaths22.03.2023 · 29 715 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
correctConfigValuesFromDefaultConfig option from Night Config Fixes moddefaultconfigs instead of using built-in default values /config command now is registered as a client-side command to prevent issues with local multiplayer when vanilla clients are trying to connect (thanks for the suggestion DJtheRedstoner!)disableConfigCommand config option has become obsolete and was therefore removed/config command itselffuzs.forgeconfigapiport.impl.util.ReflectionHelper to fix crash with the Configured mod when editing a value that does not have a valid net.minecraftforge.common.ForgeConfigSpec$RangeServerLifecycleEvents#SERVER_STARTING callback, and are unloaded after everything in ServerLifecycleEvents#SERVER_STOPPED via custom event phases (thanks to SquidDev!)fabric.mod.jsonThis version includes major changes and refactors regarding the whole structure of Forge Config Api Port, most notably a reorganization into a multi-loader project (with separate publications for a common and Fabric Gradle project); as well as moving all classes and code not present on Forge to a separate domain (fuzs.forgeconfigapiport).
defaultsconfigs directory (just like Forge, not that it's too useful).minecraft/config/), so those configs are no longer world specific, but can be accessed much easier by users/config command for opening local config files from being registered, intended to be used when hosting a LAN world to allow clients without this mod to connectcom.electronwill.nightconfig.core.io.ParsingException: Not enough data available (an issue when reading local config files from malformed/corrupted file, which apparently appears quite often)forgeconfigapiport-common and forgeconfigapiport-fabric. When developing a mod for Fabric only, simply keep using forgeconfigapiport-fabric, nothing different from before. But when developing a mod for both Forge and Fabric simultaneously using a multi-loader setup, forgeconfigapiport-common comes in handy for the common project, as it enables using most config related classes in that part of the project, really just config registration is what's left for the mod loader specific projects.fuzs.forgeconfigapiport with a similar structure to Fabric Api (divided into api, impl, and mixin)fuzs.forgeconfigapiport also is the new domain used for the Maven distributionapi package at net.minecraftforge.api has been moved to the new domain at fuzs.forgeconfigapiport.api and refactored:net.minecraftforge.api.ModLoadingContext -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigRegistry: Same as before, methods have been renamed from registerConfig to simply register though and registration needs an instance from ForgeConfigRegistry#INSTANCE.net.minecraftforge.api.ConfigPaths -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigPaths: Overhauled, includes helper methods for getting default paths for all config types, also provides the full file path, not just the directory name.net.minecraftforge.api.fml.event.config.ModConfigEvents -> fuzs.forgeconfigapiport.api.config.v2.ModConfigEvents: No changes, class has only been moved.fuzs.forgeconfigapiport.implfuzs.forgeconfigapiport.mixin16.03.2023 · 1 442 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
javax.annotation.Nullable with org.jetbrains.annotations.Nullablefuzs.forgeconfigapiport.api.config.v2.ForgeConfigPaths16.03.2023 · 650 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
fuzs.forgeconfigapiport.api.config.v2.ForgeConfigPaths16.03.2023 · 1 544 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
correctConfigValuesFromDefaultConfig option from Night Config Fixes moddefaultconfigs instead of using built-in default values /config command now is registered as a client-side command to prevent issues with local multiplayer when vanilla clients are trying to connect (thanks for the suggestion DJtheRedstoner!)disableConfigCommand config option has become obsolete and was therefore removed/config command itselffuzs.forgeconfigapiport.impl.util.ReflectionHelper to fix crash with the Configured mod when editing a value that does not have a valid net.minecraftforge.common.ForgeConfigSpec$RangeServerLifecycleEvents#SERVER_STARTING callback, and are unloaded after everything in ServerLifecycleEvents#SERVER_STOPPED via custom event phases (thanks to SquidDev!)fabric.mod.jsonThis version includes major changes and refactors regarding the whole structure of Forge Config Api Port, most notably a reorganization into a multi-loader project (with separate publications for a common and Fabric Gradle project); as well as moving all classes and code not present on Forge to a separate domain (fuzs.forgeconfigapiport).
defaultsconfigs directory (just like Forge, not that it's too useful).minecraft/config/), so those configs are no longer world specific, but can be accessed much easier by users/config command for opening local config files from being registered, intended to be used when hosting a LAN world to allow clients without this mod to connectcom.electronwill.nightconfig.core.io.ParsingException: Not enough data available (an issue when reading local config files from malformed/corrupted file, which apparently appears quite often)forgeconfigapiport-common and forgeconfigapiport-fabric. When developing a mod for Fabric only, simply keep using forgeconfigapiport-fabric, nothing different from before. But when developing a mod for both Forge and Fabric simultaneously using a multi-loader setup, forgeconfigapiport-common comes in handy for the common project, as it enables using most config related classes in that part of the project, really just config registration is what's left for the mod loader specific projects.fuzs.forgeconfigapiport with a similar structure to Fabric Api (divided into api, impl, and mixin)fuzs.forgeconfigapiport also is the new domain used for the Maven distributionapi package at net.minecraftforge.api has been moved to the new domain at fuzs.forgeconfigapiport.api and refactored:net.minecraftforge.api.ModLoadingContext -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigRegistry: Same as before, methods have been renamed from registerConfig to simply register though and registration needs an instance from ForgeConfigRegistry#INSTANCE.net.minecraftforge.api.ConfigPaths -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigPaths: Overhauled, includes helper methods for getting default paths for all config types, also provides the full file path, not just the directory name.net.minecraftforge.api.fml.event.config.ModConfigEvents -> fuzs.forgeconfigapiport.api.config.v2.ModConfigEvents: No changes, class has only been moved.fuzs.forgeconfigapiport.implfuzs.forgeconfigapiport.mixin18.02.2023 · 1 061 508 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
/config command making it fully client-side to fix issues with command argument serializationfuzs.forgeconfigapiport.impl.util.ReflectionHelper to fix crash with the Configured mod when editing a value that does not have a valid net.minecraftforge.common.ForgeConfigSpec$RangeModConfigEvents class which is the new way of handling mod config events (loading and reloading), to ensure config events are only accessed on a mod specific basisModConfigEvent class is now deprecated for removal in the next major release for 1.20@ApiStatus annotations to ensure mods are only accessing the parts of the library they are meant toimpl domainForgeConfigSpec changes from Forge05.02.2023 · 5 569 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
/config command now is registered as a client-side command to prevent issues with local multiplayer when vanilla clients are trying to connect (thanks for the suggestion DJtheRedstoner!)disableConfigCommand config option has become obsolete and was therefore removed/config command itselffuzs.forgeconfigapiport.impl.util.ReflectionHelper to fix crash with the Configured mod when editing a value that does not have a valid net.minecraftforge.common.ForgeConfigSpec$RangeServerLifecycleEvents#SERVER_STARTING callback, and are unloaded after everything in ServerLifecycleEvents#SERVER_STOPPED via custom event phases (thanks to SquidDev!)fabric.mod.jsonThis version includes major changes and refactors regarding the whole structure of Forge Config Api Port, most notably a reorganization into a multi-loader project (with separate publications for a common and Fabric Gradle project); as well as moving all classes and code not present on Forge to a separate domain (fuzs.forgeconfigapiport).
defaultsconfigs directory (just like Forge, not that it's too useful).minecraft/config/), so those configs are no longer world specific, but can be accessed much easier by users/config command for opening local config files from being registered, intended to be used when hosting a LAN world to allow clients without this mod to connectcom.electronwill.nightconfig.core.io.ParsingException: Not enough data available (an issue when reading local config files from malformed/corrupted file, which apparently appears quite often)forgeconfigapiport-common and forgeconfigapiport-fabric. When developing a mod for Fabric only, simply keep using forgeconfigapiport-fabric, nothing different from before. But when developing a mod for both Forge and Fabric simultaneously using a multi-loader setup, forgeconfigapiport-common comes in handy for the common project, as it enables using most config related classes in that part of the project, really just config registration is what's left for the mod loader specific projects.fuzs.forgeconfigapiport with a similar structure to Fabric Api (divided into api, impl, and mixin)fuzs.forgeconfigapiport also is the new domain used for the Maven distributionapi package at net.minecraftforge.api has been moved to the new domain at fuzs.forgeconfigapiport.api and refactored:net.minecraftforge.api.ModLoadingContext -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigRegistry: Same as before, methods have been renamed from registerConfig to simply register though and registration needs an instance from ForgeConfigRegistry#INSTANCE.net.minecraftforge.api.ConfigPaths -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigPaths: Overhauled, includes helper methods for getting default paths for all config types, also provides the full file path, not just the directory name.net.minecraftforge.api.fml.event.config.ModConfigEvents -> fuzs.forgeconfigapiport.api.config.v2.ModConfigEvents: No changes, class has only been moved.fuzs.forgeconfigapiport.implfuzs.forgeconfigapiport.mixin28.01.2023 · 1 424 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
/config command now is registered as a client-side command to prevent issues with local multiplayer when vanilla clients are trying to connect (thanks for the suggestion DJtheRedstoner!)disableConfigCommand config option has become obsolete and was therefore removed/config command itselffuzs.forgeconfigapiport.impl.util.ReflectionHelper to fix crash with the Configured mod when editing a value that does not have a valid net.minecraftforge.common.ForgeConfigSpec$RangeServerLifecycleEvents#SERVER_STARTING callback, and are unloaded after everything in ServerLifecycleEvents#SERVER_STOPPED via custom event phases (thanks to SquidDev!)fabric.mod.jsonThis version includes major changes and refactors regarding the whole structure of Forge Config Api Port, most notably a reorganization into a multi-loader project (with separate publications for a common and Fabric Gradle project); as well as moving all classes and code not present on Forge to a separate domain (fuzs.forgeconfigapiport).
defaultsconfigs directory (just like Forge, not that it's too useful).minecraft/config/), so those configs are no longer world specific, but can be accessed much easier by users/config command for opening local config files from being registered, intended to be used when hosting a LAN world to allow clients without this mod to connectcom.electronwill.nightconfig.core.io.ParsingException: Not enough data available (an issue when reading local config files from malformed/corrupted file, which apparently appears quite often)forgeconfigapiport-common and forgeconfigapiport-fabric. When developing a mod for Fabric only, simply keep using forgeconfigapiport-fabric, nothing different from before. But when developing a mod for both Forge and Fabric simultaneously using a multi-loader setup, forgeconfigapiport-common comes in handy for the common project, as it enables using most config related classes in that part of the project, really just config registration is what's left for the mod loader specific projects.fuzs.forgeconfigapiport with a similar structure to Fabric Api (divided into api, impl, and mixin)fuzs.forgeconfigapiport also is the new domain used for the Maven distributionapi package at net.minecraftforge.api has been moved to the new domain at fuzs.forgeconfigapiport.api and refactored:net.minecraftforge.api.ModLoadingContext -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigRegistry: Same as before, methods have been renamed from registerConfig to simply register though and registration needs an instance from ForgeConfigRegistry#INSTANCE.net.minecraftforge.api.ConfigPaths -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigPaths: Overhauled, includes helper methods for getting default paths for all config types, also provides the full file path, not just the directory name.net.minecraftforge.api.fml.event.config.ModConfigEvents -> fuzs.forgeconfigapiport.api.config.v2.ModConfigEvents: No changes, class has only been moved.fuzs.forgeconfigapiport.implfuzs.forgeconfigapiport.mixin09.01.2023 · 2 474 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
fuzs.forgeconfigapiport.impl.util.ReflectionHelper to fix crash with the Configured mod when editing a value that does not have a valid net.minecraftforge.common.ForgeConfigSpec$RangeServerLifecycleEvents#SERVER_STARTING callback, and are unloaded after everything in ServerLifecycleEvents#SERVER_STOPPED via custom event phases (thanks to SquidDev!)fabric.mod.jsonThis version includes major changes and refactors regarding the whole structure of Forge Config Api Port, most notably a reorganization into a multi-loader project (with separate publications for a common and Fabric Gradle project); as well as moving all classes and code not present on Forge to a separate domain (fuzs.forgeconfigapiport).
defaultsconfigs directory (just like Forge, not that it's too useful).minecraft/config/), so those configs are no longer world specific, but can be accessed much easier by users/config command for opening local config files from being registered, intended to be used when hosting a LAN world to allow clients without this mod to connectcom.electronwill.nightconfig.core.io.ParsingException: Not enough data available (an issue when reading local config files from malformed/corrupted file, which apparently appears quite often)forgeconfigapiport-common and forgeconfigapiport-fabric. When developing a mod for Fabric only, simply keep using forgeconfigapiport-fabric, nothing different from before. But when developing a mod for both Forge and Fabric simultaneously using a multi-loader setup, forgeconfigapiport-common comes in handy for the common project, as it enables using most config related classes in that part of the project, really just config registration is what's left for the mod loader specific projects.fuzs.forgeconfigapiport with a similar structure to Fabric Api (divided into api, impl, and mixin)fuzs.forgeconfigapiport also is the new domain used for the Maven distributionapi package at net.minecraftforge.api has been moved to the new domain at fuzs.forgeconfigapiport.api and refactored:net.minecraftforge.api.ModLoadingContext -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigRegistry: Same as before, methods have been renamed from registerConfig to simply register though and registration needs an instance from ForgeConfigRegistry#INSTANCE.net.minecraftforge.api.ConfigPaths -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigPaths: Overhauled, includes helper methods for getting default paths for all config types, also provides the full file path, not just the directory name.net.minecraftforge.api.fml.event.config.ModConfigEvents -> fuzs.forgeconfigapiport.api.config.v2.ModConfigEvents: No changes, class has only been moved.fuzs.forgeconfigapiport.implfuzs.forgeconfigapiport.mixin09.01.2023 · 318 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
fuzs.forgeconfigapiport.impl.util.ReflectionHelper to fix crash with the Configured mod when editing a value that does not have a valid net.minecraftforge.common.ForgeConfigSpec$RangeServerLifecycleEvents#SERVER_STARTING callback, and are unloaded after everything in ServerLifecycleEvents#SERVER_STOPPED via custom event phases (thanks to SquidDev!)fabric.mod.jsonThis version includes major changes and refactors regarding the whole structure of Forge Config Api Port, most notably a reorganization into a multi-loader project (with separate publications for a common and Fabric Gradle project); as well as moving all classes and code not present on Forge to a separate domain (fuzs.forgeconfigapiport).
defaultsconfigs directory (just like Forge, not that it's too useful).minecraft/config/), so those configs are no longer world specific, but can be accessed much easier by users/config command for opening local config files from being registered, intended to be used when hosting a LAN world to allow clients without this mod to connectcom.electronwill.nightconfig.core.io.ParsingException: Not enough data available (an issue when reading local config files from malformed/corrupted file, which apparently appears quite often)forgeconfigapiport-common and forgeconfigapiport-fabric. When developing a mod for Fabric only, simply keep using forgeconfigapiport-fabric, nothing different from before. But when developing a mod for both Forge and Fabric simultaneously using a multi-loader setup, forgeconfigapiport-common comes in handy for the common project, as it enables using most config related classes in that part of the project, really just config registration is what's left for the mod loader specific projects.fuzs.forgeconfigapiport with a similar structure to Fabric Api (divided into api, impl, and mixin)fuzs.forgeconfigapiport also is the new domain used for the Maven distributionapi package at net.minecraftforge.api has been moved to the new domain at fuzs.forgeconfigapiport.api and refactored:net.minecraftforge.api.ModLoadingContext -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigRegistry: Same as before, methods have been renamed from registerConfig to simply register though and registration needs an instance from ForgeConfigRegistry#INSTANCE.net.minecraftforge.api.ConfigPaths -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigPaths: Overhauled, includes helper methods for getting default paths for all config types, also provides the full file path, not just the directory name.net.minecraftforge.api.fml.event.config.ModConfigEvents -> fuzs.forgeconfigapiport.api.config.v2.ModConfigEvents: No changes, class has only been moved.fuzs.forgeconfigapiport.implfuzs.forgeconfigapiport.mixin09.01.2023 · 40 987 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
fuzs.forgeconfigapiport.impl.util.ReflectionHelper to fix crash with the Configured mod when editing a value that does not have a valid net.minecraftforge.common.ForgeConfigSpec$RangeModConfigEvents class which is the new way of handling mod config events (loading and reloading), to ensure config events are only accessed on a mod specific basisModConfigEvent class is now deprecated for removal in the next major release for 1.20@ApiStatus annotations to ensure mods are only accessing the parts of the library they are meant toimpl domainForgeConfigSpec changes from Forge07.01.2023 · 369 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
ServerLifecycleEvents#SERVER_STARTING callback, and are unloaded after everything in ServerLifecycleEvents#SERVER_STOPPED via custom event phases (thanks to SquidDev!)fabric.mod.jsonThis version includes major changes and refactors regarding the whole structure of Forge Config Api Port, most notably a reorganization into a multi-loader project (with separate publications for a common and Fabric Gradle project); as well as moving all classes and code not present on Forge to a separate domain (fuzs.forgeconfigapiport).
defaultsconfigs directory (just like Forge, not that it's too useful).minecraft/config/), so those configs are no longer world specific, but can be accessed much easier by users/config command for opening local config files from being registered, intended to be used when hosting a LAN world to allow clients without this mod to connectcom.electronwill.nightconfig.core.io.ParsingException: Not enough data available (an issue when reading local config files from malformed/corrupted file, which apparently appears quite often)forgeconfigapiport-common and forgeconfigapiport-fabric. When developing a mod for Fabric only, simply keep using forgeconfigapiport-fabric, nothing different from before. But when developing a mod for both Forge and Fabric simultaneously using a multi-loader setup, forgeconfigapiport-common comes in handy for the common project, as it enables using most config related classes in that part of the project, really just config registration is what's left for the mod loader specific projects.fuzs.forgeconfigapiport with a similar structure to Fabric Api (divided into api, impl, and mixin)fuzs.forgeconfigapiport also is the new domain used for the Maven distributionapi package at net.minecraftforge.api has been moved to the new domain at fuzs.forgeconfigapiport.api and refactored:net.minecraftforge.api.ModLoadingContext -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigRegistry: Same as before, methods have been renamed from registerConfig to simply register though and registration needs an instance from ForgeConfigRegistry#INSTANCE.net.minecraftforge.api.ConfigPaths -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigPaths: Overhauled, includes helper methods for getting default paths for all config types, also provides the full file path, not just the directory name.net.minecraftforge.api.fml.event.config.ModConfigEvents -> fuzs.forgeconfigapiport.api.config.v2.ModConfigEvents: No changes, class has only been moved.fuzs.forgeconfigapiport.implfuzs.forgeconfigapiport.mixin23.12.2022 · 739 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
fabric.mod.jsonThis version includes major changes and refactors regarding the whole structure of Forge Config Api Port, most notably a reorganization into a multi-loader project (with separate publications for a common and Fabric Gradle project); as well as moving all classes and code not present on Forge to a separate domain (fuzs.forgeconfigapiport).
defaultsconfigs directory (just like Forge, not that it's too useful).minecraft/config/), so those configs are no longer world specific, but can be accessed much easier by users/config command for opening local config files from being registered, intended to be used when hosting a LAN world to allow clients without this mod to connectcom.electronwill.nightconfig.core.io.ParsingException: Not enough data available (an issue when reading local config files from malformed/corrupted file, which apparently appears quite often)forgeconfigapiport-common and forgeconfigapiport-fabric. When developing a mod for Fabric only, simply keep using forgeconfigapiport-fabric, nothing different from before. But when developing a mod for both Forge and Fabric simultaneously using a multi-loader setup, forgeconfigapiport-common comes in handy for the common project, as it enables using most config related classes in that part of the project, really just config registration is what's left for the mod loader specific projects.fuzs.forgeconfigapiport with a similar structure to Fabric Api (divided into api, impl, and mixin)fuzs.forgeconfigapiport also is the new domain used for the Maven distributionapi package at net.minecraftforge.api has been moved to the new domain at fuzs.forgeconfigapiport.api and refactored:net.minecraftforge.api.ModLoadingContext -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigRegistry: Same as before, methods have been renamed from registerConfig to simply register though and registration needs an instance from ForgeConfigRegistry#INSTANCE.net.minecraftforge.api.ConfigPaths -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigPaths: Overhauled, includes helper methods for getting default paths for all config types, also provides the full file path, not just the directory name.net.minecraftforge.api.fml.event.config.ModConfigEvents -> fuzs.forgeconfigapiport.api.config.v2.ModConfigEvents: No changes, class has only been moved.fuzs.forgeconfigapiport.implfuzs.forgeconfigapiport.mixin23.12.2022 · 121 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
fabric.mod.jsonThis version includes major changes and refactors regarding the whole structure of Forge Config Api Port, most notably a reorganization into a multi-loader project (with separate publications for a common and Fabric Gradle project); as well as moving all classes and code not present on Forge to a separate domain (fuzs.forgeconfigapiport).
defaultsconfigs directory (just like Forge, not that it's too useful).minecraft/config/), so those configs are no longer world specific, but can be accessed much easier by users/config command for opening local config files from being registered, intended to be used when hosting a LAN world to allow clients without this mod to connectcom.electronwill.nightconfig.core.io.ParsingException: Not enough data available (an issue when reading local config files from malformed/corrupted file, which apparently appears quite often)forgeconfigapiport-common and forgeconfigapiport-fabric. When developing a mod for Fabric only, simply keep using forgeconfigapiport-fabric, nothing different from before. But when developing a mod for both Forge and Fabric simultaneously using a multi-loader setup, forgeconfigapiport-common comes in handy for the common project, as it enables using most config related classes in that part of the project, really just config registration is what's left for the mod loader specific projects.fuzs.forgeconfigapiport with a similar structure to Fabric Api (divided into api, impl, and mixin)fuzs.forgeconfigapiport also is the new domain used for the Maven distributionapi package at net.minecraftforge.api has been moved to the new domain at fuzs.forgeconfigapiport.api and refactored:net.minecraftforge.api.ModLoadingContext -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigRegistry: Same as before, methods have been renamed from registerConfig to simply register though and registration needs an instance from ForgeConfigRegistry#INSTANCE.net.minecraftforge.api.ConfigPaths -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigPaths: Overhauled, includes helper methods for getting default paths for all config types, also provides the full file path, not just the directory name.net.minecraftforge.api.fml.event.config.ModConfigEvents -> fuzs.forgeconfigapiport.api.config.v2.ModConfigEvents: No changes, class has only been moved.fuzs.forgeconfigapiport.implfuzs.forgeconfigapiport.mixin22.12.2022 · 700 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
fabric.mod.jsonThis version includes major changes and refactors regarding the whole structure of Forge Config Api Port, most notably a reorganization into a multi-loader project (with separate publications for a common and Fabric Gradle project); as well as moving all classes and code not present on Forge to a separate domain (fuzs.forgeconfigapiport).
defaultsconfigs directory (just like Forge, not that it's too useful).minecraft/config/), so those configs are no longer world specific, but can be accessed much easier by users/config command for opening local config files from being registered, intended to be used when hosting a LAN world to allow clients without this mod to connectcom.electronwill.nightconfig.core.io.ParsingException: Not enough data available (an issue when reading local config files from malformed/corrupted file, which apparently appears quite often)forgeconfigapiport-common and forgeconfigapiport-fabric. When developing a mod for Fabric only, simply keep using forgeconfigapiport-fabric, nothing different from before. But when developing a mod for both Forge and Fabric simultaneously using a multi-loader setup, forgeconfigapiport-common comes in handy for the common project, as it enables using most config related classes in that part of the project, really just config registration is what's left for the mod loader specific projects.fuzs.forgeconfigapiport with a similar structure to Fabric Api (divided into api, impl, and mixin)fuzs.forgeconfigapiport also is the new domain used for the Maven distributionapi package at net.minecraftforge.api has been moved to the new domain at fuzs.forgeconfigapiport.api and refactored:net.minecraftforge.api.ModLoadingContext -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigRegistry: Same as before, methods have been renamed from registerConfig to simply register though and registration needs an instance from ForgeConfigRegistry#INSTANCE.net.minecraftforge.api.ConfigPaths -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigPaths: Overhauled, includes helper methods for getting default paths for all config types, also provides the full file path, not just the directory name.net.minecraftforge.api.fml.event.config.ModConfigEvents -> fuzs.forgeconfigapiport.api.config.v2.ModConfigEvents: No changes, class has only been moved.fuzs.forgeconfigapiport.implfuzs.forgeconfigapiport.mixinModConfigEvents class which is the new way of handling mod config events (loading and reloading), to ensure config events are only accessed on a mod specific basisModConfigEvent class is now deprecated for removal in the next major release for 1.20@ApiStatus annotations to ensure mods are only accessing the parts of the library they are meant toimpl domainForgeConfigSpec changes from Forge21.12.2022 · 205 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
This version includes major changes and refactors regarding the whole structure of Forge Config Api Port, most notably a reorganization into a multi-loader project (with separate publications for a common and Fabric Gradle project); as well as moving all classes and code not present on Forge to a separate domain (fuzs.forgeconfigapiport).
defaultsconfigs directory (just like Forge, not that it's too useful).minecraft/config/), so those configs are no longer world specific, but can be accessed much easier by users/config command for opening local config files from being registered, intended to be used when hosting a LAN world to allow clients without this mod to connectcom.electronwill.nightconfig.core.io.ParsingException: Not enough data available (an issue when reading local config files from malformed/corrupted file, which apparently appears quite often)forgeconfigapiport-common and forgeconfigapiport-fabric. When developing a mod for Fabric only, simply keep using forgeconfigapiport-fabric, nothing different from before. But when developing a mod for both Forge and Fabric simultaneously using a multi-loader setup, forgeconfigapiport-common comes in handy for the common project, as it enables using most config related classes in that part of the project, really just config registration is what's left for the mod loader specific projects.fuzs.forgeconfigapiport with a similar structure to Fabric Api (divided into api, impl, and mixin)fuzs.forgeconfigapiport also is the new domain used for the Maven distributionapi package at net.minecraftforge.api has been moved to the new domain at fuzs.forgeconfigapiport.api and refactored:net.minecraftforge.api.ModLoadingContext -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigRegistry: Same as before, methods have been renamed from registerConfig to simply register though and registration needs an instance from ForgeConfigRegistry#INSTANCE.net.minecraftforge.api.ConfigPaths -> fuzs.forgeconfigapiport.api.config.v2.ForgeConfigPaths: Overhauled, includes helper methods for getting default paths for all config types, also provides the full file path, not just the directory name.net.minecraftforge.api.fml.event.config.ModConfigEvents -> fuzs.forgeconfigapiport.api.config.v2.ModConfigEvents: No changes, class has only been moved.fuzs.forgeconfigapiport.implfuzs.forgeconfigapiport.mixinModConfigEvents class which is the new way of handling mod config events (loading and reloading), to ensure config events are only accessed on a mod specific basisModConfigEvent class is now deprecated for removal in the next major release for 1.20@ApiStatus annotations to ensure mods are only accessing the parts of the library they are meant toimpl domainForgeConfigSpec changes from Forge07.12.2022 · 4 545 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
ModConfigEvents class which is the new way of handling mod config events (loading and reloading), to ensure config events are only accessed on a mod specific basisModConfigEvent class is now deprecated for removal in the next major release for 1.20@ApiStatus annotations to ensure mods are only accessing the parts of the library they are meant toimpl domainForgeConfigSpec changes from Forge22.11.2022 · 3 564 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
ModConfigEvents class which is the new way of handling mod config events (loading and reloading), to ensure config events are only accessed on a mod specific basisModConfigEvent class is now deprecated for removal in the next major release for 1.20@ApiStatus annotations to ensure mods are only accessing the parts of the library they are meant toimpl domainForgeConfigSpec changes from Forge31.08.2022 · 9 212 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
ModConfigEvents class which is the new way of handling mod config events (loading and reloading), to ensure config events are only accessed on a mod specific basisModConfigEvent class is now deprecated for removal in the next major release for 1.20@ApiStatus annotations to ensure mods are only accessing the parts of the library they are meant toimpl domainForgeConfigSpec changes from Forge31.08.2022 · 329 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
ModConfigEvents class which is the new way of handling mod config events (loading and reloading), to ensure config events are only accessed on a mod specific basisModConfigEvent class is now deprecated for removal in the next major release for 1.20@ApiStatus annotations to ensure mods are only accessing the parts of the library they are meant toimpl domainForgeConfigSpec changes from Forge30.08.2022 · 310 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
ForgeConfigSpec changes from Forge22.08.2022 · 1 100 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
ForgeConfigSpec changes from Forge21.08.2022 · 380 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
ForgeConfigSpec changes from Forge20.08.2022 · 759 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
ForgeConfigSpec changes from Forge20.08.2022 · 107 503 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
20.08.2022 · 4 155 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
20.08.2022 · 67 655 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
02.08.2022 · 220 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
02.08.2022 · 1 210 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
ForgeConfigSpec changes from Forge02.08.2022 · 1 561 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
02.08.2022 · 1 030 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
02.08.2022 · 260 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
02.08.2022 · 827 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
01.08.2022 · 379 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
31.07.2022 · 426 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
ForgeConfigSpec changes from Forge31.07.2022 · 516 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
28.07.2022 · 341 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
ForgeConfigSpec changes from Forge28.07.2022 · 1 027 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
27.07.2022 · 276 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
08.06.2022 · 1 771 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.
03.12.2021 · 3 949 загрузки
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog.