Summary
For some players, an Input Trigger device set to Standard Action > Fire never delivers PressedEvent to Verse, even though their weapon fires normally and the server sees their aim. Leaving and rejoining the island does not fix it. Any island that uses “shoot to select” menus, shootable 3D buttons, or click-based aim training becomes unusable for these players.
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Devices
Steps to Reproduce
We cannot trigger the faulty state on demand: it happens to specific players, and once it happens it stays with them. This is the setup that runs into it, plus what we see for an affected player:
- Place an Input Trigger device with:
- Input Type: Standard Action
- Standard Input: Fire
- Enabled At Game Start: On
- Consume Input: Off
- Show on HUD: Off
- Selected Team / Selected Class: Any
- Registered Player Behavior: Add Registered
- In a Verse creative_device:
- subscribe to InputTrigger.PressedEvent;
- on each player join (and again once their character exists), call InputTrigger.Enable() and InputTrigger.Register(Player);
- in the PressedEvent handler, run a camera ray (GetViewLocation / GetViewRotation + FindSweepHits) and activate whatever 3D button the player is looking at (teleport, start, reset, etc.).
- In the same device, a separate loop runs the SAME camera ray every server tick and highlights (turns green) the button under the crosshair.
- Publish. Island settings: Max Players = 1 (one player per server).
- An affected player (confirmed on PC) joins, equips any firearm, aims at a button and fires.
Expected Result
Every Fire press (the same button that fires the weapon) raises PressedEvent on the Input Trigger, and the button under the crosshair activates. This is what happens for most players.
Observed Result
For the affected players:
- The weapon fires normally.
- The aim highlight works: the button under the crosshair turns green. That highlight comes from our server-side Verse loop using the same camera ray as the click, so Verse is running and the server has the correct aim.
- Nothing driven by PressedEvent ever happens: no menu selection, no teleport, no Start/Reset, no 3D button of any kind, across the whole island.
- Leaving and rejoining does NOT fix it. With Max Players = 1, rejoining starts a new server, so island-side runtime state is reset. The problem goes with the player, not with the server.
- Other input paths still work for the same player: our menu still opens through a separate path (an emote Input Trigger or a remote item).
Our code never Disables or Unregisters this trigger. No other Input Trigger on the island has Consume Input enabled.
Platform(s)
PC (confirmed). Other platforms unknown. Fortnite 43.10.
Island Code
2930-7963-4380
Video
Affected PC player in our AIM lobby. 0:16–0:25: weapon firing at the “SHOOT TO SELECT” cards, cards turn green under the crosshair, nothing gets selected. 0:29: the menu opens through a different input path, which works.
Additional Notes
WHY THIS MATTERS
Shooting at things is the standard way to interact in aim trainers, edit/build training maps, 1v1 and box-fight lobbies, and any island with “shoot to select” menus or shootable 3D buttons. Our island (Blackoutz Training) routes almost everything through this one Input Trigger: picking a training, Start/Reset, bot lives, settings, and click-based aim scenarios. For an affected player the island is effectively dead, and rejoining doesn’t help, so they just leave. Any island using the same documented pattern (Input Trigger Standard Fire → PressedEvent → camera raycast) is exposed the same way. Most creators will never see it, because it only shows up as “this map doesn’t work for me” from a few players.
HISTORY: THE SAME SYMPTOM ON TWO INPUT TYPES
- Early October: identical report (“can’t interact with anything that uses the shot, even after rejoining”) while the trigger used Creative Input Action “Custom 1 (Fire)”. We assumed it was the player’s Custom 1 rebind.
- We switched the trigger to Standard Action > Fire (also so mobile players keep their native fire button).
- We had also added a fallback: subscribing in Verse to Character.WeaponPrimary through player_input. When a weapon shot arrived with no matching PressedEvent, we treated the trigger as muted for that player and ran the click from WeaponPrimary instead.
- We had to turn that fallback off (see below). Since then, reports of this exact symptom came back, now with Standard Action > Fire.
WHY WE CAN’T WORK AROUND IT
The only Verse alternative we know, subscribing to Character.WeaponPrimary, changes the mobile touch HUD. Subscribing makes the fire button jump back to its default position and size, ignoring the player’s custom HUD layout (about 3–5 s after joining). We guard it with player_input.PreferredInputMethod / AvailableInputDevices.Touch. The docs say Touch is a fixed platform capability, but in our test on a real phone the guard did not detect the phone, the subscription happened, and the custom fire button was reset again. So the only fallback either breaks mobile players or isn’t available to them
WHAT WOULD HELP
- A fix so the Standard Fire Input Trigger always delivers PressedEvent when the player’s Fire action is pressed.
- Or guidance on what player-side condition (keybinds, input device, a setting) can leave the trigger silent for a player across sessions, so we can detect it or tell players how to fix it.
- Or a way to listen to the native fire action in Verse (e.g. WeaponPrimary) WITHOUT changing the mobile touch layout, so creators can build a safe fallback.
We can provide more logs or a test build if useful.