Crash when Loading World about fabric-mumblelink-mod

[magneticflux-]

Very strange! I do stuff with AWT because I need to open URIs, but that shouldn't affect mouse click events or GLFW...

The extra mods are probably just Kotlin libraries and the config library. I'm planning on moving to Fiber Config like I did for fabric-tree-chopper eventually, which is more modern and should stay updated.

I'll take a look at this in a few hours, it shouldn't be too much of a hassle to fix.

[magneticflux-]

I'm closing this issue in favor of #78 to centralize all info about AWT-using mods.

[magneticflux-]

Are you able to reproduce it consistently? Does it occur with only fabric-mumblelink-mod installed?

It looks to me like an issue in loading datafixers for world loading, which this mod doesn't touch at all. I'm inclined to believe it's something else's fault unless it's reproducible and isolated to just this mod.

[DarianLStephens]

I'm able to load the game perfectly normally if I remove Mumble Link, though I haven't tried with only Mumble Link.

[magneticflux-]

Okay, I need this information:

• Can you reproduce it consistently? Does it happen every time you load a certain world?
• Does it occur with only the mod installed? (You can make a backup of the world if you have item- or block-adding mods)

[DarianLStephens]

1. So far, the crash has been perfectly consistent. The game will crash when loading a world with the mod, and won't without it.
2. It actually does not occur with just this mod installed; it's likely some sort of odd conflict with another.

[magneticflux-]

2. It actually does not occur with just this mod installed; it's likely some sort of odd conflict with another.

That's what I expected. Could you go through your modlist using the binary search technique https://gist.github.com/TomeWyrm/a8cff19ce112edbc3c8a and report the results? Fixing the issue will go much faster when I know which mod is conflicting and I can read through its sources.

[DarianLStephens]

Interesting; I'm no longer getting any kind of crash, whether from loading an old world or creating a new one.
My best guess in this case is that it had something to do with either Charm, Charmonium, or Strange, seeing as I updated all three before testing again.

Well, I'll be looking forward to the config rework then, whenever it should come.

[griffin4cats]

Related to the AWT thing:
It also makes this mod incompatible with The Backrooms mod.
And I'm getting another disconnect in 1.17 on a mostly vanilla server, so there may be another issue at hand. Will update once I know what it is, i think it's another AWT-related incompatibility.

[griffin4cats]

Update: ToroHealth Damage Indicators is currently incompatible, but unascribed has now made a pull request to ToroHealth that will fix the incompatibility, so this is no longer an issue on 1.17.1. If I find any more AWT incompatibilities I'll update this further, but the backrooms related AWT error still stands.

[magneticflux-]

Does #33 not work anymore? I'll have to revisit my hack and see if I can make it more effective.

It might be that including optifabric will activate my workaround and fix the mods. @griffin4cats Can you test that?

[griffin4cats]

The thing is, I never included optifabric in that modpack, but that section of code seemed to activate from what I saw when i was working with a friend to figure out the incompatibility.

[magneticflux-]

Maybe making the workaround more aggressive will help. @griffin4cats Can you test this version to see if it fixes the issues? (Unzip first)
fabric-mumblelink-mod-0.8.4.zip

[griffin4cats]

The backrooms incompatibility occured in 1.16.5 which is no longer supported by mumblelink. The backrooms does not have a 1.17 version yet. I thought I mentioned that it was in 1.16.5, but i guess I forgot to.