Skip to content

Add the two preferences that landed since the rewrite - #121

Merged
ETWOYA merged 2 commits into
mainfrom
docs/preferences-catch-up
Oct 2, 2026
Merged

ETWOYA merged 2 commits into
mainfrom
docs/preferences-catch-up

Conversation

@dankoverride

Copy link
Copy Markdown
Collaborator

PreferencesConfigurationDescriptors on main now declares 25 preferences; the page documented 23.

The preferences work has merged to main since #112, so the page now describes shipped code rather than a branch — which was the open question when it was written.

Record teleport and fall diagnostics

advanced.arrivalDiagnostics, Advanced → Diagnostics. Off by default because it checks the ground every frame. The source says what it is for and the page now says the same: if you fall through the ground after a teleport, turn it on, reproduce it, send the log.

Show demo screens on platforms

advanced.demoScreens, Advanced → Demo. Reads demo-screen-1.csv through demo-screen-3.csv from the Demo folder in the app's data directory, and the data is fabricated. The page says so plainly — a screen of made-up telemetry that nobody labelled is worse than no screen.

Both are deliberately not agent-writable

The descriptors give reasons worth preserving:

a log that switched itself on or off is one nobody can trust when reading it later

an assistant that can switch made-up data on is a way to put fabricated numbers in front of someone as if they were telemetry

🤖 Generated with Claude Code

PreferencesConfigurationDescriptors on main now declares 25 preferences; the
page documented 23. The two new ones are both Advanced, and both are the kind a
reader needs rather than the kind they can infer.

Record teleport and fall diagnostics (advanced.arrivalDiagnostics). Off by
default because it checks the ground every frame. The source says what it is
for and the page now says the same: if you fall through the ground after a
teleport, turn it on, reproduce it, send the log.

Show demo screens on platforms (advanced.demoScreens). Reads demo-screen-1.csv
through demo-screen-3.csv from the Demo folder in the app's data directory, and
the data is fabricated. The page says so plainly, because a screen of made-up
telemetry that nobody labelled is worse than no screen.

Neither is agent-writable, and the descriptors give reasons worth preserving:
a diagnostic log that switched itself on or off is one nobody can trust when
reading it later, and an assistant that can turn on made-up data is a way to
put fabricated numbers in front of someone as if they were telemetry.

The preferences work has merged to main since the rewrite, so this page now
describes shipped code rather than a branch.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@dankoverride
dankoverride requested a review from ETWOYA as a code owner October 2, 2026 01:33
@ETWOYA
ETWOYA merged commit da32c8f into main Oct 2, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants