A found-footage camera should lose its features one by one as the battery fades

Night vision, recording and the screen all eat power, and a battery that simply hits zero is dull. Here is how the camera sheds features at set levels, why switched-off modes must stop draining, and how to show a number that never lies about being empty.

Why this works

A slow loss of abilities tells a better story than a sudden stop, because the player sees the end coming and chooses what to keep. Only what actually works should use power, or the camera pays for things the player cannot use.

When not to use it

Do not use it when the device should work fully until it dies, such as a tool the player must trust in a tense scene. There, show the charge and cut it off at once, so there are no half-working states to puzzle over.

In the full entry

• What to build, step by step
• Starting values and the reason for each
• 3 common mistakes and the fix
• 30 lines of example code with 3 checks that pass
• How your AI shows you that it works

Say this to your AI

Use the Spielerando entry "A found-footage camera should lose its features one by one as the battery fades" (read_entry narr-camera-battery-feature-cutoffs) in my game. Build it step by step, and show me how you checked that it works.

Or skip this and connect the MCP: your AI then finds all of this by itself.Connect the MCP