Down But Not Out set to OFF, but activates for one player in FFA

Summary

The Down But Not Out (DBNO) setting is explicitly set to OFF, however during live gameplay one player in the FFA is still being put into a knocked state as if DBNO were enabled. All other players behave correctly and are eliminated instantly.

This occurs despite DBNO being disabled at:

Island Settings

Team Settings

Player Settings (where applicable)

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Island Settings

Steps to Reproduce

Create or load an FFA island

Set Down But Not Out = OFF

Start a public or matchmaking session

Eliminate players until the issue occurs

One player enters DBNO instead of being eliminated

Frequency:
Intermittent but repeatable across sessions. Appears more frequently in matchmaking/live environments than editor testing.

Expected Result

All players in FFA should be eliminated immediately when their health reaches zero.

Observed Result

One player is knocked (DBNO state) instead of being eliminated, creating inconsistent gameplay in an FFA environment.

Reproduction Steps:

Platform(s)

ALL - Live Matchmaking

Island Code

9061-5458-7889

Additional Notes

Additional Notes:

This appears to be a state desync or team/FFA inheritance bug

Possibly linked to hidden team assignment or device override

Behaviour differs between editor testing and live matchmaking

Impact:
This breaks FFA rules, causes confusion for players, and negatively affects competitive balance and map reputation

Screenshot 2026-01-09 155051

This should NOT be happening on FFA.