Bumps modmenu from 3.0.+ to 3.1.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps cloth-config-fabric from 6.1.+ to 6.2.57.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

As of Settxi 2.9.0, I can now easily move to SpruceUI.

Why?

Shedaniel (creator of Cloth Config) has stated that they do not recommend using Cloth anymore as the API is bad, and is only supported because they don't want to rewrite REI config.

"cloth config is bad, don't use it" - shedaniel

Things to consider

OK Zoomer

As Zoomify becomes more and more advanced to fill the gap that was left on the migration to the Quilt Toolchain, the only major difference is the config screen. I don't want Zoomify to be seen as an OK Zoomer clone.

UX

I fell the user experience in Cloth Config is marginally better than SpruceUI due to the way they handle categories.

Cloth has a header which the user can always see and click on, making the user aware of the full capabilities immediately after opening the config.

On the SpruceUI side, the config feels busy with buttons everywhere (though they can be laid out more precisely) and categories are treated as sections, with the user having to scroll down to find the other categories. This flaw could be minimised by sorting the categories into their ascending complexity, basic users don't need to scroll, more advanced users can if they wish.

Jar Size

Cloth Config is widely used in mods and is likely already included in modpacks or mod folders. Spruce, on the other hand, has no mod page on Curseforge nor Modrinth and relies on the mod to use Jar in Jar (though SpruceUI is more lightweight than Cloth).

What is this issue for?

I would like to see some feedback from modpack developers and just regular users of Zoomify on what they think of the switch.

I suggest adding two buttons: "Reset to default" and "Reset to OptiFine-like"

The latter is described on https://github.com/Fabulously-Optimized/wiki/blob/main/en-us/give-up-optifine.md

Heyo, I am a mod developer and recently I have been getting few user issue reports of getting dependency errors with cloth-config even tho the correct version of cloth config mod was in the mods folder. ~~After some investigation it was narrowed down to JIJ inclusion of cloth-config in this mod causing the issue.~~

~~Please consider one of two solutions listed bellow~~

~~- Stop including the cloth-config jar with the mod and have the user manually install it - While this is inconvenient for users, This is the solution I would be most happier with as this would eliminate this problem all-together, And this would be more beneficial to Cloth-config developers.~~
~~- At the very least include the latest CF stable release version for given the Minecraft version - I am not exactly thrilled to deal with users complaining about dependency issues through no fault of either me or the user, wasting both parties time. Nor do I want the solution to be having them remove your mod. Yes I do plan on changing my fabric.mod.json dependency configuration to allow older versions of cloth-config, which is irrelevant and I should not have to do that~~

Retracting that, half-ly, context below

This fix changes the way interpolation is calculated - switching from ticks to ms. Now the animation is less dependent on frame rate and plays normally at any value of the fps counter.

Also correct tickDelta is used for correction.

Here's a GIF for comparison (without and with):

Hello, I think I find a little issue.

The first time I configured the mod, I didn't find the setting Relative Sensitivity in Mod Menu.

After I set this option in the .json file to true instead of false, the option appeared in the settings menu.

Now, I'm able to swtich this option from the menu.

Thank you

Updated Zoomify to 2.4.0 and it popped up this toast:

However, FO unbinds Save Hotbar Activator and rebinds Zoomify's key, so there is actually no conflict whatsoever.

Pls fix

MC 1.19.2, Fapi 0.60.0, Loader 0.14.9

I've been told that this mod aims to replicate OK Zoomer's behaviour if the user so chooses. That being said, I don't think the experience is the same yet.

Difference 1

Attached is a comparison video of OK Zoomer and Zoomify (recorded at 150fps and played back at 10% speed).

What's clear about this video is that that Zoomify has a more aggressive zoom IN and a less aggressive zoom OUT than OK Zoomer. OK Zoomer's logic behind this is sound:

• Smooth zooming in is usually for cosmetic use (in this case, most competitive players use instant zoom), and so the mod can afford to zoom in less aggressively in order to make that shift less jarring.
• Smooth zooming out, however, needs to be snappy. Players stop zooming when they need to complete an activity, and so they should be able to transition out of zoom quickly, hence OK Zoomer's more aggressive zoom out.

Yes, I recorded this comparison at a high framerate and the difference is small, but it's very noticeable when playing. A variation of ease out exp tuned with these differences in mind would be ideal in Zoomify.

Difference 2

OK Zoomer lets you scroll-zoom in large steps (following the same transition curve rules as above), which lets the user scroll to easily replicated levels faster. Comparatively, Zoomify scroll-zooms in smaller increments, without smooth transitions.

You can see this difference in this video (60fps, 100% speed). Zoomify's settings were tuned to max zoom and max scroll speed in order to be comparable to OK Zoomer, by default, the scroll-zoom feels even more sluggish in Zoomify.

• Zoomify gives you finer control over your zoom.
• OK Zoomer lets you scroll-zoom faster.
• OK Zoomer's scroll-zoom transition is less jarring that Zoomify's.

To better replicate OK Zoomer, players should have the option to scroll-zoom the way OK Zoomer does.

As an OK Zoomer user trying to love Zoomify, these are the differences I've found. Besides that, the experience is identical.

Title. This can make the experience inconsistent when moving between areas like a base and an open field, and can also be jittery when the framerate fluctuates.

Bumps cloth-config-fabric from 7.+ to 8.0.75.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Bumps io.github.p03w.machete from 1.2.+ to 2.0.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

im on version 1.19.2 in a minehut server, and the cinematic zoom is broken. It turns on cinematic zoom before the zoom takes place which makes the cursor move incredibly slowly. If it turned on after the zoom it would be fixed I believe tho.

Bumps com.modrinth.minotaur from 2.4.+ to 2.5.0.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Quote from Discord:

[...] Why not make both zooms have identical options, just different keys? Y'know, like JourneyMap has two map presets with identical options

To achieve it option-wise:

Make "behaviour", "scrolling" and "controls" categories instead of tabs then make two tabs [- primary and secondary zoom] with these categories [inside]

so overall there will be 4 tabs:

• primary zoom
• secondary zoom
• spyglass
• misc