Add 120 FPS option to Max Framerate setting (and investigate tick skipping with Unlimited FPS)

Description
When playing Minecraft Java Edition with "Max Framerate" set to Unlimited, the game sometimes experiences severe tick skipping ("Running X ms behind, skipping X ticks" warnings in the console / log). This leads to noticeable lag in the world simulation (entity movement, redstone, block updates, etc.), even when the reported FPS is very high.

Many players have observed that limiting the framerate to around 120 FPS or lower often stabilizes the tick rate (TPS stays closer to 20.0) and reduces or eliminates the skipping. Setting it to Unlimited appears to cause the rendering thread to consume too many resources, leaving less time for the game tick loop.

Suggestion

Please consider adding 120 FPS as a standard preset option in the Video Settings > Max Framerate slider (in addition to the existing 60, 120 is a very common target for modern monitors and provides a good balance between smoothness and performance).

Having a built-in 120 FPS limit would:

• Make it easier for players to avoid tick skipping without manually typing a custom value in options.txt

• Reduce unnecessary GPU/CPU load on high-refresh-rate displays

• Improve overall gameplay stability for many users

Steps to Reproduce (Bug part)

1. Set Video Settings → Max Framerate to Unlimited

2. Set a relatively high render distance (16+ chunks) or load a complex world

3. Play normally and monitor F3 screen (MSPT / TPS) + console output

4. Observe frequent "skipping ticks" warnings and unstable TPS

Expected Behavior

The game tick should remain stable at ~20 TPS regardless of rendering framerate. Unlimited FPS should not negatively impact tick processing.

Observed Behavior

Tick skipping occurs more frequently with Unlimited FPS. Limiting to 120 FPS often resolves or greatly improves the issue.

Additional Information

• Affected versions: (ここにあなたのバージョン例: 1.21.x など)

• This is not a new issue, but it remains problematic for many players with high-end hardware.

• Similar discussions exist in older tickets (e.g. MC-64223), but no dedicated fix or quality-of-life option has been added yet.

Thank you for considering this report and suggestion!