Crashes clients with fabric mods that use ConfigurationTasks about velocity

[456dev]

i've just tested without fabric (directly patching vanilla minecraft itself, see this fork of mache)
and was able to add and receive a custom configuration task both with and without velocity, with no changes.

i dont know what fabric does differently (thats next for me to test), but this doesn't seem like a velocity issue?

[electronicboy]

The start and the end of the configuration phase are both well marked with two separate packets, and so there's no need for velocity to care about custom configuration phases as we just wait on the server to tell us when its done configuring the client before we can proceed with actually bumping the client out of that phase.

I'm not really sure what MM is doing here, their repo is pre configuration phase existing, and they're not doing anything in their existing repo that would break with a proxy.

[456dev]

ive found the issue, its on MightyMails side (sort of). it uses MrCrayfish/Framework, which uses login plugin messages on <1.20.2 (which makes sense, as the config phase didnt exist before then anyway.)

[electronicboy]

Yea, login messages are 100% a no-go until 1.20.5, in which at that point we miiiight be able to get something that will support that stuff a bit better (but, is a chunky engineering effort I want to get to but can't really commit to...)