Client abruptly closes shortly after launch when mod menu is present

[waynestir]

Just updated Sinytra Connector to v.2.0.0 beta 11 for Minecraft 1.21.1. Client crashes on open and doesn't generate a crash report.

Been using just fine previously with beta9+ with a NeoForge Modpack a few of us put together.
If I disable modmenu v11.0.3 it will launch fully with our modpack. I have no idea if it is related to Mod Menu or not do to no crash report being generated.

fabric mods being used
Litematica 0.19.50
MiniHud 0.32.50
Tweakeroo 0.21.50
GammaUtils 2.1.2
Camera Utils 1.0.16
Mod Menu 11.0.3 & required text placeholder api 2.4.2

[Su5eD]

Mod menu is not compatible

[waynestir]

Being that the version of mod menu I've been using that worked for more than a year now hasn't had a single update release since Oct. 2024. I can deduce changes you made broke compatibility. If you don't plan on continuing support just say so. Don't dare tell us that it isn't compatible because We've been using it just fine prior to beta11

[Tapacywka]

ModMenu for Fabric has NEVER worked through Connector: neither on version 1.20.1 nor on version 1.21.1, so stop talking nonsense. If you really want this particular interface for your mod list, use the Better ModList mod, which is an unofficial port of ModMenu to Forge/NeoForge. But don't tell fairy tales about how the original mod worked for you for over a year.

[waynestir]

Is there ever a single person who has a proper response and not some fallacy they make up in their own head?
Better ModList only changes the appearance of Neoforge built in mod menu to look similar to that of the one created for fabric. It has Zero of the functionality to go along with it! You CANNOT access the mod config files of the fabric mods being loaded with connector!
the following image shows 2 separate mod menu buttons. One is the FABRIC version ModMenu and the other is built in version from Neoforge

[Tapacywka]

Is there ever a single person who has a proper response and not some fallacy they make up in their own head? Better ModList only changes the appearance of Neoforge built in mod menu to look similar to that of the one created for fabric. It has Zero of the functionality to go along with it! You CANNOT access the mod config files of the fabric mods being loaded with connector! the following image shows 2 separate mod menu buttons. One is the FABRIC version ModMenu and the other is built in version from Neoforge

I have four modpacks that use Connector, and in all four modpacks, Better ModList interacts with Fabric mod config button. For example, I can easily open the configs for the Presence Footsteps and Footprint Particles mods.

[Tapacywka]

And on your screen, there is one Mods button from Better ModList and one from the Catalogue mod.

[1foxy2]

Is there ever a single person who has a proper response and not some fallacy they make up in their own head? Better ModList only changes the appearance of Neoforge built in mod menu to look similar to that of the one created for fabric. It has Zero of the functionality to go along with it! You CANNOT access the mod config files of the fabric mods being loaded with connector! the following image shows 2 separate mod menu buttons. One is the FABRIC version ModMenu and the other is built in version from Neoforge

because connector extras already allows you to access mod config files, there is no point adding this functionality to better modlist

[waynestir]

And on your screen, there is one Mods button from Better ModList and one from the Catalogue mod.

Still insist I'm lying. WOW
I can send you a download link to the pack I've been using that contains MODMENU working. I believe You would lie and say it doesn't.