# \[Input Trigger\] PressedEvent never fires while player is eliminated, but works normally after respawn 

**URL:** <https://forums.unrealengine.com/t/input-trigger-pressedevent-never-fires-while-player-is-eliminated-but-works-normally-after-respawn/2857159>\
**Category:** Issues and Bug Reporting\
**Tags:** fortnite-creative, unreal-editor-for-fortnite, bug-report, fortnite\
**Created:** [November 17, 2026, 4:10pm UTC](https://forums.unrealengine.com/t/input-trigger-pressedevent-never-fires-while-player-is-eliminated-but-works-normally-after-respawn/2857159 "2026-11-17T16:10:05Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![wook3024](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@wook3024](https://forums.unrealengine.com/u/wook3024)\
**Post date:** [November 17, 2026, 4:10pm UTC](https://forums.unrealengine.com/t/input-trigger-pressedevent-never-fires-while-player-is-eliminated-but-works-normally-after-respawn/2857159/1 "2026-11-17T16:10:05Z")

</div>

### Summary

The input\_trigger\_device consistently fails to detect player input while the player is fully eliminated and waiting to respawn.

The issue is 100% reproducible in our tests and affects multiple keyboard and mouse inputs, including Q, E, Tab, Left Mouse Button, Right Mouse Button, and Middle Mouse Button.

Input events work correctly while the player is alive and resume working normally after respawn.

This appears to be related to the player’s eliminated state rather than a specific key binding.

### Please select what you are reporting on:

Unreal Editor for Fortnite

### What Type of Bug are you experiencing?

Devices

### Steps to Reproduce

1. Create a UEFN island and place an Input Trigger device.
2. Configure the device to detect player input.
3. Subscribe to input\_trigger\_device.PressedEvent in Verse.
4. Start a game session and verify that the input events work while the player is alive.
5. Eliminate the player without immediately respawning.
6. While the player is fully eliminated and waiting to respawn, press the configured input.
7. Repeat the test with different inputs, including Q, E, Tab, Left Mouse Button, Right Mouse Button, and Middle Mouse Button.
8. Respawn the player and test the same inputs again.

### Expected Result

The Input Trigger should support detecting player input while the player is eliminated and waiting to respawn, allowing developers to implement custom manual respawn controls.

If input detection during the eliminated state is intentionally unsupported, this limitation should be documented and an alternative mechanism should be provided.

### Observed Result

- While alive: Input Trigger events work normally.
- While eliminated: No input events are received, regardless of the tested keyboard or mouse input.
- After respawn: Input Trigger events resume working normally.
- Reproducibility: 100% in our tests.

The issue occurs consistently and is not limited to a specific input binding.

### Platform(s)

windows

### Additional Notes

We are implementing a custom respawn system where players can manually respawn by pressing a key starting 1.7 seconds after elimination. If no input is received, they automatically respawn 20 seconds after elimination.

However, since the Input Trigger stops responding entirely during the eliminated state, implementing manual keyboard-based respawning is currently blocked.

This issue occurs in the fully eliminated state, not the Down But Not Out (DBNO) state.

Could Epic confirm whether this is intended behavior or a bug?

If this behavior is intentional, is there an officially supported way to detect keyboard or mouse input while a player is eliminated and waiting to respawn?
