The reload speed of Weapons is bugged, causing inconsistent reload time regardless of Rarity.

Summary

Various firearm-based weapons in Creative are bugged and have inconsistent reload speed. Halfway through the reloading animation, the animation speed may slow down or speed up depending on the weapon type, reload time, and rarity. It is the easiest to notice with the Legendary Maven Auto Shotgun, Common Rocket Launcher, Oscar’s Frenzy Auto Shotgun, and the recently added Mythic version of the EvoChrome Shotgun.

In some cases it can ruin a Creative / UEFN experience in terms of balance. The Heisted Explosive AR is a good example as it isn’t supposed to reload as fast as a normal Red-Eye Assault Rifle because it would be unbalanced, this bug altered its functionality.

Please select what you are reporting on:

Creative

What Type of Bug are you experiencing?

Assets

Steps to Reproduce

Equip a weapon that is common, legendary, or mythic rarity, fire it, and then reload it.

Expected Result

When reloading, the reload time should be consistent and match the reload time depending on the weapon rarity.

Observed Result

While reloading, the animation may slow down or speed up halfway through depending on the weapon rarity and type. Common rarity weapons may reload as fast as a legendary, or legendary weapons may have the reload speed of its common rarity counterpart or slower than that.

Platform(s)

PC, Xbox One, PS4, Nintendo Switch, Xbox Series X/S, PS5, & Mobile/Streaming platforms.

Additional Notes

This bug was first encountered with the release of Fortnite version v31.00 and it hasn’t been fixed since. This bug is not present anywhere in Battle Royale or Reload, it only happens in Creative and UEFN.

This bug is also affecting modular weapons using speed or drum mags.

The Gatekeeper Shotgun with a speed mag is slow.
Previously Mentioned Frenzy Auto Shotgun is very slow with a drum mag.
Warforged AR with a speed mag isn’t as fast either.

Someone told me the cause of this bug might be related to the Gameplay Mode: First Person device, however I don’t think that’s very likely as this issue was present before the device was even added to the game in update 31.30.

Could you try again today after the update and let us know?

I can confirm with the release of the 32.10 update, this issue is still present.

Here’s a YouTube video I’ve just uploaded that shows the issue. https://youtu.be/5X46jEO46-c