T5 allows .afk while the player is downed #6

Open
opened 2026-10-12 10:09:28 -04:00 by goddard · 1 comment
Collaborator

On T5, .afk can be activated while the player is downed. The command grants invulnerability, suppresses zombie targeting, and freezes controls without first rejecting last stand.

  • tws_t5_afk.gsc:65-81 checks only whether the player is already AFK before setting ignoreme, calling enableInvulnerability(), and freezing controls.
  • T6 already rejects AFK entry during last stand through its player_active check; T5 needs the corresponding downed-state guard.

Fix

  • Reject .afk while a T5 player is downed/in last stand, before changing AFK state, protection, zombie targeting, or controls.
  • Show a clear message explaining that AFK cannot be entered while downed.
  • Verify in T5 that attempting .afk while downed leaves normal bleed-out and revive behavior intact and does not activate AFK protection.
  • Verify that, after being revived, the player can use .afk and .back normally.
  • Update the T5 live-check documentation to cover downed activation and successful activation after revival.
On T5, `.afk` can be activated while the player is downed. The command grants invulnerability, suppresses zombie targeting, and freezes controls without first rejecting last stand. - `tws_t5_afk.gsc:65-81` checks only whether the player is already AFK before setting `ignoreme`, calling `enableInvulnerability()`, and freezing controls. - T6 already rejects AFK entry during last stand through its `player_active` check; T5 needs the corresponding downed-state guard. **Fix** - [ ] Reject `.afk` while a T5 player is downed/in last stand, before changing AFK state, protection, zombie targeting, or controls. - [ ] Show a clear message explaining that AFK cannot be entered while downed. - [ ] Verify in T5 that attempting `.afk` while downed leaves normal bleed-out and revive behavior intact and does not activate AFK protection. - [ ] Verify that, after being revived, the player can use `.afk` and `.back` normally. - [ ] Update the T5 live-check documentation to cover downed activation and successful activation after revival.
goddard added the
priority
medium
type/bugtype/exploitgame/t5game/t6
labels 2026-10-12 10:09:28 -04:00
josh was assigned by goddard 2026-10-12 10:09:28 -04:00
goddard changed title from .afk gives instant invulnerability with no cooldown, and T5 allows it while downed to T5 allows .afk while the player is downed 2026-10-12 20:05:34 -04:00
goddard removed the game/t6 label 2026-10-12 20:05:34 -04:00
Author
Collaborator

Reviewed 3bb0b5178e. Unresolved; leaving open within the narrowed T5-only scope.

This review checks the current implementation against every acceptance criterion, regardless of commit references.

Checklist

  • Reject downed activation. t5/scripts/tws_t5_afk.gsc:65–80 checks only hud_afk_on before changing AFK state, ignoreme, invulnerability and controls. There is no last-stand guard.
  • Clear rejection message. The only entry message is AFK — type .back to return; no downed-state rejection exists.
  • Bleed-out/revive validation. The required guard is absent, so normal downed behavior after rejection has not been demonstrated.
  • Post-revive validation. No acceptance evidence establishes normal .afk/.back after revival with the requested fix.
  • T5 live checks. The T5 module documentation does not include the requested downed-activation and post-revive scenarios.

Review notes

  • T6 already has its own active-player guard; that does not fix T5. No cooldown or broader combat-activation policy is added to this ticket.

Next steps

  • Add the T5 last-stand guard before any state changes, provide a clear message, and validate/document both downed and post-revive paths.
Reviewed 3bb0b5178e40ea6d322093283edb39f160542a07. Unresolved; leaving open within the narrowed T5-only scope. This review checks the current implementation against every acceptance criterion, regardless of commit references. **Checklist** - [ ] **Reject downed activation.** t5/scripts/tws_t5_afk.gsc:65–80 checks only hud_afk_on before changing AFK state, ignoreme, invulnerability and controls. There is no last-stand guard. - [ ] **Clear rejection message.** The only entry message is AFK — type .back to return; no downed-state rejection exists. - [ ] **Bleed-out/revive validation.** The required guard is absent, so normal downed behavior after rejection has not been demonstrated. - [ ] **Post-revive validation.** No acceptance evidence establishes normal .afk/.back after revival with the requested fix. - [ ] **T5 live checks.** The T5 module documentation does not include the requested downed-activation and post-revive scenarios. **Review notes** - T6 already has its own active-player guard; that does not fix T5. No cooldown or broader combat-activation policy is added to this ticket. **Next steps** - Add the T5 last-stand guard before any state changes, provide a clear message, and validate/document both downed and post-revive paths.
Sign in to join this conversation.