Report cumulative player scores alongside balances

t6/scripts/README.md

@@ -131,11 +131,22 @@ It sends four event types over the life of a match, mirroring the T5 script:
 
 Each event payload includes `event`, `server`, `map`, `match`, `seq`, `round` (except `game_start`)
 and a `players` array with `name`, `guid`, `kills`, `headshots`, `downs`, `revives`
-and `score` per player. `guid` reads Plutonium's `player.guid` engine property
+and `score` plus `score_total` per player in stat reports. `game_start` includes
+only player identity. `guid` reads Plutonium's `player.guid` engine property
 (T5 uses the `player getGuid()` method — T6 has no such method, but the field is
 equivalent for identity purposes). `kills`/`headshots`/`downs`/`revives` read
 from T6's stock match counters in `player.pers[]`; missing or negative values
 are reported as `0`. `score` is the player's current spendable `player.score`.
+`score_total` reads `player.score_total`, the stock cumulative match score used
+by the final scoreboard. Spending does not reduce it; stock grants can opt out
+of adding to the total. Missing or negative totals report as `0`, independently
+of the balance. Deploy Electric Cherry's receiver support before these scripts;
+older payloads without totals remain valid and their totals are unknown.
+
+Stock `end_game` yields before `player_intermission` replaces the balance with
+the total. The reporter serializes both at the first end signal without yielding,
+so retries and replay keep the original balance and total. Custom end sequences
+must emit a supported end signal before overwriting the balance.
 
 Delivery uses one in-flight request and a FIFO queue. Every match receives a
 native-generated key; `seq` starts at 1 for `game_start` and increases at capture.