What causes a Godot shader still receiving light when it should be unshaded?

The shader writes to ALBEDO and relies on lighting instead of declaring render_mode unshaded and writing the final color, so it is shaded by scene lights.

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 a Godot Spatial Shader Still Being Lit After Setting It Unshaded

Quick answer: Add render_mode unshaded to the shader and write your color to ALBEDO (or EMISSION) so the surface ignores lighting and shows the flat color you intend.

Self-illuminated UI-style surfaces, holograms, and stylized flats should not respond to scene lights. In Godot a spatial shader is lit by default unless you opt out with a render mode. Here is how to fix it.

How to fix it

1. Declare unshaded mode

Put render_mode unshaded; after the shader_type line so the fragment color is used directly without diffuse or specular lighting applied.

2. Write the final color to ALBEDO

With unshaded, the value you assign to ALBEDO is the output color; there is no need to manage EMISSION or light functions.

3. Use EMISSION if you want bloom

If you instead want the surface to stay lit but glow into a glow/bloom pass, keep it shaded and raise EMISSION rather than going unshaded.

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.