The Fortnite Challenges for Week 3 of Season 5 Have Been Leaked - Dexerto

The Fortnite Challenges for Week 3 of Season 5 Have Been Leaked

Published: 23/Jul/2018 9:16 Updated: 10/Oct/2020 17:37

by Ross Deason


As has become a common theme in recent seasons of Fortnite, dataminers have once again leaked the weekly challenges that are expected to go live on Thursday, July 26.

Players around the world are already well on their way to unlocking the various skins, items, emotes and other cosmetics that are associated with the Season 5 tiers but week three looks set to be the most difficult so far.


According to Storm Fortnite Leaks, there will be a mixture of the usual challenges, like following a treasure map and searching chests in a specific location, and some more vague ones like destroying specific targets.

As reported by Forbes, this isn’t a datamining account that we have seen a great deal of in the past. But the leaked challenges, shown in the image below, do seem to make sense.


@fortnite_leaks / Twitter

If you can’t see the image, the leaked Week 3 challenges are as follows:

  • Deal damage to passenger vehicles (0/1000)
  • Destroy specific targets (?/?)
  • Use a Launchpad (0/1)
  • Search Chests in Fatal Fields (0/7)
  • Follow the treasure map in Flush Factory (0/1)
  • Explosive eliminations (0/3)
  • Eliminate Opponents in Haunted Hills (0/3)

There is currently no detailed information about the “destroy specific targets” challenge, so players will have to wait until Thursday to find out exactly what it is referring to.

The “deal damage to passenger vehicles” task clearly refers to the new All Terrain Kart (ATK) that was added to the game as part of the V5.0 patch at the start of Season 5.


As is always the case with these leaks, nothing is confirmed and all of the information is subject to change. You will need to wait until July 26 for the official list to go live but history tells us that most, if not all, of the leaked challenges will become a reality.


Epic Games reveal bug fixes coming in Fortnite v14.30 update

Published: 10/Oct/2020 12:38 Updated: 10/Oct/2020 12:40

by Connor Bennett


Epic Games have revealed some of the bug fixes that they’ve got lined up for the next Fortnite update, and a few annoying issues look set to be resolved. 

Fortnite Chapter 2, Season 4 is almost at its endpoint, some fans are already looking ahead to what the cinematic end of season event might have in store, as well as what Chapter 2, Season 5 could be about in terms of the theme.


Despite all the speculation, Epic Games are just cracking on with keeping the current season feeling fresh – releasing new challenges, new cosmetics, as well as some other superpowers for players to use.

On top of that, they’ve also been rooting out problems with their regular updates. With the v14.30 patch on the horizon, the devs have also got a few fixes coming to all of their modes. 

Epic Games
Season 4 has been all about Marvel, but that will change in Season 5.

A handful of problems have been labeled as ‘Fixed in next Game Update’ on their public Trello board as of October 10, with a few annoying battle royale issues being addressed.

These include the issue with movement stopping when placing a marker, inventory shuffling after respawning in Team Rumble, and licensed audio playing on the Last Forever emote.

In addition to those, mobile players who had been frustrated by the XP bar not showing the correct level will have their issues fixed as well. 


Fortnite v14.30 bug fixes

  • Placing a map marker cancels movement 
  • Inventory shuffling after respawning in Team Rumble 
  • Audio of Last Forever emote playing even with licensed audio muted 
  • XP bar can be visually incorrect while in a match/incorrect leveling up on mobile. 

As for Save the World, there are two issues labeled as fixed in Future Game Update, including the wrong animation for the Sword of the Daywalker and Xbox homeshare players being unable to access STW.

However, as leaker iFireMonkey points out, these are not guaranteed to ship with the v14.30 update and could be coming later down the line. We’ll just have to wait and see.