HUD Surfaces
Configure HUD Output
1
Check the visible status
Check the attempt status and policy state before enabling submission-oriented displays or attempt-changing widgets.
2
Enable one surface at a time
Turn on the base row in the Labels tab, then open the popup to configure rows, labels, colors, or display limits.
3
Check suboptions
Read any suboption policy badges. History pinning, timer freeze, and similar behavior can carry a different policy from the parent.
4
Test in a room
Close the overlay and confirm the widget appears where expected without covering gameplay-critical information.
Input Tools
Use the input viewer to see your current inputs as a text chord. Use input history to review recent inputs after movement, death, or a routed attempt. Enable the control display for a visual overlay of which keys or buttons are pressed. Check inputs per second to monitor your press rate. Input displays show local inputs without changing gameplay. Anything that synthesizes or redirects inputs sets the attempt status to Cheat.Room Stats and Labels
The Room Stat Tracker shows room name, deaths, timer, berry count, and alive time in the label HUD. Its freeze behavior is a tracker suboption with its own policy badge - check it separately from the base label. Use Custom labels when you want to build your own HUD text from Akron variables, event triggers, and label-specific styling.Streamer Mode
Streamer Mode hides local filesystem paths in Akron-owned UI and proof output. It is a presentation setting, not a gameplay mutation or a general privacy mode.