vwemirror/BT411
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

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

Browse Source
This commit is contained in:
Joe DiPrima
2026-08-13 15:12:51 -05:00
parent 510f4f4c1b
commit 5272a3db64
1 changed files with 8 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/WEAPONS_FIELD_GUIDE.txt
+8 -3
View File
@@ -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.