docs(plan): phase 15's other-repository findings are fixed
All checks were successful
PR checks / checks (pull_request) Successful in 2m42s
All checks were successful
PR checks / checks (pull_request) Successful in 2m42s
PLAN.md §16 recorded three phase-15 findings as reported rather than fixed. The org lead asked for them fixed the same day: Module-Rust #59 (24 decision numbers in admin copy, and "1 player holds one") and Rust-Plugins #45 (EventsEnabled's comment). The record now says so. Reading every EventsEnabled check for that comment also showed the switch applies at once when saved from the site's config editor, while the bridge's other settings wait for its next reload. RunicGateway.json now says that, and adds paying coins to what the switch stops. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
This commit is contained in:
@@ -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