{"id":2961,"date":"2023-04-04T02:37:07","date_gmt":"2023-04-04T02:37:07","guid":{"rendered":"https:\/\/xgamingserver.com\/blog\/?p=2961"},"modified":"2026-06-15T19:21:13","modified_gmt":"2026-06-15T19:21:13","slug":"how-to-stop-the-day-cycle-in-your-minecraft-server","status":"publish","type":"post","link":"https:\/\/xgamingserver.com\/blog\/how-to-stop-the-day-cycle-in-your-minecraft-server\/","title":{"rendered":"How to disable the day cycle in your Minecraft server"},"content":{"rendered":"\n

Freezing time is one of the most common requests server owners have, and for good reason. A locked daytime makes building, terraforming, and screenshot sessions painless because hostile mobs stop spawning in the light and you never lose your view to nightfall. A locked nighttime is great for a horror map, a PvP arena, or a perpetual mob-farming environment. Whatever the goal, the mechanic behind it is a single vanilla game rule: doDaylightCycle<\/code>. This guide walks through exactly how to stop the day\/night cycle on a Minecraft server, how to pin the world to a specific time of day, how the related weather rule works, what changed in recent Minecraft versions, and how to put everything back the way it was.<\/p>\n\n\n\n

Everything here is for Java Edition unless a section says otherwise, and there is a dedicated Bedrock section near the end because the two editions handle this slightly differently. All commands assume you have operator access. If you do not yet have op on your own box, set that up first with our walkthrough on adding an op admin via ops.json and \/op<\/a>.<\/p>\n\n\n\n

The short answer: doDaylightCycle false<\/code><\/h2>\n\n\n\n

The day\/night cycle is governed by a boolean game rule. When it is true<\/code> (the default), time advances normally \u2014 the sun rises and sets, the moon goes through its phases, and a full day lasts 20 real-world minutes. When you set it to false<\/code>, the clock simply freezes at whatever value it currently holds. Run this command from in-game chat as an operator, or from the server console (in the console you drop the leading slash):<\/p>\n\n\n\n

\/gamerule doDaylightCycle false<\/code><\/pre>\n\n\n\n
That is the whole trick. But freezing time “wherever it happens to be” is rarely what people want \u2014 you usually want it locked to a clean midday or a clean midnight. That is where the \/time set<\/code> command comes in, and the standard workflow is to set the time first, then freeze the cycle.<\/p>\n\n\n\n
Lock the server to permanent day<\/h2>\n\n\n\n
To pin a world to eternal daytime, set the time to day<\/code> (or to the exact tick value 1000<\/code>, which is bright morning sun) and then stop the cycle:<\/p>\n\n\n\n
\/time set day\n\/gamerule doDaylightCycle false<\/code><\/pre>\n\n\n\n
The order matters in practice. If you freeze the cycle before<\/em> setting the time, you simply lock whatever moment you happened to be in. Setting the time first guarantees you land on the visual you want, and freezing it second nails it in place. With permanent day and full light, hostile mobs that require darkness will no longer spawn on the surface, which is exactly why creative-build servers reach for this.<\/p>\n\n\n\n
Useful \/time set<\/code> values<\/h3>\n\n\n\n
You can use named keywords or raw tick numbers. A full day is 24,000 ticks long, starting at tick 0 (sunrise). The keywords map to specific ticks:<\/p>\n\n\n\n
Command<\/th>Tick value<\/th>What you get<\/th><\/tr><\/thead>
\/time set day<\/code><\/td>1000<\/td>Bright morning, sun well up<\/td><\/tr>
\/time set noon<\/code><\/td>6000<\/td>Sun at its absolute peak (brightest)<\/td><\/tr>
\/time set night<\/code><\/td>13000<\/td>Just after sunset, dark<\/td><\/tr>
\/time set midnight<\/code><\/td>18000<\/td>Moon at its peak (darkest)<\/td><\/tr>
\/time set sunrise<\/code><\/td>23000<\/td>Sun on the eastern horizon<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n
For the brightest possible permanent day with zero shadows on the horizon, \/time set noon<\/code> (tick 6000) is the cleanest choice. For a normal “morning forever” feel, day<\/code> (tick 1000) is what most people expect.<\/p>\n\n\n\n
Lock the server to permanent night<\/h2>\n\n\n\n
Permanent night uses the exact same two-step pattern, just with a night-time value:<\/p>\n\n\n\n
\/time set midnight\n\/gamerule doDaylightCycle false<\/code><\/pre>\n\n\n\n
Use night<\/code> (tick 13000) for the moment the sky goes dark, or midnight<\/code> (tick 18000) for the darkest point with the moon high. There is one important consequence to keep in mind for permanent night: hostile mobs spawn continuously in the dark, and players who go too long without sleeping become eligible for phantom attacks. If you want eternal night but without<\/em> the phantom nuisance, disable the insomnia rule alongside it:<\/p>\n\n\n\n
\/gamerule doInsomnia false<\/code><\/pre>\n\n\n\n
On Minecraft Java 1.21.11 and newer this rule was renamed to spawn_phantoms<\/code> (more on the rename below). And because a frozen night means players can never sleep through to morning, sleeping simply will not skip time while the cycle is locked \u2014 beds still set your respawn point, but the clock will not move.<\/p>\n\n\n\n
Freezing the weather too: doWeatherCycle<\/code><\/h2>\n\n\n\n
Stopping time does not stop the weather. Rain and thunderstorms run on their own independent game rule, doWeatherCycle<\/code>, which is also true<\/code> by default. If you want a server that is permanently sunny and clear in addition to permanently daytime, you need to handle both. Set the weather to clear, then freeze the weather cycle:<\/p>\n\n\n\n
\/weather clear\n\/gamerule doWeatherCycle false<\/code><\/pre>\n\n\n\n
This is the single most common follow-up question after locking time, because a frozen midday world that still randomly clouds over and rains looks broken. Freezing the weather cycle keeps it whatever you last set it to. You can force a storm and freeze that too (handy for an atmospheric horror map) by running \/weather thunder<\/code> before freezing the cycle. Note that doWeatherCycle<\/code> kept its name through the recent rename era; under the newer snake_case scheme it becomes advance_weather<\/code>.<\/p>\n\n\n\n
Version differences you need to know in 2026<\/h2>\n\n\n\n
Minecraft Java changed how game rules are named, and this directly affects the daylight commands. If you are running a very recent server, the classic doDaylightCycle<\/code> you have seen in every old tutorial may not be the name your server expects.<\/p>\n\n\n\n