Keybind 'Reset Building' causes an Editing Bug

Summary

There’s a bug with the new “Reset Building” bind in Fortnite. When sprinting, using the reset bind causes the game to hover in edit mode instead of completing the reset. If the player then swaps to another weapon or item while still sprinting, they get stuck in edit mode; unable to shoot but still able to aim down sights (ADS) and select tiles as if editing. This makes building resets unreliable and interrupts normal combat flow, as players can’t fire or properly exit edit mode until pressing their edit key again.

Please select what you are reporting on:

Creative

What Type of Bug are you experiencing?

Character

Steps to Reproduce

  1. Edit any build so that it is reset-able for next steps.
  2. Start sprinting and remain sprinting while follow the next two steps.
  3. Use the “Reset building” bind to reset build piece. (Not the “Reset building edit” bind)
  4. Swap to a weapon, build bind, or Pickaxe. And you can now stop sprinting.

Expected Result

The Expected outcome would be to have the build pieces that have been edited to be reset while pressing the bind in sprint. And when switching inventory, build binds or pickaxe after attempting to reset build while sprinting, be out of edit mode!

Observed Result

The build piece does not reset while sprinting until you also press Edit bind after “Reset building”. And when the Player also presses a slot while running, the player then can freely swap weapons, build binds and still will be stuck on editing mode for that building piece selected with “Reset building” bind. You can even ADS your guns while selecting the editing tiles. You will only exit it by pressing edit bind or building far away enough.

Platform(s)

Keyboard and Mouse

Video

I am the person who posted this. As of 24/10/2025 I’ve tried this bug again and noticed that the latest patch has fixed it! Thanks Epic Games, doubt they’ve seen this post but it’s very nice that the issue is resolved!

1 Like

Thank you for letting us know!

1 Like

FORT-1000394 has been ‘Closed’ as a duplicate of an existing known issue.