Checking your access…
This area is for the Ancient Warden moderation team. If you reached this by mistake, head back home.
Back to homeNewly created or renamed realms wait here until a reviewer clears them. Force rename confiscates a name (nobody can re-take it for 30 days).
A hold with no account uid refuses the name to everybody. A hold WITH an account uid is an exception grant: that one account may take that one name even if it hits the blocklist. Names are matched on their folded form, so spelling variants land on the same hold.
The list owners choose realm tags from. Deactivating a tag stops new selections and hides the directory filter; realms that already carry it keep it until their owner edits.
Every realm moderation action, including ones taken by realm owners and realm moderators, lands here with its reason. Escalation rows are denied attempts by realm-local actors against the owner, staff, or another moderator.
Capacity is sold from the operator-entered core counts only. A node's own reports are a cross-check display and can never change what placement sells. Enrollment tokens and node keys are shown exactly once.
Invalid or unauthorized access attempts, recorded append-only. Bot detection files its findings as system reports in the Reports tab; this feed is the raw evidence trail behind them.
Run a server update or a capacity stress test from here. The ops agent runs the task on the box and streams its log below. Only one task runs at a time.
Pulls the latest css/, js/, api/, assets/ and root *.html pages from GitHub into the stage folder, minifies css/js and the root pages (api and assets copied as-is), then Publish copies stage to the live site - api/config.php is never touched. When ops_dir is configured it also ships the web host ops tools (the top-level ops/*.php scripts) to that folder outside the web root, and writes aw-paths.php there so they can find the live api/. Publishing empties the stage, so re-publishing needs a fresh fetch. Runs in short automatic steps, so shared-hosting and Cloudflare timeouts can’t kill it - if a step is dropped, just click the button again to resume.
If the server cannot reach GitHub, download the repository zip yourself and stage it from here - this never contacts GitHub from the server.
Plain text: blank lines split paragraphs, bare links become clickable. It goes out in the standard Ancient Warden email template with each subscriber's own one-click unsubscribe link. Preview first, test-send to yourself, then send - only confirmed subscribers are ever mailed.
Which places we advertise Keeper and realms are actually working. Every number here is a count of events, never of people: nothing that could identify a visitor is collected, so there are no unique visitors, no funnels per person and no way to drill into anyone. Visitors who send Do Not Track or Global Privacy Control are not counted at all.
Loading…
Loading…
This checks the api/ side (bans, rate limits, IP history). The WebSocket/game server trusts forwarded headers separately, via its own TRUST_PROXY env var (see docs/OPS.md).
Emergency switches. Turning one off blocks that entry point for everyone right away. Player login also revokes existing non-staff sessions; they can’t refresh, so they end within about an hour. Staff can always still sign in and stay signed in.
Add an issue to a component and the status page shows that colour and your message. The page still runs its own checks; the worse of the two wins. Clear the notice when it is resolved.
Loading…