[xjjakm]

Type of change

• Bug fix
• New feature

Description

Fixes three crashes on MC 26.3:

• ConnectionMixin: re-apply the tick-end fix for Invalid move player packet received kicks (bug when I try to hit a player (26.3) #6733) — the server now rejects multiple position packets within a single client tick, so ServerboundClientTickEndPacket is re-inserted as needed. Without this, using modules such as Criticals (packet-based attack) gets the player kicked.
• TitleScreenMixin: guard against a null Config during early title screen rendering — since MC 26.3, the first frame is extracted during Minecraft.<init>, before Meteor finishes initialization, causing an NPE crash at startup.
• SodiumDefaultFluidRendererMixin: fix java.lang.VerifyError: Bad local variable type with Sodium mc26.3-0.9.2 — the otherState local variable was removed upstream, so capturing it via @Local produced invalid bytecode. The neighbor state is now derived from BlockGetter directly, and the injection targets the new 5-param isFluidSideExposed signature.

Related issues

• bug when I try to hit a player (26.3) #6733

How Has This Been Tested?

• Launch MC 26.3 with Meteor: title screen loads without an NPE crash
• Launch with Sodium 0.9.2 and enter a world: no VerifyError, Xray fluid rendering works
• Join a server and use Criticals: no Invalid move player packet received kick

Checklist:

• My code follows the style guidelines of this project.
• I have added comments to my code in more complex areas.
• I have tested the code in both development and production environments.

[crosby-moe]

1. prefer one pr per fix
2. remove useless llm comments
3. otherState definitely still exists as a local
4. id rather have a human fix the packet issue, my gut feeling tells me lying to the server that the client is ticking at 40tps isnt as good a fix as you think it is