Multiconnect does not ignore/block unrecognized custom payloads
Mhowser opened this issue ยท 6 comments
I am still not entirely sure on the best way to fix this. I think probably non-vanilla custom payloads should be blocked by multiconnect by default, and then add a way in the API for mods to transform custom packets.
@lenrik1589 the statistics menu issue should be fixed in the latest multiconnect. The minecraft:register
thing is still an issue, however.
In the fix for this, I will block non-vanilla custom payload packets coming from older versions from triggering normal handing of custom payload packets. I will add an API to instead allow custom handling of these packets.
To fix this, I had to change a little how the API loads. The new API is still binary compatible with mods already using the old one (so no need for a major version bump), but the way it loads could cause issues if the player has an older version of multiconnect than the version of the API another mod is using. So therefore, the new API will be part of the 1.16 version of multiconnect, where players will have to install the new multiconnect anyway.