/time set night doesn't change the visual time — why?

Running /time set night and seeing nothing change is a common head-scratcher. It almost always comes down to the daylight-cycle gamerule or a plugin that controls time itself. Here's how to make time behave.

Why the command seems to do nothing

If doDaylightCycle is true, time keeps advancing right after you set it, so a fixed time won't "stick." And if a plugin manages time (for example a real-time or day-length plugin), it will override your command entirely. On multiworld setups, the command only affects the world you're standing in.

How to fix it

1. Lock the time: run /gamerule doDaylightCycle false, then /time set night. It will now stay night.
2. Let time flow again: run /gamerule doDaylightCycle true when you want the normal cycle back.
3. Check for a time plugin. If one controls the clock, adjust the time there instead of via the command.
4. On multiworld servers, run the command while in the correct world (or target that world).

Tip: Use doDaylightCycle false for builds and events where you want a fixed sky, then flip it back to true afterward.

Frequently asked questions

I locked it to night but a plugin flips it to day. A time-managing plugin is overriding the gamerule. Configure the time in that plugin.

Does this work per-player? No — time is per-world on the server. For a personal client-side sky change, that's a resource pack matter, not a server setting.

Command still ignored after setting the gamerule. Confirm you're an operator and in the right world, then restart and try again. If it persists, share your setup via a ticket.