Missing mixin in fabric-registry-sync-v0 suspected to break modded registry loading
@Su5eD arbeitet bereits daran.
Seit 14.7.2026.
Bewertung
Dieses Issue wurde noch nicht bewertet.
Beschreibung
Minecraft version
26.1.x
Describe the bug
FAPI's WorldLoderMixin replacies RegistryDataLoader.WORLDGEN_REGISTRIES with DynamicRegistries.getBootstrappingRegistries(), but FFAPI has no such mixin. This results in modded dynamic registries not being present in the RegistryOps, which can cause resource load failures when a modded Codec expects to be able to locate a Holder for its own registry objects. Sometimes these resource load failures can also crash the game.
Steps to reproduce
The easiest way to reproduce this issue is to use Big Globe, as it registers quite a few dynamic registries.
- Install Sinytra Connector, Forgified Fabric API, and Big Globe.
- Launch the game once.
- Close the game, open
.minecraft/config/bigglobe/mixins.properties, and setbuilderb0y.bigglobe.mixins.Biome_DontFreezeRiverWatertofalse. This is a workaround for a different issue and is unrelated to this issue. - Launch the game again and attempt to create a world.
- AutoCodec (a JIJ dependency of Big Globe) should error out with a message similar to "Registry not present in RegistryOps", and you will not be able to successfully create a world.
Logs
The log submitted to me can be found here.
Additional context
A reference implementation of the required mixin can be found here. However, looking through the parent folder would indicate that FAPI has a lot of other mixins that FFAPI is lacking. I suspect some of this functionality may be provided natively by NeoForge. I did not check if NeoForge replaces the reference to RegistryDataLoader.WORLDGEN_REGISTRIES with something else, as I do not have a NeoForge dev environment setup right now. All the code digging I did for this issue was done in a fabric dev environment. This issue serves as my best guess as to what the problem is.
- Vorherrschende Sprache
- Java
- Sterne
- 181
- Forks
- 41
- Ø Merge
- 19 T. 17 Std.
- Gemergte PRs (30 T.)
- 1
Entwicklungsumgebung
- Kein Dockerfile und keine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus Sinytra/ForgifiedFabricAPI
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 85/100
Sinytra/ForgifiedFabricAPI#298 ·
-
1.21.x bug
Sinytra/ForgifiedFabricAPI#276 ·
-
1.21.x bug
Sinytra/ForgifiedFabricAPI#269 ·
-
1.21.x bug
Sinytra/ForgifiedFabricAPI#267 ·
-
1.21.x bug
Sinytra/ForgifiedFabricAPI#265 · 6 Kommentare ·
Alle Issues in Sinytra/ForgifiedFabricAPI
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
floci-io/floci#5369 · 1 Kommentar ·
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
sqlcipher/sqlcipher-android#97 · 1 Kommentar ·
-
bug IIIF interoperability
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
Netcracker/qubership-integration-platform#1046 ·
Maintainer antworten meist innerhalb von 2 Tagen