The Dashboard
An in-game window for managing sims without typing. .dashboard opens it.
The pages
| Page | Open with | What’s on it |
|---|---|---|
| Home | .dashboard |
The hub |
| Party | .dashboard party |
Your members, their classes and levels, and the buttons to dismiss them |
| Nearby | .dashboard nearby · .nearby |
Invitable sims within ~1500 units, each with an Invite button |
| Commands | .dashboard commands |
Every command, in-game |
Party-affecting commands (.party, .invite, .inviteme, .dismiss) also open the Party page, so you
see the result immediately.
Why use it over typing
Buttons carry the target for you. Rather than needing to select a sim before .invite, the Nearby page
lists who’s around and each row’s button acts on that sim. Same for dismissing a member from the Party
page.
Under the hood
What the window is
The dashboard is rendered as client HTML and sent to you like any NPC panel, so it obeys the client’s own limits: a fixed tag set, no styling of our own, and a size cap on what one page can carry. Every button is a command the chat dispatcher already understands.
That has one useful consequence: anything the window can do, you can also type. The window is a convenience over the commands, not a separate capability.
Where this comes from
- Design:
docs/design/debug-observer-seam.md. - Live code:
shell/command/Dashboard.javabuilds the window;shell/command/CommandDispatch.javahandles what its buttons send.
Related
Voice Commands · Sim Party Mechanics
Page set verified against CommandDispatch.java:217-229 (Dashboard.Page HOME · PARTY · AUTOHUNT ·
NEARBY · COMMANDS) and the command→page routing at :162-164.