ВЕРСИИ (82)

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - First release for Forge and NeoForge. Same code as Tick Stabilizer 1.0.2 for Fabric. - After a lag spike the server does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - The wait between ticks is spent on chunk loading and world generation, as in vanilla, so world generation runs as fast as without the mod. - /tick sprint (1.20.3 and later) is left alone, and a /tick rate faster than 20 is followed. - /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json in the game's config folder. A value outside 15-50 ms is clamped, with a warning in the log; an empty or broken file does not crash the server. - Install it on the server, or in singleplayer. Clients joining a server do not need it. - On Minecraft 1.20.1 the same file runs on Forge and on NeoForge.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.2: - Ticks are now spaced the way vanilla spaces them, instead of putting the server thread to sleep. In 1.0.1 the server slept before each tick, and that time was taken from chunk loading and world generation: a pregeneration could fall behind until the server ran out of memory. The server now keeps working on chunks while it waits for the next tick, so world generation runs as fast as without the mod. - After a lag spike the server still does not run the missed ticks back to back: ticks keep starting at least 50 ms apart, with no burst of fast ticks. - /tick sprint (1.20.3 and later) is no longer held to 20 ticks per second, and a /tick rate faster than 20 is followed. - New /tickstabilizer command for operators: shows the interval, sets it with /tickstabilizer interval <15-50>, and reloads the config file with /tickstabilizer reload. - config/tickstabilizer.json: a value outside 15-50 ms is clamped, with a warning in the log. An empty or broken file no longer crashes the server: the default 50 ms is used and the file is left as it is, so you can fix it. - Fabric API is no longer needed. - One file per Minecraft version, from 1.18.2 to 26.3. Now also available for Forge and NeoForge. - Install it on the server, or in singleplayer. Clients joining a server do not need it.

v1.0.1: - Fixed mod icon not displaying in ModMenu