Summary
In a private UEFN/Fortnite 42.10 Windows session, native Settings clicks reached a Verse PointerSelect.BeginDetectEvent callback while Settings remained visible. This can change underlying island selection. A counter-only diagnostic reproduced it without initializing board logic, custom UI, cameras or gameplay controls. Could Epic clarify whether this detection event is expected to receive native menu clicks, or identify the supported way to suppress them? No published-island reproduction or engine root cause is claimed.
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Verse
Steps to Reproduce
- In an existing single-player project, replace gameplay controller startup with a counter-only diagnostic. Leave existing native scene actors, but do not initialize board logic, custom UI, cameras or gameplay controls.
- Add TouchMapping and TraversalMapping once to the active player. Retain one PointerSelect.BeginDetectEvent and one Jump.BeginDetectEvent subscription. Callbacks only increment counters; no deprojection or board mutation.
- In normal gameplay, click once and press Space once: pointer=1, jump=1.
- Open the native Esc menu and click the gear, then click the Display category in Settings.
- Observe pointer increments to 2 at 14:08:19 UTC and to 3 at 14:08:49 UTC, September 6, 2026, while Settings is visible.
- Space alone in that Settings state did not increment Jump. Clicking Back incremented pointer to 4; after returning, a deliberate click and Space advanced counters to 5/2.
- End the game and unsubscribe. One subscription instance and generation were retained throughout the observations.
Expected Result
Native menu interaction should not reach island pointer-selection logic. The Virtual Pointer tutorial says it does not work when Fortnite game menus are open, and its screen-coordinate example subscribes to PointerSelect.BeginDetectEvent. Please clarify whether this promise includes detection callbacks.
Observed Result
The same raw PointerSelect subscription received the native gear, Settings Display-category, and Back clicks. The Display-category click incremented the counter while Settings remained visible. The tested Space press in Settings did not increment Jump; this does not establish isolation for all controls or menus.
Platform(s)
Windows PC; UEFN / Fortnite 42.10; private editor-launched session. Observed September 6, 2026 UTC. Not tested on a published island, console or mobile.
Additional Notes
Scope: this is business-logic isolation in an existing scene, not a blank-project reproduction or proof of engine root cause. Native scene actors and both mappings remained. The diagnostic compiled and ran privately, then was removed and ordinary gameplay restored.
Documentation clarification: the input_events(t) reference describes BeginDetectEvent as low-level detection that fires even if activation is canceled, and recommends TriggerActivationEvent for most bindings. But the Virtual Pointer tutorial itself uses PointerSelect.BeginDetectEvent while stating that the pointer does not work in Fortnite game menus. Does native menu suppression include detection callbacks, or only a different part of the pointer system? The public player_input API does not list a native-menu-open query/event.
Separately, switching PointerSelect to TriggerActivationEvent in the gameplay project still delivered menu clicks and was reverted. A normal UI button isolated the tested menu input, but focused Space activated that button and conflicted with independent Space confirmation; this is not being reported as a separate engine defect. No unsupported focus-property workaround is requested.
Filtered counter evidence (UTC, September 6, 2026; pointer/jump):
14:07:28 subscribed, instance 1, generation 3: 0/0
14:07:51 normal click: 1/0
14:07:59 normal Space: 1/1
14:08:19 native gear click: 2/1
14:08:49 Settings Display click: 3/1
14:09:40 Back click: 4/1
14:09:56 recovery click: 5/1
14:10:07 recovery Space: 5/2
14:15:09 OnEnd unsubscribed: final 5/2 (cleanup generation 4).
No account IDs, session endpoints, authentication data, screenshots or full client logs are included.
Please advise the supported mapping/event or native-menu gate, or whether a separate clean-project reproduction is required.