Hi, currently Balm on the server requires connecting clients to have the same version of itself installed, if the mod is present on that connecting client. I'm not sure if this is intentional or not, but is there any way to disable it? A lot of the players connecting to my server use the Modrinth App to play, and so whenever they "Update all" of their mods and Balm auto-updates, they're then unable to connect until I notice and update the Balm mod on the server's end. Any chance could learn to play ball with client/server mod version mismatches? Thanks in advance for any help :)

Totally get your reasoning, and I do support it for wider modpack usage. Perhaps a config option could be added to allow modpack creators and/or server owners such as myself to choose to disable the version mismatch check? You could comment it something like # Do not touch this unless you know what you're doing. In my specific instance, this would be safe, as I have close control over the entire server and its small playerbase, and I would be well aware this is the cause if I encountered any issues. Up to you, thanks anyway for your reply! Awesome work :))

Version mismatches were probably a lot more frequent in the last few days because there were some critical issues that required some versions to be taken down and hotfixes to be pushed. This should hopefully have calmed down so that releases will be less frequent again and you should run into fewer of these issues.

The version mismatch check was added because running mismatched version has high potential to result in confusing crashes or disconnects, which lead to a spike in bug reports when Waystones made a change to its network protocol earlier this year.

Ideally, modpack consumers are gradually taught to avoid using the Update all button because of all the other things that can break by carelessly diverting from upstream versions.

However, I could look into versioning the network protocol separately since it generally doesn't change as often, but that would likely only apply to Balm itself. For mods adding content I'd prefer to avoid the error potential stemming from subtle differences between client and server.

Next version separates the network version from the mod version, so version mismatches on Balm shouldn't occur anymore unless actual incompatible changes to the network protocol are made.

You're awesome, cheers!