Forward- Forge-Client-Reset-Packet

ForgeClientResetPacket 0.3.2 – Forge 1.20 / 1.20.1

Changes since 0.3.1:

Oculus shaders workaround (#3, possibly #12)

• Oculus shaders are switched off on the render thread just before the client reset, and turned back on about 2 seconds (40 ticks) after you land on the new server. This works around the "Failed to clear, closing connection" kick when switching servers with shaders on.
• If the switch fails, shaders come back on at the title, multiplayer or disconnected screen.
• Shaders are only turned back on if they're still off the way the mod left them. If you changed the shader setting during the switch, your choice is kept.
• A shutdown hook restores your Oculus config if the game closes mid-switch.
• The restore always runs on the render thread, and a failed restore is retried (up to 3 times) instead of silently leaving shaders off.
• Soft dependency through the public Iris/Oculus API only. Nothing changes when Oculus isn't installed.

Fixes

• mods.toml now declares Minecraft [1.20,1.20.2) and Forge [46.0.14,48), so 1.20.2 no longer tries to load this jar and crash with NoClassDefFoundError: NetworkConstants.
• The mod version in mods.toml now comes from the build, and the project links point to FoxyCraftNetwork.

Client-side only. PR: https://github.com/FoxyCraftNetwork/Forge-Client-Reset-Packet/pull/14