sodium-fps-step-fix-fabric-1.0.2-26.2.jar
Curse Maven Snippet
What's new
Fixed
- Fixed a startup crash (
InvalidInjectionException) when the mod is used together with newer Sodium builds. The old mixin was anchored toSodiumConfigBuilder#buildGeneralPage; in Sodium 0.9.3-beta.1 for 26.3 that method gained aVanillaOptionsparameter and no longer callssetRange(10, 260, 10), so the mixin selector no longer resolved and, withdefaultRequire: 1, the game failed to start. - The Framerate Limit slider now keeps its 1 FPS step on every supported Sodium build, including builds that derive the framerate range from Minecraft's
OptionInstanceinstead of declaring(10, 260, 10).
Changed
- Reworked how the slider step is applied:
SodiumConfigBuilderMixinwas replaced bySodiumRangeMixin, which injects intoRange.step()(public Sodium API) and returns 1 for the 10–260 range used by the Framerate Limit option. The fix no longer depends on Sodium internal method signatures, so Sodium updates within the same Minecraft version are much less likely to break the mod. - Other options are untouched: the range guard only applies to
min == 10 && max == 260. OptionsMixin(integer FPS persistence inoptions.txt) andMinecraftMixin(precise frame limiter) are unchanged; their injection targets were re-verified on current Minecraft and NeoForge-patched builds.- Bumped to 1.0.2 for the 26.2 and 26.3 branches. Other Minecraft branches stay on 1.0.1.
Compatibility
- 26.3 (Fabric and NeoForge): Sodium 0.9.2, 0.9.3-alpha.1, 0.9.3-beta.1 and 0.9.3-beta.5.
- 26.2 (Fabric and NeoForge): Sodium 0.9.1 and 0.9.2.
This mod has no additional files