All checks were successful
PR checks / checks (pull_request) Successful in 2m10s
PLAN.md §16, D63/D64, plus D67-D69 taken 2026-10-22. - Core docs use core's words: a Team, a game server, the sidecar, the bridge plugin, the game module. Detail that belonged to Ultima Online moved into its pages rather than being dropped. - New "Ultima Online" sidebar group (nine pages): an overview, Connect a ServUO shard, Verify the bridge, The shard connection, Client files, Troubleshooting, Bridge.cfg, sidecar.toml, Shard event catalog. Five moved URLs answer a real 301 (src/config/redirects.mjs, asserted by the served test). - Getting started is game-neutral. "Connect your game server" keeps the old URL and hands off to each game; Rust links docs main:rust-link/INSTALL.md until phase 15. "Verify the whole stack" stays, neutral (D69). - D68: GameExample.astro labels a game's real example on a core page with the game's name; checkTerms allows that game's words inside it. - scripts/checkTerms.mjs, the twelfth check: 16 game words, docs pages and both sidebar trees, one allowlisted phrase (Discord's "Guild (server) ID"). Wired into verify and pr-checks.yml. - canonicalDocs grouped by game; the Rust group carries four documents. - D67: the screenshot rule from #32 is adopted. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
123 lines
6.4 KiB
Plaintext
123 lines
6.4 KiB
Plaintext
---
|
|
title: Teams
|
|
description: Core owns the Team machinery and cannot create a Team. What that means in practice, and what the admin screen controls.
|
|
---
|
|
|
|
import { Aside } from '@astrojs/starlight/components';
|
|
|
|
Teams are a core platform primitive: membership, roles, forums, notifications, moderation
|
|
and the Discord integrations are all core's, and none of it knows what a Team *is* in your
|
|
game.
|
|
|
|
**Core cannot create a Team.** Teams arrive from the installed game module, which maps
|
|
whatever the game calls its groups of players onto a Team. On a deployment with no module, the Team machinery is
|
|
present and permanently empty. That is not a bug to work around; it is the contract that
|
|
lets the same forum, notification and moderation code serve any game.
|
|
|
|
<Aside type="note" title="What that means when you are looking at an empty screen">
|
|
*No Teams in the projection yet* on a site with no module installed is the correct and
|
|
final state. Install a module, connect its game server, and Teams appear as that module
|
|
reconciles them.
|
|
</Aside>
|
|
|
|
## The projection, and why it can be stale
|
|
|
|
**Admin → Teams** shows a sync panel per module: last attempt, last success, consecutive
|
|
failures and the last error, with **Sync now** and **Resync now**.
|
|
|
|
The wording on that panel is exact and worth reading. Until a sync has succeeded, it says
|
|
that core has never had an answer it could trust, and that the list below it is not a
|
|
confirmed empty one.
|
|
|
|
An empty list therefore means one of two very different things — there are no Teams, or
|
|
nobody could ask. The panel tells you which: a *last success: never* with a *last error*
|
|
that names the game connection is the second. Fix the game module's connection to its game
|
|
server and sync again. Each game's group in the sidebar covers its own connection screen.
|
|
|
|
## Forums
|
|
|
|
Team forums are switched on site-wide in **Settings**, along with whether images are
|
|
allowed and how long an author may edit a post — see
|
|
[Configuration](/docs/administration/configuration/).
|
|
|
|
Two rules are structural rather than settings:
|
|
|
|
- **A Team's leaders moderate their own forum.** That is the point of a Team forum.
|
|
- **Reports about that forum do not go to them.** They go to site staff, because a report
|
|
about a leader has to reach someone above them. See
|
|
[Moderation](/docs/administration/moderation/).
|
|
|
|
## Team notification emails
|
|
|
|
**Team emails are sent by the engagement rules, and they arrive switched off.**
|
|
|
|
Someone posting in a Team forum used to send mail with no configuration at all. It now goes
|
|
through the same engine as everything else the site sends: the forum post raises an event,
|
|
an **engagement rule** decides who is told and through which message template, and the
|
|
outbox delivers it. Push notifications to the app and the Discord bridge below are
|
|
unaffected — only the email moved.
|
|
|
|
The practical consequence on an existing site: **nobody gets Team email until you turn a
|
|
rule on.** Open **Admin → Engagement → Rules**. Four rules are waiting there, one per Team
|
|
event, all switched off, and the screen says so at the top for as long as they all are.
|
|
Switch on the ones your site wants.
|
|
|
|
| Rule | Sends when |
|
|
|---|---|
|
|
| **Team forum posts** | someone posts a new thread or reply |
|
|
| **Team announcements** | a leader posts an announcement |
|
|
| **Team — new member** | someone joins, at most once an hour per person |
|
|
| **Team — leadership change** | a new leader is named, at most once an hour per person |
|
|
|
|
The first two are the ones most sites want. The last two describe things that already show
|
|
up on the Team's activity feed and arrive from a sweep rather than from a person doing
|
|
something — which is why they ship off and with a cooldown.
|
|
|
|
<Aside type="note" title="Members still control their own mail">
|
|
A rule decides whether the site sends at all. Each member still chooses, per Team, between
|
|
no email, one message per post, and a daily digest — on their own notifications screen or
|
|
through the unsubscribe link in any Team email. Turning a rule on does not sign anybody up.
|
|
</Aside>
|
|
|
|
**Digests are re-read at the moment they are sent**, not assembled as posts arrive. A site
|
|
that was down for two days sends one digest rather than two days of backlog, a post a
|
|
moderator hid is not in it, and somebody who lost access to a forum between the post and the
|
|
send does not receive it.
|
|
|
|
**Unsubscribe links keep working.** A link in mail sent before this change still does what
|
|
it says. What changed is that it is now precise: it stops the emails it came with and leaves
|
|
that Team's push notifications alone, where before it silenced both.
|
|
|
|
You can change what any of these messages say — see
|
|
[Message templates](/docs/administration/message-templates/) — decide which of them are sent
|
|
at all under [Engagement rules](/docs/administration/engagement-rules/), and see who was
|
|
actually sent what in **Admin → Engagement → Send log**.
|
|
|
|
## The Discord bridges
|
|
|
|
Two integrations, both optional, both configured from **Admin → Teams**.
|
|
|
|
**Notification bridge** — sends Team notifications to a Discord channel: a default for
|
|
every Team, overridable per Team. A message is sent once and never retried; the bridge is a
|
|
courtesy, and nothing on the site depends on it arriving. With nothing configured, no Team
|
|
event leaves the site.
|
|
|
|
**Voice channels** — gives each Team a Discord voice channel of its own, with access
|
|
granted by a per-Team role, so a Team's members can see and join theirs and nobody else
|
|
can. It needs the bot reachable, and members need a linked Discord account and membership of
|
|
your Discord server.
|
|
|
|
Its three settings deserve a thought each:
|
|
|
|
| Setting | What it decides |
|
|
|---|---|
|
|
| **Minimum members** | How large a Team must be to get a channel. Every active member counts, linked account or not. |
|
|
| **Grace window (days)** | How long a Team keeps its channel after it stops qualifying. A Team that recovers inside the window keeps the same channel; zero removes it on the next pass. |
|
|
| **Staff roles** | Roles that can see and join every Team's channel. Discord server administrators already can, so this is for staff who are not administrators. |
|
|
|
|
<Aside type="caution" title="Voice channels are a per-server ceiling, not a per-Team one">
|
|
Discord's role and channel limits apply to the whole Discord server, so a site with many small Teams
|
|
can exhaust them. The minimum-members setting is the lever that keeps the count sane, and
|
|
it is easier to raise it before provisioning than to unpick channels afterwards.
|
|
</Aside>
|