LR WAR COMMAND — DESIGN BRIEF v0

Requested by Mags · 2026-09-03 21:47 TCT · status: PROPOSAL, AWAITING GO · one userscript for PC (Tampermonkey) and Torn PDA, fed by leadership assignments from this site · nothing here deploys for RW 48652

The verdict: yes. It is possible, and more than half of it is already running on this site. The enemy roster feed, the target scoring, the leadership control-panel pattern and the contributor key vault all exist for RW 48652. What is missing is three things: the userscript itself, a small assignment file with a leadership page to write it, and a check-in file so leadership can see who has the script installed. None of it needs a database, a login system, or anyone's API key on a server.

What already exists

Piece	Where	Status	What it gives the script
Enemy roster feed	war-room/targets-lr.json	LIVE	All 54 BCC members, refreshed every 20 min through Monday: state, hospital-until, online/idle/offline, last action, revivable, ELO, hold rate, hits won/lost, best damage, RW hits. The script reads this instead of hammering Torn itself.
Target scoring	war-target-board-lr.html	LIVE	THREAT and FARM axes, ranked within the enemy roster. Becomes the default sort inside the script.
Leadership control panel pattern	war-room/control-lr.php	LIVE	Password-gated PHP page that writes one JSON file. The assignment panel is the same pattern with a different form.
LR roster feed	war-room/roster-lr.json	LIVE	All 49 LR members with IDs. Group builder ticks names off this list; the script confirms the member is LR from it.
Contributor key vault	keyvault.html → offline	54 KEYS	Declared purpose already covers Fair Fight / battle-stat estimation and faction tools. Server-side enrichment only; keys never leave the vault.
RSVP board	war-rsvp-board.html	LIVE	Where the “script readiness” card lands: IN / PARTIAL / OUT next to INSTALLED / MISSING.
Userscript	lr-war-command.user.js	TO BUILD	The member side. Built on the war-page selectors from the TWSE fork and the 39X source, which are tested against Torn's actual DOM.
Assignment feed + panel	war-room/assignments-lr.json + assign-lr.php	TO BUILD	Groups, direct assignments, group assignments, priority, version stamp.
Check-in	war-room/checkin-lr.php + checkins-lr.json	TO BUILD	Script posts ID + name + version every few minutes. No key, ever.

Architecture

                       legitimatenexus.com
                              |
   leadership                 |                     members
   assign-lr.php  ---writes-->  assignments-lr.json  <--reads--  lr-war-command.user.js
   (password, same as           targets-lr.json     <--reads--  (Tampermonkey on PC,
    war-status control)         roster-lr.json      <--reads--   Torn PDA on phone)
   NEXUS via this line  ---writes-->                             |
   or #council                  checkins-lr.json    <--posts--   id + name + version
                              |
                       NEXUS refresh loop  (vault keys, server side)
                       rebuilds targets-lr.json every 20 min
                       -- member API keys stay on the member's device. Always. --

Two static JSON files do the work. The script polls assignments-lr.json every 30 s during a war and re-renders only when the version stamp changes. 49 members polling a static file twice a minute is nothing to the host; it is not 49 members hitting the Torn API.
Leadership assigns two ways. A form on the site (same LR password as the war-status control), or in plain words to NEXUS here or in #council: “put Moms_Spaghetti and Sassafras on Push Team” and the file is written within the minute.
Groups use the 39X convention. A negative player_id means “everyone in group N”. Kept on purpose so the mental model transfers from the script the faction already knows.

Where the ChatGPT design gets changed

1. Keys never leave the device. Not even once. The proposed registration step still sends the raw Torn key to the server one time to learn who the member is. That is not necessary. The script can ask Torn's API directly from the member's own browser (Torn permits cross-origin API calls) for player ID and faction, then check in with only the ID and name. On Torn PDA the app supplies the key to the script locally through its ###PDA-APIKEY### placeholder, so phone users never even type it. The site never sees a key, so there is nothing to leak, log, or be accused of storing. That also closes the exact concern Mags remembers about 39th.online.

2. Battle stats without TornStats. TornStats needs each member's own TS key and gives spies only where someone has spied. The default sort in LR War Command is NEXUS's own THREAT / FARM scoring, computed server-side from public stats for every enemy, every 20 minutes, and delivered inside the feed. Members with a TornStats key can paste it in as an optional overlay; it is stored locally on their device and called from their browser, never through us.

3. No “Load assigned targets” button. Sync is automatic and shows SYNC: LIVE · 12s ago. A new assignment pops a banner in the panel within 30 s of leadership saving it.

4. Torn PDA rules shape the code. One self-contained file, no @require, no external libraries. Only fetch, localStorage and the PDA key placeholder, so the same file runs unchanged under Tampermonkey and inside PDA without relying on PDA's GreaseMonkey shim. Mobile-first panel: it must be readable on a phone in a hospital bed at 03:00 TCT, because that is where wars are actually fought.

The member panel

LR WAR COMMAND                                    v0.1 · SYNC: LIVE 12s
------------------------------------------------------------------
3 ONLINE   2 IDLE   7 FARM   2 EXITING       enemy-only: ON

ASSIGNED   Moms_Spaghetti [1192893]   L72   Okay   Offline 1h
           hold rate 3.4%  ·  FARM #4  ·  est. score/hit  18.0
           [ ATTACK ]  [ NEXT ]  [ COPY CALL ]

PERSONAL   Sassafras [.......]        L45   Hosp 0:43  EXITING
PINNED     kingslayer [.......]       L61   Okay   Online

Assignments: 3   Personal: 1   Next up rotates: assigned → personal → pool

Three tiers, kept apart

ASSIGNED leadership gave you this target, directly or through your group. Always on top.
PERSONAL you pasted the ID yourself. Survives reloads, never overwritten by sync.
PINNED the one you are working right now.
FARM everyone else, sorted by the leadership-chosen order.

NEXT rotates in priority order

Assigned targets first, then personal, then the general pool of attackable enemies. If leadership has given you three names, NEXT cycles those three before it ever offers you the pool. Targets in hospital drop out of rotation until 60 s before exit, when they come back flagged EXITING.

Kept from TWSE

Real-time hospital and travel countdowns, corrected against the feed.
Incoming-attack detection, chain timer, rapid status refresh.

Kept from 39X

Focus targets, focus-to-top, individual and group assignments.
Battle-stat sort and filter, with NEXUS scoring as the default source.

New for LR

ONLINE-HOSP / IDLE-HOSP / FARM / LEAVE states, enemy-only mode, hospital-exit priority.
Hit-call copy button that pastes a clean line into Discord.
Assignment banner, automatic sync, readiness reporting.

Energy optimisation — what the script can actually rank on

Ranked-war score per hit is the respect the hit earns, and respect scales with the target's level, so a win against an L80 is worth roughly four times a win against an L20 for the same 25 energy. The other half of the equation is how often that target actually goes down. NEXUS already computes both halves for every enemy, and can publish a single expected score per hit figure in the feed: probability the target loses a defend (their hold rate, from public stats) multiplied by the respect their level pays. That is the number the FARM sort orders by. It makes “who should hit whom” an arithmetic question leadership can answer at a glance: the top of the list is the best return on a stacked energy bar, and the THREAT axis says which of those need a heavy hitter rather than a recruit.

Big hitters (high ELO, high best-damage, high RW hits) are flagged THREAT and get assigned to the High Stat group, not left in the pool for an L15 to bounce off.
Most active (last action, online pattern from the feed) are the ones worth the ONLINE-HOSP treatment: keep them in a bed so they cannot score.
Softest for the level is the FARM list. Best score per energy for the bulk of the faction.

Leadership side

assign-lr.php

Groups: name a group, tick members off the LR roster. Push Team, High Stat, Cleanup, Chain Watch, or whatever the war needs.
Assign: pick an enemy from the live feed (sorted by state and score), send to a member or a group, set priority 1–3, optional note (“keep in hosp”, “leave, he is bait”).
Save bumps the version; every script sees it within 30 s.

Readiness

LR members

from roster feed

Script installed

—

checked in this war

Missing

—

never checked in

Stale

—

no check-in for 24h

Lands as a card on the RSVP board next to the IN / PARTIAL / OUT tally, so one page answers both “who is coming” and “who can see their targets”.

Build plan

Phase	What	Who tests	When
0	This brief. Mags and Crysi confirm the shape; Mags uploads the TWSE fork and the 39X source to this channel so the build starts from tested war-page selectors.	—	now
1	Userscript v0.1: enemy panel from the feed, three tiers, NEXT rotation, PDA-compatible, no assignments yet.	Mags on PC + PDA, Crysi on PC	after BCC, wk of 7 Sep
2	Assignment feed, leadership panel, plain-words assignment through NEXUS. Script gains SYNC and the banner.	Mags, Crysi	same week
3	Check-in and readiness card on the RSVP board.	leadership	before next RW
4	Faction rollout: install guide page, one Discord announcement, readiness chased like RSVP.	everyone	next RW
5	Optional TornStats overlay with the member's own key, stored locally.	members who have one	later

Not for tomorrow. RW 48652 opens in eighteen hours. An untested script on a war-day phone is a way to lose a war, not win one. The BCC war runs on the live target board and Discord calls as planned; LR War Command is built this week and blooded on the war after.

Boundaries this design keeps

No member API key is ever transmitted to, stored on, or logged by legitimatenexus.com. Registration is ID + name only.
Contributor keys in the vault are used server-side, for the purposes contributors consented to, and never for anything the script displays about LR's own members beyond what the target board already shows.
Nothing about anyone's cash on hand is read, ranked, or shown. Standing operator ruling.
Everything is a file on this site under git: any change is revertable in one commit.

Live target board →BCC dossier →

NEXUS · Legitimate Remnants · design brief compiled 2026-09-03 21:55 TCT · supersedes nothing yet · v0