Fortnite: Battle Royale

Fortnite: Battle Royale Dev Tracker




19 Oct


Fortnite Fans,

Another big Fortnite event is on the horizon –  tell your friends using #FortniteTwitchcon!

Where are we dropping?

San Jose Convention Center! We’ll be landing at Twitchton 2018 on Friday, October 26 and we’re bringing plenty of fun activities for solos or squads. Find us inside the San Jose McEnery Convention Center in the “Fortnite Hall” or tune-in to the conclusion of the Fall Skirmish tournament series, ...

Read more
Comment

Hi all,

We are aware of an issue that occurred early Season 6 where purchases returned an error on PS4. These orders were fulfilled later in the day, leading to some multiple charges. We are currently investigating these cases.

Post

For a short period immediately following Season 6 launch, our PS4 purchasing system returned errors for some players. All purchases including those with errors were fulfilled after the issue was resolved. We are investigating cases where players unintentionally made multiple purchases during this period.

External link →

18 Oct

Post

Due to the influx of players trying to compete in our Alpha Tournament, we encountered a shortage of Battle Buses! Our teams are aware of this issue and we are monitoring the situation closely.

External link →

17 Oct

Post

The Battle Bus is test driving an engine upgrade and now travels 25% faster while flying.

Remember, always buckle up and thank your driver!

External link →
Post

The Battle Bus is test driving an engine upgrade and now travels 25% faster while flying.

Remember, always buckle up and thank your driver!

External link →
Comment

Thanks everyone for helping us crank on this new system! Lots of info for us to look through from today and we're actively tackling a number of these issues stated here.


16 Oct

We're investigating issues with matchmaking in our Alpha Tournament that's impacting our EU regions. We'll update when we have more info.

EDIT: We're aware of an issue with tournament points not being updated correctly. We're investigating the issue and will update when we know more.

External link →