feat(rust): RaidableBases — feed, raids map layer, Warlord, Spawn a raid base, profiles (PLAN_REDESIGNS §11.4)
PLAN_REDESIGNS §11.4 (D202-D208, D386-D391), protocol 14. Spec: docs rust-link/PROTOCOL.md §20.12. - raid.started, raid.completed, raid.purchased and raid.locked public, raid.ended staff's; raidableBases.js reads each row per viewer (raiders' and a buyer's names only for the presence audience, D376/D390; Steam ids, position and a run's key only for staff). Feed lines in the World filter. - The step rust.raidbase.spawn, "Spawn a raid base" (ledgered, budget rust.raids): difficulty, profile and base from option sources listing each server's own names (D386), a spot as a world call's location with a height adjustment or an exact height, and PvP/NPCs/lock as on/off/blank. A base the raids helper made is a world resource, so eventWorld's revert and reconcile serve it and world.expired marks it expired; one it did not make records nothing and the run log says it despawns on its own timer. Refused at verify for a server that said it cannot; a dry run with a spot returns the spot check as detail.warnings (MODULE_API 1.16.0, D391). rb-not-ready retries in ten minutes. - Warlord: raids_completed, title category raidscompleted, the leaderboard's Raid bases column (sort=raidsCompleted). - The map's raids layer (D114), public by default with its own audience; the run's key is dropped before any viewer gets it. - Server settings' line for RaidableBases; its profiles in Mod configuration under a virtual path (D205). - Swagger fragment, bundle and README. Tests: server 684/684 (raidableBases.test.js new, every name in it invented); client 99/99, build and externals. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01E14m6SuuY6i1vASFeGDBeY
This commit is contained in:
13
README.md
13
README.md
@@ -144,6 +144,19 @@ one now, kept when the run ends: an airdrop or a patrol helicopter can be sent t
|
||||
alone — and the run log says so. Refused where Guarded Crate or NpcSpawn is absent, where the event
|
||||
is not one the server has, or where the framework cannot run its console command
|
||||
(`docs/modules/rust/PLAN_REDESIGNS.md` §14.3.5).
|
||||
- **RaidableBases** (nivex, 3.2.2, free or paid), with **CopyPaste** to paste its bases, and the
|
||||
**raids helper** `RunicGatewayRaids.cs` the plugin ships beside the bridge. With them: a base
|
||||
appearing, raided, bought or locked to a player are public feed lines (*"Alice and Bob raided a Hard
|
||||
raid base · G7"*, the names only for the presence audience), every live base is on the live map's own
|
||||
**Raid bases** layer (public by default, set in Admin → Rust visibility), the **Raid bases**
|
||||
leaderboard column and the *Warlord* title count the bases a player raided, and the step **Spawn a
|
||||
raid base** spawns one: at a difficulty, a profile or a named base, where RaidableBases picks or at a
|
||||
spot, with its own PvP, NPCs, despawn time and lock. That base is the event's, despawned when the run
|
||||
ends. A dry run checks a spot and says what is in the way, as advice. Every difficulty, profile and
|
||||
base name is the server's own. Without the helper the step can still ask RaidableBases for a base
|
||||
where it picks, but it despawns on its own timer, and the step says so. RaidableBases' profiles are
|
||||
editable from **Mod configuration**, reloaded and rolled back like any config
|
||||
(`docs/modules/rust/PLAN_REDESIGNS.md` §11.4).
|
||||
- **ZLevels Remastered** (nivex, 3.3.1). The servers page says whether it is loaded, and that is all:
|
||||
its levels are never read, and the leaderboard has no column for them. Its XP boosts are its own
|
||||
permissions (`zlevelsremastered.vip1`–`vip3`), so a *Double XP weekend* is a **Permissions until the event ends**
|
||||
|
||||
Reference in New Issue
Block a user