warjort

https://github.com/MinecraftForge/MinecraftForge/blob/b5655b0ddc93ee0c02c9ad1b3a9a4dbd9bd3c572/src/main/java/net/minecraftforge/client/event/ScreenEvent.java#L236 Then check event.getScreen() instanceof TitleScreen and draw what you like. But don't be suprised if another mod is also trying to do the same thing as you.

That is private.

I underlined the mod: illuminations-forge-1.18.2-1.10.2.19.jar

Check you have the latest version the contact the mod author.

That is the one you posted before. The launcher_log.txt is not in the logs folder. It is the log of Mojang's launcher that sometimes logs errors when the game hard crashes. From my footer: NOTE: As I said above, you need to post the launcher_log.txt directly after the crash. If you restart the launcher, that will clear the log and we won't see the error (if there is one). Also you are still posting logs in the forums.

Whatever that is, it shows the game being shutdown normaly at 16:35:33, nearly 4 hours BEFORE the crash in your previous log. My footer and the sticky EAQ post at the top of the forum explain how to find the logs. Read them.

Conflict between apoli and obsureapi. Check you have the latest versions then contact the mod authors.

Check you have the latest version then contcat the mod author.

Please don't post large files in the forums use a file upload site. There is no error in that log. If that really is the full log post the launcher_log.txt from directly after the crash. The last thing in the log is: If it really did crash here, it's likely an issue with your graphics driver.

Use java 17, mixin does not support java 20

Use java 17, mixin does not support java 20

Just replace where it says "java" in your run.bat with "C:\Program Files\Java\jdk-17\bin\java.exe" or wherever the java17 executable is located. That way you know exactly which java it is using. The quotes are important because there is a space in the path.

You shouldn't be caching the registry like that. You should just retrieve the data when you need it. At best you will have the wrong registry if somebody reloads the datapacks. At worst you will cause memory leaks or weird bugs. Caching data in static fields is a major cause of memory leaks in java and/or data leaking into contexts where it is not valid.

Issue with immersive portals. Check you have the latest version then contact the mod author.

@EventBusSubscriber(modid = MODID) // Automatic registration public class EventHandlingClass { @SubscribeEvent // method handles an event public static void handleAnEvent(SomeEvent event) { ... } } If you don't use @EventBusSubscriber and static methods, you have to explicitly register the class, instance or method. https://docs.minecraftforge.net/en/latest/concepts/events/

All the ResourceKeys where defined in the Registry inteface class before Mojang's refactoring. I think it was Registry.BIOME_REGISTRY

I already showed you how to get the biomes loaded from datapacks by using the server's RegistryAccess. Look at this code: @EventBusSubscriber(modid = MODID) public class Test { @SubscribeEvent public static void listBiomes(ServerStartingEvent event) { var biomes = event.getServer().registryAccess().registryOrThrow(Registries.BIOME); LOG.info("Datapack: " + biomes.stream().toList().size()); LOG.info("Forge: " + ForgeRegistries.BIOMES.getValues().size()); } } Which when run against 1.19.4 produces: Datapack: 63 Forge: 0 I don't know why that Forge Biome registry still exists? All the other dynamic registries were removed when Mojang changed how datapack registries work in 1.19.3 https://gist.github.com/ChampionAsh5357/c21724bafbc630da2ed8899fe0c1d226#registries

The long version: * mixin is a tool used by mods to modify java bytecode. It is distributed with forge for the convenience of mod developers that use it, but it is not supported by forge. In fact, its use is discouraged. * the current version of mixin was released 4 months BEFORE java 18 so it will know nothing about that and later java versions https://github.com/SpongePowered/Mixin/releases * java 18 or 19 are no longer supported and neither will java 20 be supported once java 21 the next LTS (long term support) version is released sometime around September this year * java 17 is the current LTS: https://en.wikipedia.org/wiki/Java_version_history with support ending in 2027 or later The short version: Use java 17. Or alternatively, uninstall all the mods that use mixins.

Use java 17, mixin does not support java 20

And please do not post large files in the forums, use a file upload site.

Use java 17, mixin does not support java 20

The thing sending the incorrect data is on the server. So it won't be a client only mod.

The parameter you are passing is the wrong type. You can't post compiler errors here. This is a support forum not a teaching forum and especially not a teaching java forum.

Your client and server disgaree on what data an entity (a bat) has. The server thinks something is complicated data (NBT) while the client thinks it is a boolean. Probably the only way to find the mod causing the problem is to experiment with removing mods until the error stops happening. Backup your world(s) before removing mods.