Menu
Stop running DCLPulseTestClient bots gracefully. Use when the user wants to stop, kill, disconnect, or shut down the test client / bots.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Validate the full client↔server networking flow end-to-end — QUIC/UDP connect, DCL ECDSA handshake, movement, interest-managed state fan-out, and resync — by running two DCLPulseTestClient bots against a live server and cross-checking server logs, client logs, and per-transport Prometheus metrics. Covers ENet and WebTransport; WebTransport needs the extra cert/bind setup documented here. Use when asked to validate, verify, or smoke-test the end-to-end flow, especially over WebTransport.
Modify the Pulse wire protocol — add/change/remove messages, enums, fields, or quantization options in the .proto files and regenerate C# bindings. Use when the user wants to change the wire format, add a new Client/Server message variant, add or retune a quantized field, or otherwise touch the schema.
Add a defense against a specific network/protocol attack vector to Pulse — isolate protection in Hardening/ classes, wire it through config + metrics + docs, and verify with Rider inspections. Use when the user wants to add rate limiting, admission control, input validation, resource caps, replay protection, or any other server-side defense.
Add a new metric to the Pulse analytics layer — instrument, accumulate, snapshot, export to Prometheus, and display on the console dashboard. Use when the user wants to track a new server metric.
Launch DCLPulseTestClient bot(s) against a Pulse server. Use when the user wants to run, start, or launch the test client / bot / load test.
| name | stop-test-client |
| description | Stop running DCLPulseTestClient bots gracefully. Use when the user wants to stop, kill, disconnect, or shut down the test client / bots. |
| user-invocable | true |
| allowed-tools | Bash |
Gracefully stop running test bots so they disconnect cleanly from the server.
Find the process:
tasklist | grep -i DCLPulseTestClient 2>/dev/null || ps aux | grep DCLPulseTestClient 2>/dev/null
If no process is found, tell the user there are no running bots.
Create the stop signal file. The bot polls for this file every 500ms and triggers graceful shutdown (disconnects each peer, flushes ENet, then exits):
touch "$TMPDIR/dcl-pulse-test-client.stop" 2>/dev/null || touch "$TEMP/dcl-pulse-test-client.stop" 2>/dev/null || touch /tmp/dcl-pulse-test-client.stop
Wait for the process to exit gracefully:
sleep 3
Check if the process is still running. If it is, force-kill as a fallback:
tasklist | grep -i DCLPulseTestClient && taskkill //F //IM DCLPulseTestClient.exe 2>/dev/null || echo "Bots stopped gracefully."
On macOS/Linux fallback: pkill -9 -f DCLPulseTestClient