Quick answer: Raise the minimum nighttime ambient and moonlight to a playable floor, lift shadow brightness, and lean on emissive light sources so night is moody but navigable.

Your physically accurate night is so dark players bump into everything and complain. Games usually cheat night brightness upward so it reads as night while staying playable.

How to fix it

1. Set a night ambient floor

Clamp the nighttime ambient and moonlight to a minimum that keeps the scene readable, so night looks dark and blue but players can still navigate and fight.

2. Lift shadows and add fill

Raise the shadow/black point at night and add a subtle cool fill light or sky color so silhouettes stay visible instead of dissolving into pure black.

3. Encourage light sources

Make torches, lanterns, and the player's own light meaningfully brighten the surroundings so the dark feels like a mechanic rather than a visibility bug.

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 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.

Ship the fix, watch the signature disappear from the next build. That's how you know it's really gone.