In Fortnite, the update 11.50.1 was released today for PS4, Mac, Android, and Nintendo Switch. This patch is intended to finally fix a bug that annoyed players. We will show you what has changed.
What kind of patch is this? The update 11.50.1 became available on Xbox One and iOS on Tuesday, February 11, 2020.
Today, on February 12, the update is also available on the following platforms:
- Playstation 4
- Nintendo Switch
- Mac
- Android
On PC, the update 11.50.1 is also expected to be available soon according to Fortnite Status on Twitter
Update 11.50.1 finally fixes the annoying harvesting bug
What has the patch changed? The most important change fixed with the update is the harvesting bug.
Players could not harvest properly as the weak points were not counted. This cost a lot of time in the game, as it took twice as long to gather materials.
Now the weak points should be counted correctly again, allowing players to harvest faster.
Has the bug been fixed? Our author Eilyn Rapp downloaded the update and tested whether the bug was really fixed.
She encountered no problems. Therefore, the error should be fixed at least on the PlayStation 4.
Fortnite players were annoyed by the bug
As this bug affected players in the game and made them invest a lot more time into harvesting, they were understandably annoyed by this bug.
Player JOSE4251 posted a clip about this on reddit where many players reported. They do not seem too thrilled about this bug, and they write:
- “This is so annoying! I hope they fix this as soon as possible.”
- “The game is really unplayable on console because of this. I could gather the maximum amount of materials in one round before. Now I can be happy if I get 200 per material selection.”
- “I hate this! I will not play Fortnite anymore until this is fixed.”
Now that the bug seems to have been fixed on almost all platforms, players can go back to searching for materials.
Players participating in the Playstation tournament starting on February 15 can also be happy. Otherwise, it would have been quite a limitation.
Did you also have this bug? Are you glad it has finally been fixed?
