Sodium FPS Cap Fix

- Added Minecraft 26.3 support on Fabric and NeoForge, built against Sodium 0.9.2 and Reese's Sodium Options 2.2.5. - Fixed NeoForge failing to start when Reese's Sodium Options is installed. 1.0.36 put a class inside Reese's own package, which NeoForge refuses to load, on NeoForge 1.21.1, 1.21.11, 26.1.2, and 26.2. - Fixed NeoForge 1.21.11 rounding typed FPS limits down to the nearest multiple of ten. - The FPS textbox in the vanilla video settings now applies the cap when you finish editing (Enter, Escape, clicking away, or closing the screen) instead of on every keystroke, so typing 144 no longer caps the game at 10 FPS for a moment. - The FPS textbox now identifies Sodium's FPS option by its id, so another mod's option that happens to be named "Max Framerate" is no longer replaced or saved as the FPS cap. - The saved FPS cap now lives in the game directory's `config` folder even when a launcher starts the game from a different working directory. - Fabric builds now require the exact Minecraft version they were built for, like the NeoForge builds already did.

- Added Minecraft 26.3 support on Fabric and NeoForge, built against Sodium 0.9.2 and Reese's Sodium Options 2.2.5. - Fixed NeoForge failing to start when Reese's Sodium Options is installed. 1.0.36 put a class inside Reese's own package, which NeoForge refuses to load, on NeoForge 1.21.1, 1.21.11, 26.1.2, and 26.2. - Fixed NeoForge 1.21.11 rounding typed FPS limits down to the nearest multiple of ten. - The FPS textbox in the vanilla video settings now applies the cap when you finish editing (Enter, Escape, clicking away, or closing the screen) instead of on every keystroke, so typing 144 no longer caps the game at 10 FPS for a moment. - The FPS textbox now identifies Sodium's FPS option by its id, so another mod's option that happens to be named "Max Framerate" is no longer replaced or saved as the FPS cap. - The saved FPS cap now lives in the game directory's `config` folder even when a launcher starts the game from a different working directory. - Fabric builds now require the exact Minecraft version they were built for, like the NeoForge builds already did.

- Added Minecraft 26.3 support on Fabric and NeoForge, built against Sodium 0.9.2 and Reese's Sodium Options 2.2.5. - Fixed NeoForge failing to start when Reese's Sodium Options is installed. 1.0.36 put a class inside Reese's own package, which NeoForge refuses to load, on NeoForge 1.21.1, 1.21.11, 26.1.2, and 26.2. - Fixed NeoForge 1.21.11 rounding typed FPS limits down to the nearest multiple of ten. - The FPS textbox in the vanilla video settings now applies the cap when you finish editing (Enter, Escape, clicking away, or closing the screen) instead of on every keystroke, so typing 144 no longer caps the game at 10 FPS for a moment. - The FPS textbox now identifies Sodium's FPS option by its id, so another mod's option that happens to be named "Max Framerate" is no longer replaced or saved as the FPS cap. - The saved FPS cap now lives in the game directory's `config` folder even when a launcher starts the game from a different working directory. - Fabric builds now require the exact Minecraft version they were built for, like the NeoForge builds already did.

- Added Minecraft 26.3 support on Fabric and NeoForge, built against Sodium 0.9.2 and Reese's Sodium Options 2.2.5. - Fixed NeoForge failing to start when Reese's Sodium Options is installed. 1.0.36 put a class inside Reese's own package, which NeoForge refuses to load, on NeoForge 1.21.1, 1.21.11, 26.1.2, and 26.2. - Fixed NeoForge 1.21.11 rounding typed FPS limits down to the nearest multiple of ten. - The FPS textbox in the vanilla video settings now applies the cap when you finish editing (Enter, Escape, clicking away, or closing the screen) instead of on every keystroke, so typing 144 no longer caps the game at 10 FPS for a moment. - The FPS textbox now identifies Sodium's FPS option by its id, so another mod's option that happens to be named "Max Framerate" is no longer replaced or saved as the FPS cap. - The saved FPS cap now lives in the game directory's `config` folder even when a launcher starts the game from a different working directory. - Fabric builds now require the exact Minecraft version they were built for, like the NeoForge builds already did.

- Added Minecraft 26.3 support on Fabric and NeoForge, built against Sodium 0.9.2 and Reese's Sodium Options 2.2.5. - Fixed NeoForge failing to start when Reese's Sodium Options is installed. 1.0.36 put a class inside Reese's own package, which NeoForge refuses to load, on NeoForge 1.21.1, 1.21.11, 26.1.2, and 26.2. - Fixed NeoForge 1.21.11 rounding typed FPS limits down to the nearest multiple of ten. - The FPS textbox in the vanilla video settings now applies the cap when you finish editing (Enter, Escape, clicking away, or closing the screen) instead of on every keystroke, so typing 144 no longer caps the game at 10 FPS for a moment. - The FPS textbox now identifies Sodium's FPS option by its id, so another mod's option that happens to be named "Max Framerate" is no longer replaced or saved as the FPS cap. - The saved FPS cap now lives in the game directory's `config` folder even when a launcher starts the game from a different working directory. - Fabric builds now require the exact Minecraft version they were built for, like the NeoForge builds already did.

- Added Minecraft 26.3 support on Fabric and NeoForge, built against Sodium 0.9.2 and Reese's Sodium Options 2.2.5. - Fixed NeoForge failing to start when Reese's Sodium Options is installed. 1.0.36 put a class inside Reese's own package, which NeoForge refuses to load, on NeoForge 1.21.1, 1.21.11, 26.1.2, and 26.2. - Fixed NeoForge 1.21.11 rounding typed FPS limits down to the nearest multiple of ten. - The FPS textbox in the vanilla video settings now applies the cap when you finish editing (Enter, Escape, clicking away, or closing the screen) instead of on every keystroke, so typing 144 no longer caps the game at 10 FPS for a moment. - The FPS textbox now identifies Sodium's FPS option by its id, so another mod's option that happens to be named "Max Framerate" is no longer replaced or saved as the FPS cap. - The saved FPS cap now lives in the game directory's `config` folder even when a launcher starts the game from a different working directory. - Fabric builds now require the exact Minecraft version they were built for, like the NeoForge builds already did.

- Added Minecraft 26.3 support on Fabric and NeoForge, built against Sodium 0.9.2 and Reese's Sodium Options 2.2.5. - Fixed NeoForge failing to start when Reese's Sodium Options is installed. 1.0.36 put a class inside Reese's own package, which NeoForge refuses to load, on NeoForge 1.21.1, 1.21.11, 26.1.2, and 26.2. - Fixed NeoForge 1.21.11 rounding typed FPS limits down to the nearest multiple of ten. - The FPS textbox in the vanilla video settings now applies the cap when you finish editing (Enter, Escape, clicking away, or closing the screen) instead of on every keystroke, so typing 144 no longer caps the game at 10 FPS for a moment. - The FPS textbox now identifies Sodium's FPS option by its id, so another mod's option that happens to be named "Max Framerate" is no longer replaced or saved as the FPS cap. - The saved FPS cap now lives in the game directory's `config` folder even when a launcher starts the game from a different working directory. - Fabric builds now require the exact Minecraft version they were built for, like the NeoForge builds already did.

- Added Minecraft 26.3 support on Fabric and NeoForge, built against Sodium 0.9.2 and Reese's Sodium Options 2.2.5. - Fixed NeoForge failing to start when Reese's Sodium Options is installed. 1.0.36 put a class inside Reese's own package, which NeoForge refuses to load, on NeoForge 1.21.1, 1.21.11, 26.1.2, and 26.2. - Fixed NeoForge 1.21.11 rounding typed FPS limits down to the nearest multiple of ten. - The FPS textbox in the vanilla video settings now applies the cap when you finish editing (Enter, Escape, clicking away, or closing the screen) instead of on every keystroke, so typing 144 no longer caps the game at 10 FPS for a moment. - The FPS textbox now identifies Sodium's FPS option by its id, so another mod's option that happens to be named "Max Framerate" is no longer replaced or saved as the FPS cap. - The saved FPS cap now lives in the game directory's `config` folder even when a launcher starts the game from a different working directory. - Fabric builds now require the exact Minecraft version they were built for, like the NeoForge builds already did.

- Added Minecraft 26.3 support on Fabric and NeoForge, built against Sodium 0.9.2 and Reese's Sodium Options 2.2.5. - Fixed NeoForge failing to start when Reese's Sodium Options is installed. 1.0.36 put a class inside Reese's own package, which NeoForge refuses to load, on NeoForge 1.21.1, 1.21.11, 26.1.2, and 26.2. - Fixed NeoForge 1.21.11 rounding typed FPS limits down to the nearest multiple of ten. - The FPS textbox in the vanilla video settings now applies the cap when you finish editing (Enter, Escape, clicking away, or closing the screen) instead of on every keystroke, so typing 144 no longer caps the game at 10 FPS for a moment. - The FPS textbox now identifies Sodium's FPS option by its id, so another mod's option that happens to be named "Max Framerate" is no longer replaced or saved as the FPS cap. - The saved FPS cap now lives in the game directory's `config` folder even when a launcher starts the game from a different working directory. - Fabric builds now require the exact Minecraft version they were built for, like the NeoForge builds already did.

- Added Minecraft 26.3 support on Fabric and NeoForge, built against Sodium 0.9.2 and Reese's Sodium Options 2.2.5. - Fixed NeoForge failing to start when Reese's Sodium Options is installed. 1.0.36 put a class inside Reese's own package, which NeoForge refuses to load, on NeoForge 1.21.1, 1.21.11, 26.1.2, and 26.2. - Fixed NeoForge 1.21.11 rounding typed FPS limits down to the nearest multiple of ten. - The FPS textbox in the vanilla video settings now applies the cap when you finish editing (Enter, Escape, clicking away, or closing the screen) instead of on every keystroke, so typing 144 no longer caps the game at 10 FPS for a moment. - The FPS textbox now identifies Sodium's FPS option by its id, so another mod's option that happens to be named "Max Framerate" is no longer replaced or saved as the FPS cap. - The saved FPS cap now lives in the game directory's `config` folder even when a launcher starts the game from a different working directory. - Fabric builds now require the exact Minecraft version they were built for, like the NeoForge builds already did.