From 5272a3db640eac735f22b5d8f530821e48492de8 Mon Sep 17 00:00:00 2001 From: Joe DiPrima Date: Thu, 13 Aug 2026 15:12:51 -0500 Subject: [PATCH] field guide: second reply mode added -- mark up the file itself and post it back (the Oracle workflow from the issues handout; spreadsheet exports welcome), alongside the per-section Discord replies --- docs/WEAPONS_FIELD_GUIDE.txt | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/docs/WEAPONS_FIELD_GUIDE.txt b/docs/WEAPONS_FIELD_GUIDE.txt index 7cb1d10..a57310e 100644 --- a/docs/WEAPONS_FIELD_GUIDE.txt +++ b/docs/WEAPONS_FIELD_GUIDE.txt @@ -15,9 +15,14 @@ if a section simply matches what you remember, a one-word "matches" is genuinely useful data. - HOW TO REPLY: in the Discord weapons thread, one reply per section, - starting with the section name in caps (e.g. "GAUSS:"). Then - MATCHES / CONTRADICTS / CAN'T RECALL, then whatever detail you have. + HOW TO REPLY -- two ways, both welcome: + (a) Discord weapons thread, one reply per section, starting with the + section name in caps (e.g. "GAUSS:"). Then MATCHES / CONTRADICTS / + CAN'T RECALL, then whatever detail you have. + (b) OR mark up THIS FILE the way the issues list gets marked up: add + your notes directly under any section (prefix lines with your + callsign) and post the edited file back to the thread. Spreadsheet + exports welcome too -- whatever is easiest keeps the data coming. Which floor, which revision, which mech you flew -- machine-room details turn weak memories into strong evidence.