Tags
Creators
Details
1.8.2-hotfix1020
Compatibility
Required content
Changes
JEG 1.8.2-hotfix1020 Changelog
Date: 2026-10-20
Version: 1.8.2-hotfix1020
Target: Minecraft 1.21.1, 26.2, and 26.3, Fabric / NeoForge; Java 21 for 1.21.1 and Java 25 for 26.x. Existing 26.3 compatibility fixes remain included.
Artifacts: Six loader/version-specific JARs listed in 1.8.2-hotfix1020-manifest.json.
Fixed
-
All six maintained ports: supplied the missing Phantom SMG item fallback; also supplied the missing animated texture in both 1.21.1 ports. Reuse each port's matching Custom SMG artwork and preserve existing models/UVs.
-
Backported the resource repair to all five legacy branches without changing their release versions.
-
Fabric: fixed joining a world failing with
Invalid player datawhen recipe synchronization is enabled. Magazine-mode filtering now callsRecipeMap.create()so Fabric initializes its synchronized-serializer index. -
Both loaders: filter the original recipe registry through a delegated lookup and let the platform factory construct the recipe map. Switching modes can restore hidden recipes while retaining recipe-book filtering and reload behavior.
-
Fixed startup on NeoForge
26.3.0.95/ FancyModLoader12.0.12: FML renamedModConfig.Type.SERVERtoSYNCED, causingNoSuchFieldErrorduring JEG construction. The hotfix resolves the appropriate type at runtime and also supports earlier 26.3 loaders. -
Preserved the
jeg-server.tomlfilename and server-to-client configuration synchronization. Existing globalconfig/jeg-server.tomlsettings continue to be read. -
NeoForge uses the same factory construction for platform and mod compatibility; the Fabric-specific synchronized-serializer crash was not reproduced on NeoForge.
-
Fixed the startup crash on NeoForge
26.3.0.95/ FancyModLoader12.0.12caused by the removedModConfig.Type.SERVERfield. Resolve the renamedSYNCEDtype at runtime, withSERVERsupport retained for earlier 26.3 loaders. -
Kept the existing
jeg-server.tomlfilename and server-to-client configuration synchronization, so the globalconfig/jeg-server.tomlcontinues to be used. -
Included the recipe-map fix from commit
c999b73c: build filtered recipe maps throughRecipeMap.create()to preserve platform and mod initialization hooks. The Fabric-specific synchronized-serializer crash was not reproduced on NeoForge.
Upgrade notes
- Replace the old JEG JAR with the artifact matching your loader; keep only one JEG JAR installed.
- On FML 12.0.8+, world-specific synchronized overrides use
<world>/syncedconfig/. If you previously customized<world>/serverconfig/jeg-server.toml, copy it to<world>/syncedconfig/jeg-server.toml. The globalconfig/jeg-server.tomlneeds no rename or move. - All six maintained modules now declare
1.8.2-hotfix1020. Use the JAR matching both your Minecraft version and loader.
Current texture rebuild verification
- All six maintained modules passed
build; Fabric also passedcompileClientJava. - All 11 source branches and six release JARs passed texture path, PNG integrity, and expected resource-content checks. All six JARs passed ZIP integrity and version metadata checks.
- No new client session or gameplay regression was run for this resource-only repair. Legacy ports were checked at source-resource level.
Earlier 26.3 hotfix verification
The following checks were performed on the earlier 26.3 hotfix artifacts before this texture rebuild.
- Reproduced the unfixed Fabric
bySyncedSerializernull-pointer failure during a real client login to a dedicated server. - The recipe repair passed 24 real-client regression steps per loader: dedicated login, same-player reconnect, server restart, singleplayer, both modes, and reloads. All 14 controlled recipes and ordinary vanilla/JEG recipes were checked; Fabric checks also require actual client synchronization events.
- The hotfix version passed another 18 dedicated-server recipe steps per loader, including reconnects and restart. The NeoForge run includes the config compatibility change.
- Fabric
build compileClientJavaand NeoForgebuildpassed in independent source snapshots. Delivered JAR versions, factory mixins, and absence of verification fixtures were checked. NeoForge's delivered classes and resources match the independently tested build; mixin JSON differs only in formatting. gradlew.bat clean buildpassed, including magazine-mode, vehicle geometry/damage, explosion-shake, and raid-balance checks.- The production config-type resolver passed against FML
12.0.0(SERVER) and12.0.12(SYNCED). - NeoForge
26.3.0.7-betadedicated server reachedDone, loaded 161 JEG recipes, and stopped normally. - The packaged JAR started on production NeoForge
26.3.0.95/ FML12.0.12and joined a disposable singleplayer world with GeckoLib5.5.7. - A world-specific
syncedconfig/jeg-server.tomlwithmagazineFeedEnabled = falsewas read correctly: the server loaded direct-feed mode and 151 JEG recipes, and the client joined successfully. - Packaged mod metadata declares
1.8.2-hotfix1020.
Full gameplay regression testing was not performed. Existing GeckoLib animation parsing warnings remain outside this hotfix; offline authentication/Realms warnings were expected during the disposable client check.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:dxTydNDF:OiV988q6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:dxTydNDF:OiV988q6"
}

