From da617e6f8f90c519da006d5963d5a16ee94f517d Mon Sep 17 00:00:00 2001
From: arcattack <arcattackmusic@gmail.com>
Date: Sat, 25 Jul 2026 19:56:56 -0500
Subject: [PATCH] README + release notes: match reports UPLOAD THEMSELVES --
 stop asking testers to send them

The operator caught this: I had carried the old "please send the operator your
matchlog" instruction into the release notes, and the shipped README has said
it for a while.  It is out of date.

Since 2026-07-22 the client auto-uploads its match forensic log to the relay
after every round: btl4main.cpp:914 calls BTRelayUploadMatchLog() once
RunMissions() returns, and the console receives it on route -9 and saves it as
matchlogs/<peer>_<name> (btconsole.py:1026-1042).  content/matchlogs/ is
already full of them.

So the instruction was making every tester hunt down and attach a file the
operator already had.  Corrected to state the real contract, including the
gaps the auto-upload genuinely cannot cover:

  * RELAY modes only -- join.bat and join_lan.bat both set BT_RELAY, so both
    upload.  play_solo.bat and play_steam.bat set none, so those still need a
    manual send.
  * The upload fires when a round ends CLEANLY (after RunMissions returns), so
    a mid-round CRASH loses it -- exactly the case we most want the file for.
  * join.log is NEVER uploaded -- no mechanism exists -- so that one is still
    a manual ask, and is now called out separately rather than buried.

Also added the same correction to dist/RELEASE_NOTES_4.11.550.md.

The zip cut before this (BT411_4.11.550.zip) carries the stale README and must
be re-cut.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---
 players/README.txt | 13 +++++++++----
 1 file changed, 9 insertions(+), 4 deletions(-)

diff --git a/players/README.txt b/players/README.txt
index 8a635fa..91377ab 100644
--- a/players/README.txt
+++ b/players/README.txt
@@ -31,10 +31,15 @@ When a round ends your game AUTOMATICALLY rejoins for the next one
 Close the window to leave for real.
 If the game closes unexpectedly, send the operator content\join.log.
 
-AFTER A MULTIPLAYER SESSION: the game writes a small match report,
-content\matchlog_<date>_<time>_<number>.txt.  Please send the operator
-the newest one -- we combine everyone's files to verify damage, kills
-and scores worked correctly across all players.
+AFTER A MULTIPLAYER SESSION: the game writes a small match report
+(content\matchlog_<date>_<time>_<number>.txt) and, on join.bat /
+join_lan.bat, UPLOADS IT TO THE OPERATOR BY ITSELF at the end of each
+round -- you do not need to send it.  Please send one MANUALLY only if
+the game CRASHED mid-round (the upload happens on a clean round end, so
+a crash loses it) or if you were playing SOLO or over STEAM (no relay
+to upload through).
+IF ANYTHING CRASHED OR MISBEHAVED, send content\join.log -- that one is
+never uploaded and only exists on your machine.
 
 You start INSIDE the cockpit with the pod's MFD panels composited
 around the view (one window).  The red MFD buttons, radar rails and