Save Point device with "Save Loadout" removes active disguise on load, no Disguise device events fired

General Issues and Bug Reporting
, ,
1

Title: Save Point device with “Save Loadout” removes active disguise on load, no Disguise device events fired

Build: 6.0.0-59596594+++Fortnite+Release-43.00
Platform: PC

Summary
When a player has a disguise applied by a Disguise device and their data is loaded through a Save Point device with Save Loadout enabled, the disguise is removed. The Disguise device does not fire On Disguise Removed or On Disguise Broken (neither the device-specific nor the “Any” variants), so the device seems unaware that the disguise is gone.

Steps to reproduce

  1. Place a Disguise device with no damage and no destroy.
  2. Place a Save Point device. Set every save option to No except Save Loadout (Auto Save and Auto-Load off).
  3. Place a zone or trigger that calls Save Player on the Save Point device, and another one that calls Load Player.
  4. Bind On Disguise Removed, On Disguise Broken, On Disguise Removed Any and On Disguise Broken Any to HUD Message devices for debugging.
  5. Start a session and apply the disguise to a player.
  6. Trigger Save Player, then trigger Load Player.

Expected result
The disguise stays on the player after loading. Loading the saved loadout should only restore inventory items. If the disguise is removed for some reason, the Disguise device should at least fire On Disguise Removed or On Disguise Broken.

Actual result

  • The disguise is removed as soon as the player data is loaded.
  • None of the Disguise device events fire. The HUD Message devices never show.

Additional testing

  • All save options No, only Save Team = Yes: the disguise is not removed on load.
  • Only Save Loadout = Yes: the disguise is removed on load.
  • So the issue appears to be tied specifically to the Save Loadout option.

Impact
Any game that combines disguises with saving and loading inventory through the Save Point device (e.g. temporary inventory swaps in specific areas) loses the player’s disguise. Because no events fire, creators cannot reliably detect the removal and react to it.

3

Additional observation / suggestion (related to Save Loadout)

While testing this, I noticed something else about the Save Loadout option: the hotbar slot positions of weapons and items are not restored on load. After Load Player, the items come back, but in a seemingly random slot order instead of the order the player had when Save Player was triggered.

Steps to reproduce

  1. Use the same Save Point setup as above (only Save Loadout = Yes).
  2. Give the player several weapons/items and arrange them in a specific hotbar order.
  3. Trigger Save Player, then Load Player.

Expected / suggested behavior
Loaded items return to the same hotbar slots they occupied when the data was saved. This could also be an optional setting on the Save Point device (e.g. “Preserve Hotbar Slot Order”).

Actual behavior
All items are restored, but their hotbar slot positions change.

Why this matters
Players often arrange their hotbar deliberately (e.g. weapons first, then healing). When an inventory is saved and loaded temporarily, for example when entering and leaving an area, they have to rearrange their hotbar every time, which hurts the experience.

I’m not sure whether this is intended or a limitation of the current implementation, so I’m posting it as a suggestion. Since it’s about the same Save Loadout feature, it might make sense to look at both issues together.

4

The status of FORT-1189930 changed to ‘Needs Triage’. We are routing this to the appropriate team for investigation.

5

Here is another improvement to the save point device…