Summary
When a Player opens Fortnite’s native system UI (e.g. inventory, map, settings, etc.) while multiple custom input-consuming UIs are active in a layered stack (not UI ZOrder), the lower-layer custom UI becomes permanently broken and cannot be reshown for the remainder of that game session–forcing the player to quit, which negatively impacts KPIs for the island.
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
UI/Tools
Steps to Reproduce
- Create multiple custom input-consuming UIs in a layered stack.
- Open any of Fortnite’s native system UI (e.g. inventory, map, settings, etc.).
- Close Fortnite’s native system UI.
- Close remaining custom input-consuming UIs.
- Try to access the custom input-consuming UIs again (will not work, 100% repro).
Expected Result
Normal UI Stack Management:
- When UI Layer 1 is open and UI Layer 2 is summoned, Layer 1 hides.
- When UI Layer 2 closes, Layer 1 reappears automatically.
- This works correctly when only custom UIs are involved.
With System UI Interaction:
- When Fortnite system UI is opened, custom UIs should properly handle the interruption.
- Upon closing system UI, custom UI stack should restore to its previous state.
- Lower-layer custom UI should be capable of reshowing when upper layer closes.
Observed Result
- Player opens custom UI Layer 1 (e.g., custom UI for Daily Quests) - input consuming, visible.
- Player opens custom UI Layer 2 (e.g., custom UI for detailed info on a Daily Quest) - input consuming, visible.
- Layer 1 correctly hides (expected behavior).
- Player opens Fortnite system UI (e.g. inventory, map, settings, etc.) while Layer 2 is open.
- Player closes Fortnite system UI and returns to game.
- Player closes custom UI Layer 2.
- Custom UI Layer 1 never reappears - it is now permanently broken for this session.
- This issue persists until Player leaves and starts a new game session.
Platform(s)
ALL - PC / Console / Mobile