Summary
After the latest UEFN/Fortnite update, Down But Not Out starts enabling by itself after a session has been running for around 30–60 minutes. At the beginning of the session everything works correctly and players die instantly when eliminated, because DBNO is disabled everywhere. However, later in the same session, players start getting knocked instead of dying, even though no settings were changed.
Please select what you are reporting on:
Creative
What Type of Bug are you experiencing?
Devices
Steps to Reproduce
- Open or publish a UEFN island where Down But Not Out is disabled.
- Make sure Down But Not Out is set to Off in all relevant settings, including Island Settings, Team Settings, Class Designer, and Class Selector / class setup.
- Start a live/published session.
- Eliminate a player at the beginning of the session.
- Notice that the player dies instantly as expected.
- Keep the same session running for around 30–60 minutes.
- Eliminate a player again later in the same session.
- The player now gets knocked instead of dying instantly, even though DBNO is still disabled and no settings were changed.
Expected Result
Players should always die instantly when eliminated because Down But Not Out is disabled everywhere. The DBNO setting should remain Off for the entire session, no matter how long the session has been running.
Observed Result
At the beginning of the session, players die instantly as expected. After the session has been running for around 30–60 minutes, players start getting knocked instead of dying. It looks like Down But Not Out becomes active automatically during runtime, even though it is disabled in all settings and no device or setting was changed during the session.
Platform(s)
All the Platforms
Island Code
9862-4661-6699
Upload an image
Additional Notes
This issue started happening after update 40.40. Before update 40.40, this problem was not happening and DBNO stayed disabled correctly for the entire session.
This does not appear to be a configuration issue. If it was a wrong setting, the issue would happen from the start of the session. Instead, the session starts correctly and players die instantly, then after 30–60 minutes the behavior changes by itself and players begin getting knocked.
The issue is very damaging for live published islands because it breaks elimination flow, respawn logic, gameplay systems, and the player experience. The problem is also hard to catch in short testing because it only appears after the session has been running for a while.
Please investigate whether update 40.40 caused DBNO settings to be reset, overridden, or desynced during long-running published Creative / UEFN sessions.