tws-zombies-scripts/t6/README.md

TWS T6 Zombies scripts

Plutonium T6 versions of the T5 server scripts. Defaults live in the scripts, just like T5. There is no separate TWS config file or database setup.

File	Role	Dependencies
tws_t6_common.gsc	Shared HUD values, helpers and first-spawn dispatcher	Stock T6
tws_t6_hud.gsc	Match/round timers, name, zombie count and health bar	Common
tws_t6_afk.gsc	.afk / .back, protection, movement and weapon blocking	Common
tws_t6_lock.gsc	Lock at round 20; clear password on game over	Common, HUD
tws_t6_telemetry.gsc	HTTP JSON round updates, enabled by default	t6-gsc-utils

Install

1. Copy these five tws_t6_*.gsc files into Plutonium/storage/t6/scripts/zm/.
2. For telemetry, install t6-gsc-utils v3.1.1 in Plutonium/plugins/ and restart the server process. The other four scripts do not require that plugin.
3. Restart the map to load script updates.

If updating an existing deployment, remove tws_t6_db.gsc and tws_t6_bank.gsc from the server script directory. Copying the remaining files will not remove those old scripts. Remove any exec server.example.cfg added for the earlier version. Neither a database nor that config file is used anymore.

Source .gsc files load directly under Plutonium's documented T6 script layout. Keep the filenames and scripts/zm location so shared references resolve. To omit telemetry, remove its script; disabling it at runtime does not remove its plugin dependency during linking.

Defaults, matching T5

• HUD values live in tws_t6_common::common_config(). That function and ensure_config() came from T5; they initialize in-script values and do not load a config file. The requested fullscreen corner alignment is retained.
• AFK uses T5's native level waittill("say", message, player) listener. .back restores movement and weapons immediately, then ends protection after two seconds. The T6 control/weapon fix remains in place.
• Lock uses T5's HUD round/game-over notifications. Default threshold is 20. As in T5, it clears g_password at startup and game over.
• Telemetry is enabled by default and posts to http://192.168.1.199:3000/api/telemetry. Set tws_server_id to the exact, case-sensitive Electric Cherry registry name; missing or overlong names disable reporting with a console diagnostic.

The optional dvars already present in T5 are still supported: tws_lock_round, tws_server_id, tws_telemetry_url, and tws_telemetry_enabled (0 disables telemetry). None require a separate config file. If earlier settings are already set on the server, they still override these defaults.

Round telemetry

Telemetry runs directly in GSC using t6-gsc-utils. Configure the exact Electric Cherry registry name and full endpoint in your existing server configuration:

set tws_server_id "t6_zombie_town_1"
set tws_telemetry_url "http://192.168.1.199:3000/api/telemetry"

It sends the first occupied positive round and subsequent round changes:

{"event":"round_change","server":"t6_zombie_town_1","round":17,"players":4}

Delivery is asynchronous, with one in-flight request and one replaceable pending observation. Transport failures retry at most three times (1/2/5 seconds), retiring snapshots older than 15 seconds or superseded by a newer round. Transport success does not establish API acceptance. These reports update Fleet; they do not send beta boot, session, feature or match-completion evidence.

Validation

All five scripts compile for T6 PC with gsc-tool 1.4.10. To repeat:

.\tools\check.ps1 -CompilerPath C:\path\to\gsc-tool.exe

Compilation does not verify engine/plugin linking or gameplay. T6 differences, research sources and live checks are in NOTES.md.