Skip to content

Shelved PR 539 t34 relic contested vehicle

rayswaynl edited this page Jul 3, 2026 · 1 revision

Shelved: PR #539 — T-34 relic contested vehicle (Lane 183 re-do)

State: Ray-shelved 2026-07-03 (Build 89 / cmdcon44 pick round). PR #539 was closed without merging; nothing from it is in Build 89. The feature was default-off and never live, so nothing needs to be reverted.

REJECT-SHELVED: Ray already ruled on the relic/gun objective family — see the earlier ruling below. This is a re-decision, not a fresh call.

WHAT

Adds a default-off contested-vehicle event: one uncrewed T34_TK_GUE_EP1 spawns at a neutral town at match start, neutral until the first player drives it. A 15-second scan loop claims it for that driver's side — updating wfbe_side_id, wiring the kill-bounty EH, and re-issuing setVehicleInit so JIP clients see the correct owning side. This is the same "capturable neutral relic" concept as the previously-shelved PR #388, re-implemented on a fable lane with review fixes.

WHERE

  • PR: #539 — "feat(lane183): T-34 relic contested vehicle [WFBE_C_T34_RELIC default 0]".
  • Branch / head commit: fable/lane183-t34-relic (head at shelve time; recover the branch tip).
  • Flag (if any): WFBE_C_T34_RELIC = 0 (default OFF, dark). At flag=0 the file exits before any vehicle is created — byte-identical to pre-PR behaviour.
  • Files touched: new Server/Server_T34Relic.sqf; Server/Init/Init_Server.sqf (flag-gated execVM); Common/Init/Init_CommonConstants.sqf (flag). Mirrored across all three maps; plus a JOURNAL.md entry. (Note: this is a distinct implementation from the earlier #388 — it uses the single master flag WFBE_C_T34_RELIC and derives the all-towns-owned fallback centre from WFBE_BOUNDARIESXY / 2, so ZG places near ~4096,4096 rather than the CH midpoint.)

WHY SHELVED

Ray already ruled "neither" on relics. On 2026-07-03 Ray was offered a choice between two "capturable neutral relic/gun side-objective" designs — the T-34 relic (#388) and the Arty Cache static-gun (#370) — and picked "C, neither" (recorded in Shelved-PR-388-t34-relic-capturable.md and Shelved-PR-383-...). PR #539 is a fresh re-implementation of the exact same T-34 relic concept, so it falls under the standing ruling: the whole neutral-capturable-relic space is declined for now. Shelved on the same basis; nothing to revert (default-off, never live).

HOW TO REVIVE

  • Recover from branch fable/lane183-t34-relic (tip at shelve time). Gated behind WFBE_C_T34_RELIC, so it reintroduces default-off with low risk. This implementation is cleaner than #388's (single flag, world-size-aware fallback centre, JIP side-bake fixed) — prefer it over #388 if the concept is ever revived.
  • Decide the design question first: Ray declined the entire "neutral capturable relic/gun" space (both #388 and #370, now #539 too), so a revival needs a fresh design pitch, not just a re-open. If reviving alongside any sibling objective (Arty Cache #370, comms-relay #538, TK SCUD site #309), pick ONE — they share the same niche.
  • In-engine validation owed before any live use: relic spawns near a neutral town; a WEST/EAST driver flips the map marker to their colour; a JIP client joining after a claim sees the correct side (not GUER green); the ZG fallback path spawns near map centre (~4096,4096) not the CH midpoint; and destroying the claimed relic exits the ownership loop cleanly.

Sidebar

Clone this wiki locally