Files
Module-Rust/client/src/lib/mapEvents.js
wtclaude 549b3a5ffd
All checks were successful
PR Checks / client-build (pull_request) Successful in 25s
PR Checks / server-tests (pull_request) Successful in 31s
PR Checks / frozen-manifest (pull_request) Successful in 44s
feat(rust): Dynamic PVP's zones on the feed and the map (PLAN_REDESIGNS §14.3.3)
Stage 4 of the §14.3 integration plan, on protocol 14 (docs
rust-link/PROTOCOL.md §20.7).

- pvp.zone.created is a public kind, pvp.zone.deleted a staff kind. Each row
  is read per viewer by the new dynamicPvp.js: grid for everyone, the event's
  name only for Dynamic PVP's own vanilla events, position and zone id for
  staff only.
- The feed's world filter carries the opening: "A PvP zone opened around the
  downed patrol helicopter · G7 · for 10 min". It names nobody.
- The map gains a fifth layer, `pvp` (PvP zones), public by default with its
  own audience in Admin → Rust visibility, drawn as a red ring with its
  event's name.
- Server settings' plugin line names Dynamic PVP; the swagger schemas and
  route descriptions carry the layer and the integration (fragment
  regenerated); ci/bundle.json ships dynamicPvp.js; README lists it.

Tests: server 611/611 (dynamicPvp.test.js new, catalogue and map extended)
and every check; client 89/89 (feed and map tooltip), build and externals.

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

68 lines
2.6 KiB
JavaScript

// ── What an event marker says (runicnpc stage 8, D302, D303) ──────────────
//
// An NPC's marker says its name and its event; a boss is drawn bigger, and no
// health is shown (D303 — the server does not even send it). A boss placed
// outside any event is in the world layer as `kind: 'boss'` (D302).
//
// The event's title comes from core's public calendar, which publishes each
// run's id for this: a map row holds a run id and nothing else. The calendar
// lists announced events only, so an unannounced event is "an event" here and
// nothing more.
//
// Pure, and free of React, so it is tested in Node.
/** `{ [runId]: title }` from core's public calendar answer. */
export function titlesFrom(calendar) {
const out = {}
for (const e of (calendar && calendar.entries) || []) {
if (e && e.kind === 'run' && e.runId != null && e.title) out[String(e.runId)] = e.title
}
return out
}
/** The run ids an answer's events layer names that `titles` does not know yet. */
export function unknownRuns(events, titles) {
const out = new Set()
for (const e of events || []) {
if (e && e.runId != null && !Object.prototype.hasOwnProperty.call(titles || {}, String(e.runId))) out.add(String(e.runId))
}
return [...out]
}
/** The tooltip for one events-layer row that is not a zone. */
export function eventTip(row, titles) {
const event = (titles && row && row.runId != null && titles[String(row.runId)]) || 'an event'
if (!row || row.kind !== 'npc') return `Event crate · ${event}`
const who = row.name || 'Event NPC'
const role = row.boss ? ' (boss)' : row.add ? " (a boss's add)" : ''
return `${who}${role} · ${event}`
}
/** Whether a row is drawn as a boss: bigger (D303). */
export function isBoss(row) {
return Boolean(row && (row.boss || row.kind === 'boss'))
}
// ── Dynamic PVP's zones (protocol 14, PLAN_REDESIGNS §14.3.3) ──────────────
/** Dynamic PVP's own events as the map names them; a monument's or an operator's is shown as written. */
export const PVP_NAMES = Object.freeze({
Helicopter: 'Patrol helicopter',
Bradley: 'Bradley APC',
Satellite: 'Satellite crash',
TimedSupply: 'Airdrop',
SupplySignal: 'Signalled airdrop',
CargoShip: 'Cargo ship',
HackableCrate: 'Locked crate',
ExcavatorIgnition: 'Giant Excavator',
GhostShip: 'Ghost ship',
DeepSeaIsland: 'Deep Sea island',
IslandCannon: 'Island cannon',
})
/** A Dynamic PVP ring's tooltip: "PvP zone · Patrol helicopter". */
export function pvpTip(z) {
const name = PVP_NAMES[z.event] || z.event
return name ? `PvP zone · ${name}` : 'PvP zone'
}