docs(plan): phase 15's other-repository findings are fixed #36
19
PLAN.md
19
PLAN.md
@@ -2155,15 +2155,18 @@ game-neutral `--help` that phase 14 reported, fixed in `installer` #43 alongside
|
||||
the Teams panel — so `platform.json` moved to it. Its only change is that help text, which no page
|
||||
quotes.
|
||||
|
||||
**Findings in other repositories**, reported rather than fixed:
|
||||
**Findings in other repositories.** Reported in the PR, and then fixed at the org lead's ask the
|
||||
same day, each in its own repository's PR into `edge`:
|
||||
|
||||
- **`Module-Rust` admin copy shows decision numbers.** A group's *Servers* tab reads "unless it is
|
||||
shared (D189)", and the *not imported yet* chip's tooltip ends "(D198)". Neither means anything
|
||||
to an operator.
|
||||
- **`Module-Rust`'s servers page reads "Last pushed: 1 player hold one."** — the plural verb is
|
||||
used for one.
|
||||
- **`Rust-Plugins`' `PluginConfig.EventsEnabled` comment says it "gates taking a lease only"**.
|
||||
That stopped being true at protocol 9, when it began gating every world write.
|
||||
- **`Module-Rust` admin copy showed decision numbers.** A group's *Servers* tab read "unless it is
|
||||
shared (D189)", and the *not imported yet* chip's tooltip ended "(D198)". A search of every
|
||||
non-comment line found **24** such strings an administrator reads — the event editor's step and
|
||||
budget descriptions and five NPC validation errors among them. All went in `Module-Rust` #59; the
|
||||
developer-facing swagger descriptions keep theirs.
|
||||
- **`Module-Rust`'s servers page read "Last pushed: 1 player hold one."** Also `Module-Rust` #59.
|
||||
- **`Rust-Plugins`' `PluginConfig.EventsEnabled` comment said it "gates taking a lease only"**,
|
||||
which stopped being true at protocol 9. It now lists everything the switch gates, read from every
|
||||
check in the file: `Rust-Plugins` #45.
|
||||
- **`docs` `rust-link/INTEGRATION.md` predates the installer**: it says there is no installer
|
||||
support for Rust and shows protocol-1 samples. **`rust-link/INSTALL.md`'s by-hand step names two
|
||||
helpers**; the bundle ships three. The org lead approved a separate `docs` PR for these:
|
||||
|
||||
@@ -46,8 +46,12 @@ can be renamed for a season without losing its history.
|
||||
## The event bounds
|
||||
|
||||
`EventsEnabled` ships **off**. While it is off the site may still list and give back what events
|
||||
hold, so switching it off never strands anything; it may not borrow, place, count or say anything
|
||||
new. See [Events, zones and rewards](/docs/rust/events-zones-and-rewards/).
|
||||
hold, so switching it off never strands anything; it may not borrow, place, count, pay or say
|
||||
anything new. See [Events, zones and rewards](/docs/rust/events-zones-and-rewards/).
|
||||
|
||||
Saved from [Mod config](/docs/rust/mod-config/), **`EventsEnabled` takes effect at once**. The
|
||||
bridge never reloads itself, so its other settings apply at its next reload — a server restart,
|
||||
or a reload at the console.
|
||||
|
||||
Each `EventsMax…` key is how much **one step** may do on this server — or, for
|
||||
`EventsMaxWorldCalls`, one run, and for `EventsMaxTallies`, the whole server at once. Two rules
|
||||
|
||||
Reference in New Issue
Block a user