Fix bank GUID serialization on T5 and T6 (Refs #15)

t6/scripts/README.md

@@ -48,13 +48,21 @@ The optional `tws_t6_bank.gsc` adds `.b`, `.d <amount|all>` and
 `.w <amount|all>` and registers them in help. It requires common and telemetry
 `1.0.0` or newer, the TWS t6 plugin `1.1.0`, Electric Cherry's bank API and
 a private per-server credential. Follow [bank setup and recovery](../../README.md#player-bank-t5-and-t6),
-including a full process restart for the plugin. Bank `2.0.0` uses only
+including a full process restart for the plugin. Bank `2.0.0+` uses only
 `https://ec.thewrightserver.net/api/bank` and ignores `tws_bank_url`.
 Update EC agents to `1.9.1+` first. If the old endpoint differs, follow the
 [endpoint upgrade procedure](../../README.md#upgrading-the-bank-endpoint):
 an EC rebuild must settle legacy journals before the new scripts start.
 When the endpoint already matches, only a map restart is required.
 
+Bank `2.0.1` reads the persistent `player.guid` field used by telemetry and
+converts it to a string before requests or journal writes. Existing strings
+are preserved exactly; missing or invalid identities fail privately without
+changing points. Stock T6
+[`callback_playerconnect()`](https://github.com/plutoniummod/t6-scripts/blob/2d8440321602f22f63f5335817110d60ddf223d5/ZM/Core/maps/mp/gametypes_zm/_globallogic_player.gsc)
+populates that field before the `connected` notification. Follow the shared
+[identity and deployment checks](../../README.md#bank-identity-validation).
+
 ## Persistent Discord text
 
 The HUD shows `https://discord.thewrightserver.net` in small light-gray text
@@ -156,9 +164,9 @@ 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` 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
+only player identity. `guid` reads the persistent `player.guid` field populated
+by T6's stock connection initialization (T5 reads `player getGuid()` directly).
+`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