
Custom Time Cycle
Allows the day and night durations of Minecraft days to be customised, without changing tick speed.
Screenshots



About this Mod
Custom Time Cycle
Custom Time Cycle is a mod that allows changing the duration of Minecraft days and nights using a simple
command, without changing tick speed. It is available for both Fabric and NeoForge. It can be used on servers (without
being required on player clients), and in singleplayer.
Since Minecraft 26.1, Custom Time Cycle allows changing the duration/rate of change between every time marker for a clock, which are
data-driven. This allows very granular control over the rate at which time for a clock progresses.
The mod also applies a small fix to villager behaviour, so that they still properly spawn iron golems with longer day/night durations
than vanilla.
License
This mod is licensed under GNU LGPLv3.
Donating
If you like this mod, consider donating.
Discord
For support and/or any questions you may have, feel free to join my discord.
Version support
| Minecraft Version | Status |
|---|---|
| 26.1.x | ✅ Current |
| 1.21.11 | ✔️ Available |
| 1.21.9+10 | ✔️ Available |
| 1.21.6+7+8 | ✔️ Available |
| 1.21.5 | ✔️ Available |
| 1.21.4 | ✔️ Available |
| 1.21.2+3 | ✔️ Available |
| 1.21+1 | ✔️ Available |
| 1.20.5+6 | ✔️ Available |
| 1.20.4 | ✔️ Available |
| 1.20.1 | ✔️ Available |
I try to keep support up for the latest drop of Minecraft. Updates to newer Minecraft
versions may be delayed from time to time, as I do not always have the time to immediately update my mods.
Unsupported versions are still available to download, but they won't receive new features or bugfixes.
NeoForge ports are available for Minecraft 1.21+1 and for Minecraft 1.21.9 onwards.
Usage
On Fabric, the Fabric API is required. When installed server-side, the mod is not required on clients.
Durations of time markers can be configured for each periodic world clock and are saved across server restarts / world saves.
For clients, the time cycle of a world can be configured upon creation, by selecting the "More" tab at the top, then
clicking the "Time Cycle" button. You can also configure default time cycle durations for all new created worlds, in the mod's
global configuration screen. This can be accessed on Fabric using the ModMenu mod, and on NeoForge using the built-in mod menu.
Global configuration is stored in .minecraft/config/customtimecyle.json.
The mod also adds a simple command, /timecycle, which can be used to alter the time cycle on servers and existing singleplayer worlds.
Its usage is as follows:
/timecycle status- Shows a simple status message displaying which time durations and rates are currently in use in the current dimension.
/timecycle set <dayduration> <nightduration>- Modifies the durations of the Minecraft day and night in the current dimension.
/timecycle set from <from> to <to> duration <duration>- Modifies the duration in ticks between 2 time markers in the current dimension.
/timecycle set from <from> to <to> rate <rate>- Modifies the rate at which time progresses between 2 time markers in the current dimension.
/timecycle reset- Resets the rates of all time markers in the current dimension.
/timecycle of <clock> ...- Allows running all of the above commands, but for that specific clock instead of the one of the current dimension.
The rate modifications the mod makes apply on top of the vanilla /time rate command.
Using the /timecycle command requires the timecycle.command permission or operator level 2.
Modpack developers can also include the following file in the config folder to preconfigure time cycle durations for
worlds on servers or clients:
{
"daytime": <day time ticks>,
"nighttime": <night time ticks>
}
How it works (technical explanation)
Since Minecraft 26.1, the game now has a "clock" concept. In vanilla, there are only 2 clocks, and only 1 that matters here:
the minecraft:overworld clock, for the overworld dimension.
Clocks in Minecraft control timelines, and can progress at a custom rate, though
by default, they progress at the same rate as the server's tick rate: 20 ticks per second. In vanilla, this rate can
be configured for the entire clock, using the /time rate command.
This mod simply allows configuring the rate at which a clock progresses on a time marker
basis. Time markers mark a certain moment along the clock, such as minecraft:day for the start of the day,
or minecraft:midnight for midnight. You'll have seen these in the /time set command too. The mod adds 2 custom time
markers for the vanilla minecraft:overworld clock, customtimecycle:sunrise and customtimecycle:sunset. These
are added primarily for legacy reasons, and are used for the /timecycle set <dayduration> <nightduration> command.
As was said before, this mod can work on any clock, as long as it is a periodic one, like minecraft:overworld. This makes
it work well with custom dimensions added by datapacks/mods that use their own clock.
Available Versions
How to Install Custom Time Cycle on Your Server
Order Server
Order a Minecraft Java server with at least 3 GB RAM (4 GB recommended).
Set fabric Loader
In the panel under "Egg", select the fabric loader and matching Minecraft version (26.1.2).
Install Mod
Open the mod browser in the dashboard and search for "Custom Time Cycle". Click "Install" – done! Alternatively, upload the .jar via SFTP to the /mods folder.
Compatibility
Mod Loaders
Minecraft Versions
26.1.2, 26.1.1, 26.1 (+20 more)
Server-side
✓ RequiredRecommended RAM
4 GB(min. 3 GB)Frequently Asked Questions
Custom Time Cycle server crashes on startup – what to do?
Most common cause: wrong fabric version or insufficient RAM. Check the server log (latest.log) for "OutOfMemoryError" or "Mixin" errors. With Mado Hosting: ensure at least 3 GB RAM is allocated and the loader matches the mod version (26.1.2). You can switch loaders with one click in the panel.
Is Custom Time Cycle compatible with fabric and neoforge?
Custom Time Cycle officially supports fabric, neoforge for Minecraft 26.1.2, 26.1.1, 26.1. The Mado dashboard automatically detects incompatible loader combinations.
Server lagging with Custom Time Cycle – how to optimize performance?
Recommended RAM: 4 GB (per 8 players). Use /spark profiler to check if Custom Time Cycle consumes the most tick time. Common fixes: reduce server view-distance to 8-10, install "performant" or "starlight" as supplementary mods on Forge. With Mado Hosting, your server runs on NVMe SSDs with dedicated CPU cores for minimal latency.
Similar Mods
Rent Modded Server
Install Custom Time Cycle with just one click on your server.