Fortnite: Save the World

Fortnite: Save the World Dev Tracker




09 Jun

Commanders,

We're posting to let you know that we've just released a maintenance patch on PC. This patch addresses the issue negatively impacting Bows and the ...

Read more External link →

08 Jun

Comment

Originally posted by T_manYT

u/magyst it looks like a bigger bug than previously thought of

I guess something went wrong with charge weapons as a whole in this update

Yep, we're aware of that also. Been diving into this issue. Thank you!

Comment

PC players can try to swap to DX11 which might help out in the short term. We're gonna dive more into this and figure out what's causing this type of slow down.

Comment

Originally posted by T_manYT

Thank you, I can also vouch for that it is happening in creative (even though that isn't really your problem, I thought knowing that might be some help if it's the same issue causing it)

Yeah, for sure. Bugs having has much context when reported is great. Definitely makes things easier if we can determine if it's isolated to one game mode or spread.

Comment

Originally posted by bejoe905

u/Magyst

This is very much not a Premium Experience ™️

Thanks for the tag. Gonna have the QA team run some tests and see if we can take a look at what's happening here.

Comment

We're are of this bug, here's our trello card for tracking.

Comment

Originally posted by gabriel_GAGRA

This a super huge one, game is not identifying how far you push it and just returning to the standard value

Some guy said it’s also happening in creative, so maybe could be an engine bug? Just in case: u/magyst

It's a definitely interesting one.. Here's Trello for tracking. Definitely sorry about this one, I know how popular bows are. Pushing with the team to try and get some fixes.

Commanders!

Downtime for v17.00 has ended, and the next Season of Ventures is on the horizon.

Learn more about our return to the Blasted Badlands Venture Season — as well as what else v17.00 brings to Save the World — in our newest Homebase Status Report!

We’ll see you in the Badlands, Commanders.

External link →

Commanders,

We’re beginning to disable services in preparation for the v17.00 update. Players currently in a session can continue to play until downtime starts at approx. 2 AM ET (06:00 UTC).

We’ll post a new thread when downtime has ended and services are back up.

External link →

07 Jun

Hi hi /r/FORTnITE commanders!

Downtime for v17.00 begins at 2 AM ET (06:00 UTC). You can follow along with this process at @FortniteStatus.

With the launch of the new Season, please note that patch sizes will be larger than normal on all platforms.

External link →

02 Jun

Comment

Writing this up and shooting it over to the team. Thank you.


27 May

Comment

Definitely need to get DECOY's voice lines working again. 100%. This made the ability so unique. Apologies that it's been an issue for this long.

Comment

Interesting, I'll have the team take a look into this one.

Comment

Thanks for the heads up. Shooting this over to the QA team to investigate.


25 May

Commanders!

Downtime has ended for the v16.50 update.

Check out this week’s Homebase Status Report to find out about what’s coming this week (and next!) to Save the World.

Thank you.

External link →

Commanders,

We've begun to disable services in preparation for v16.50. If you’re currently in a session, you can continue to play until downtime starts at approx. 4 AM ET (08:00 UTC).

We’ll update you with a new thread when downtime has ended and services are back up.

External link →

24 May

Commanders,

The v16.50 update is scheduled for release on May 25, with downtime beginning at approx. 4 AM ET (08:00 UTC).

You can follow downtime along through our posts here or on @FortniteStatus on Twitter!

Be on the lookout for the Homebase Status Report after downtime.

Thank you

External link →

14 May

Comment

This was resolved late last night. We deployed some new servers to correct this issue.

Thank you for your patience!

Comment

Thanks for the heads up. The team is looking into this now. Definitely seeing some issues on our end as well.