I suggest that multiconnect allows the usage of modded registries when connecting to a server that is running on the same version as the client, in which case multiconnect already does nothing (there's nothing to do).

I kind of see why that could be of use, but then, why not have a separate instance for connecting to a modded server, where you could install more mods that are interacting with server, and if you already have those client-side mods that are required server-side, why bother connecting to older version: it is very much possible that mod dev changed their networking between the versions.

Here's why: I use many client-side mods, such as Tweakeroo and Xaero's *Map. I often forget to remove multiconnect when connecting to modded servers, and so I load into Minecraft then go to connect and am unable to. I then have to remove multiconnect and restart Minecraft. Minecraft takes a decent amount of time to load, and it's just an inconvenience since I also forget to add multiconnect back when I'm done with the modded server.

Minecraft takes a decent amount of time to load

I'd suggest adding LazyDFU if you don't have it already.

I've been meaning to get it. However, that's besides the point. The point is that multiconnect blocking perfectly valid same-version things when connecting to a server with the same version is an unnecessary hassle.

Duplicate of #226

Ah, I scanned for issues, but I didn't see that one, because it didn't say "registry" in the title.