What causes the moon not rising as the sun sets?

Only the sun's transform is animated by the day-night cycle; the moon is either absent or pinned, so it never arcs across the night sky.

How do I catch this when it only happens for some players?

Capture it automatically from the player's device with the full stack trace, the device and OS, the build, and a breadcrumb trail of what they did. That turns a vague complaint into a specific, reproducible issue you can fix without owning the hardware it happens on.

How to Fix the Moon Not Rising as the Sun Sets

Quick answer: Drive a second directional light and moon billboard opposite the sun's direction, fading the moon's light in at night and out during the day.

Your sun sets but no moon comes up to light the night. The moon needs its own animated direction (roughly opposite the sun) and a night-gated light to take over after dusk.

How to fix it

1. Position the moon opposite the sun

Place a moon billboard and a second DirectionalLight3D at a direction derived from the negated sun direction (with an offset/tilt) so it arcs across the sky as the sun is down.

2. Cross-fade the lights

Fade the sun light out and the cooler, dimmer moon light in around the horizon crossing so shadows hand off from sun to moon without a dark gap.

3. Show moon phase

Optionally vary the moon billboard's lit fraction over in-game days for phases, and keep its glow tied to the night factor so it does not show during daytime.

Catching the ones you can't reproduce

The hardest version of this to fix is the one you can't reproduce — it only happens on a player's hardware, OS, driver, or save state, under conditions that simply aren't present on your machine. A report that says “it crashed” or “it froze” gives you nothing to act on, so the bug survives release after release while quietly costing you players.

Automatic error capture closes that gap. Each failure arrives with its full stack trace, the device and OS, the build number, and a breadcrumb trail of what the player did right before it broke, so even a failure you have never seen becomes a specific, reproducible issue. Fold identical failures into one signature ranked by how many players each hits, and your worklist sorts itself worst-first instead of arriving as a stream of vague complaints.

This is where a tool like Bugnet earns its place. Its SDK captures every Godot error automatically with the full stack trace plus device, OS, memory, build, and game-state context, folds duplicates into one grouped issue with an occurrence count, and ties each to the build it first appeared on — so you fix the problem that hurts the most players first and confirm it is gone when its signature disappears from the next release.

A crash you can name from its stack trace is a crash you can usually fix in minutes.