Files
runicgateway.com/src/content/docs/docs/rust/who-sees-who-is-online.mdx
wtclaude 75c8ffc07a
All checks were successful
PR checks / checks (pull_request) Successful in 2m5s
feat(docs): phase 15 - the Rust group, its reference pages checked against their sources
PLAN.md §16 phase 15. A Rust group of fifteen pages after Ultima Online
(D70): the module, installing the bridge (installer, Pterodactyl egg, by
hand), connecting the site, verifying the bridge, linking Steam accounts,
permissions and groups, mod config, who sees who is online, events, zones
and rewards, optional plugins, the live map, troubleshooting, and three
reference pages - rust-link's sidecar.toml, the plugin's
RunicGateway.json, and the event kinds.

checkReference.mjs gains three Rust sections rather than a new check:
sidecar.toml keys and RUSTLINK_* overrides from Rust-Link config.rs,
RunicGateway.json from the plugin's PluginConfig, and the event kinds
in three classes against Module-Rust server/catalogue.js (D71). Every
admin screen was walked on the walk site before it was described (D36).

Core pages now hand off to the Rust group instead of linking out to the
docs repository. Three defects the re-read found here are fixed: the UO
/health sample's hard-coded protocol 4 (both games' samples now render
platform.json through <Code>), Authentication's missing Steam tab, and
two pages saying the site cannot reach EventsEnabled - false on Rust.

Installer v0.8.1 moved checkFacts red mid-phase; platform.json follows.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
2026-10-22 15:23:07 -05:00

86 lines
4.1 KiB
Plaintext

---
title: Who sees who is online
description: Admin → Rust visibility — nothing names a player by default; where an operator widens that, for presence, clan rosters, news in game chat and each live-map layer.
---
import { Aside } from '@astrojs/starlight/components';
**Nothing on the site names who is online unless you choose to show it.** That covers more than
the Online tab: the joins, deaths and chat in each server's feed, and the leaderboard's *last
seen*, all say that a named player was on at a given moment. **How many** players are online is
always shown — a count is never a name.
**Admin → Rust visibility** (`/admin/rust/visibility`) is where an operator widens that, on
purpose. Every setting has a fleet-wide default and a per-server override.
## The audiences
Each setting picks one of three audiences, narrowest last:
| Audience | Who |
|---|---|
| **Everyone** | Anybody, signed in or not |
| **Signed-in members** | Anybody with a site account |
| **Staff only** | Admins and moderators |
## Who is online
The default is **staff only**. It decides who sees a **named** player: the Online tab, and the
feed's [presence kinds](/docs/rust/event-kinds/#presence) — joins and leaves, respawns, deaths,
chat, the per-minute tally, and the death of a RunicNPC boss, which names its killer. Below it,
the public feed carries only what names nobody: a wipe, a start, a shutdown, a world event.
## Clan rosters
Who is in each clan, on every server. The default is **the clan's members and staff**: players
whose linked Rust account is in the clan, plus admins and moderators. Each clan's name, colour,
score and member count are always public.
## News in game chat
Per server: **off**, **in chat**, or **as a popup**. When a news post is published, its title is
said on every server switched on here. A server that is down at that moment is skipped rather
than told late. A popup needs PopupNotifications on that server; one without it refuses the post
and says why.
## The live map
The map's **picture** is always public: it is drawn from the map's seed and says nothing about
who plays. Everything that moves on it is a **layer**, and each layer has its own audience:
| Layer | What it shows | Default |
|---|---|---|
| **Monuments & world events** | Cargo, helicopters, Bradley, supply drops, locked crates, and RunicNPC bosses placed outside an event | Everyone |
| **Site events** | The zones, crates and NPCs this site's events placed, while they run | Everyone |
| **Players** | Where everybody is, with names, and the sleepers | Staff only |
| **Bases** | Tool cupboards and vending machines, as positions only | Staff only |
| **PvP zones** | Dynamic PVP's own zones. Needs Dynamic PVP on the server | Everyone |
| **Raid bases** | RaidableBases' live bases and when they despawn. Needs RaidableBases | Everyone |
**The players layer can never show more than *who is online* does**, whatever it is set to here.
**You and your clan**, on by default, lets a linked player see themselves and their online clan
mates whatever the players layer says.
Per server, this section also says how many monument labels the map has and how many are hidden,
and where the map's picture came from, with **Fetch again**. See
[The live map](/docs/rust/the-live-map/).
<Aside type="note" title="Why the default is the narrowest one">
A feed that says a named player was on at 3 a.m. is a record of somebody's evenings. So nobody's
presence is published until an operator decides it should be, and a new server follows the
fleet's default rather than starting open.
</Aside>
## What this does not cover
Some kinds never reach a public page at any setting: IP addresses, player reports, bans, who
destroyed whose base, and permission changes are [staff-only kinds](/docs/rust/event-kinds/#staff).
They are not on this screen because there is nothing to choose.
## Canonical documents
[`rust-link/PROTOCOL.md`](https://gitea.whitlocktech.com/RunicGateway/docs/src/branch/main/rust-link/PROTOCOL.md)
§8.5 sets out why the boundary is the module's, and
[`modules/rust/PLAN.md`](https://gitea.whitlocktech.com/RunicGateway/docs/src/branch/main/modules/rust/PLAN.md)
§23 records the presence rule.