Skip to content

Shelved PR 388 t34 relic capturable

rayswaynl edited this page Jul 3, 2026 · 1 revision

Shelved: PR #388 — Capturable T-34 relic side-objective

State: Ray-shelved 2026-07-03 (Build 89 pick round). PR #388 was closed without merging; nothing from it is in Build 88/89.

WHAT

Adds a default-off "capturable relic" event: one uncrewed T-34 tank (T34_TK_GUE_EP1) parks near a resistance-held town, announced in chat with a yellow map marker. The tank is neutral until the first WEST/EAST/GUER crew boards it — that side claims it, the marker recolors to their color, and destroying the claimed tank pays the normal vehicle kill bounty like any other mission vehicle.

WHERE

  • PR: #388 — "[codex] lane183 capturable T-34 relic".
  • Branch / head commit: codex/lane183-t34-relic-capturable @ db341debab2a054d1365e32c5084da42714fcfc6.
  • Flag (if any): WFBE_C_T34_RELIC_ENABLE = 0 (default OFF). Tunables: WFBE_C_T34_RELIC_CLASS = "T34_TK_GUE_EP1", WFBE_C_T34_RELIC_START_DELAY = 20, WFBE_C_T34_RELIC_MIN_RADIUS = 70, WFBE_C_T34_RELIC_MAX_RADIUS = 150, WFBE_C_T34_RELIC_FUEL = 0.65.
  • Files touched: new Server/Server_T34Relic.sqf (99 lines); Server/Init/Init_Server.sqf (flag-gated execVM launch); Common/Init/Init_CommonConstants.sqf (6 constants). Mirrored across Chernarus, Takistan, and Zargabad; plus a JOURNAL.md entry.

WHY SHELVED

Ray was offered a choice between two "capturable neutral relic/gun side-objective" designs — this T-34 relic (#388) and the Arty Cache static-gun (#370) — and on 2026-07-03 picked "C, neither". Both sibling PRs are shelved together; neither side-objective is going into Build 88/89. The feature was default-off and never live, so nothing needs to be reverted.

HOW TO REVIVE

  • Recover from branch codex/lane183-t34-relic-capturable @ db341debab2a054d1365e32c5084da42714fcfc6; the whole feature is gated behind WFBE_C_T34_RELIC_ENABLE, so it can be reintroduced default-off with low risk.
  • Decide the design question first: Ray declined the entire "neutral capturable relic/gun" space this round (both #388 and #370), so a revival needs a fresh design pitch, not just a re-open.
  • Needs in-engine validation before any live use: marker visibility, board/claim timing, and confirming the kill bounty actually credits the claiming side.
  • If reviving alongside the sibling Arty Cache (#370), pick ONE — the two occupy the same "capturable neutral relic/gun" niche and shouldn't both ship.

Sidebar

Clone this wiki locally