warjort

https://forge.gemwire.uk/wiki/BlockState_JSONs and getVariantBuilder()

What you do is go to the Mojang office and put a big red "NO" sticker over all the developer's refactoring button in their IDE. 🙂 Mojang still regard the worldgen introduced in 1.16.x as experimental, so any worldgen modding is going to be painful porting across versions until they (if ever) stabilise the code. See DimensionSpecialEffects.forType() and related code.

https://www.curseforge.com/minecraft/mc-mods/invmove/relations/dependencies

FriendlyByteBuffer.readList()/writeCollection() e.g. ClientBoundExplodePacket sends a list of exploded BlockPos

Install the latest preview release of optifine.

The "broken" thread dump just shows it processing image data. It is not "stuck". Of course it might be looping infinitely due to one of your mods breaking minecraft's internal data structures. But that isn't something we can diagnose with a log. If you managed to narrow it down to the quark mod, I suggest you check you have the latest version then contact the mod author. But it could also be as I said above, where the increased number of mods requires a bigger texture atlas for more textures. That is stressing your memory and the java garbage collector.

If you know the problem is byg and you have tried the latest version, contact the mod author.

https://forge.gemwire.uk/wiki/Dependencies/1.18 You can't use obfuscated mods in a development environment.

Issue with apotheosis/placebo trying to generate random loot. Check you have the latest version then contact the mod author.

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

Maybe this? https://forums.minecraftforge.net/topic/119518-exit-code-1073740940/#comment-524102

I've never use the gametest stuff, but I bet if you ./gradlew --debug task-you-are-running to look at the command line used to start minecraft, you have 2 versions of mixin on the classpath? You need to figure out why.

Mods for 1.19.3 aren't going to work with minecraft 1.19.2

Maybe this? https://forums.minecraftforge.net/topic/119518-exit-code-1073740940/#comment-524102

If you know the issue is with create and you have the latest version, then you should contact the mod author.

You seem to somehow have 2 versions of forge on the classpath?

As was stated on the link I provided above, this is crash in native code. If it's not flywheel, you need to report it to microsoft or try a different java.

You are missing or have the wrong version of the AutoRegLib mod.

There is no 1.19.3 version of "oh the biomes you will go", (yet). https://www.curseforge.com/minecraft/mc-mods/oh-the-biomes-youll-go/files/all?filter-game-version=1738749986%3a73407

Install the latest preview release of optifine for 1.18.2

Looks like you have an issue with your resource packs. Maybe there is something wrong with the list in options.txt?

Maybe this? https://forums.minecraftforge.net/topic/119518-exit-code-1073740940/#comment-524102

If it's not flywheel then you should ask them to try removing any client side graphics mods they have like rubidium or optifine. Also, ssk them to add the following system property to their java (jvm) arguments this will let us see what is happening at the network level and what error (if any) they are getting there. Otherwise, without an explicit crash error, probably the only way you are going to find the problem is by experimenting with removing mods using a test server. So you can locate which mod is causing the problem.

It might be related to these messages? Showing a mod mismatch between the client and server? Around the disconnect, there are some earlier errors related to rendering which suggests one of the mods is doing something unsupported by the graphics driver? There are some "warnings" from create/flywheel just before they are kicked. The last thing in the log is from the xaero's map mod, but these are status messages rather than errors/warnings. Maybe try turning off create's special flywheel rendering? https://forums.minecraftforge.net/topic/119518-exit-code-1073740940/#comment-524102 Also ask the user if they get this problem if they play with the same mods in single player.

We need a link to the logs/debug.log so we can see the error.