Fortnite: Battle Royale

Fortnite: Battle Royale Dev Tracker




11 Oct

Comment

Couple questions: What device are you playing on, what OS version is this device, and what were you doing in match before this prompt occurred?

Post

We're investigating reports of the Out of Time OT challenges not granting the red style variants for the Cosmic Cleavers pickaxe and Pixel Pilot glider when the Eternal Voyager style is unlocked.

You can track this issue on our Trello page here.

External link →
Comment

Originally posted by A35K

Yes, I was even trying to restart my phone but nothing worked.

Can you try pairing a controller to your device and seeing if that will get you past this screen?

Comment

Originally posted by A35K

Yes, I was even trying to restart my phone but nothing worked.

I am going to send this over to the QA team to investigate.

Comment

Does this occur to you every time you launch the game and hit this screen?


10 Oct

Comment

Originally posted by milanhin

I hear what you're saying. But since it still is a bug that has to je fixed after the other ones, I just posted it

The issue is i am not seeing a bug here? Everything when slowed down frame by frame seems like it is working correctly. You can see your edit, press the floor and build buttons almost at the same time, this action of pressing it so quickly while jumping ( and seemingly not gaining enough height) doesnt place the floor.

Once you land you are turning the camera left and right but never pressing the placement button. Once you do it builds. It was a short video and I looked at the video in as slow motion as I could, that is what i noticed.

Comment

I tried to break this video down frame by frame to see the issue. It looks as if you edit and pressed the floor piece while jumping. When jumping it does not look like you are reaching the height to were you could jump and place that floor. Holding down the build button when you cant build will result in showing the button pressed but no actions.

As you showed in the video once you tried again you were able to build, you also made the jump and just turned the camera without pressing the build button, once you pressed the button it worked correctly.

Comment

The reason it was removed is that we don't have an ETA atm for this to change. Right now this is a design choice and not considered a bug, so it was removed.

Comment

Thanks for the report! We’re working on a fix to grant the harvesting tool and glider variant to everyone who unlocked the red outfit style.

Comment

Hey, if you do not mind me asking who provides your internet and what region are you currently in, NAE, NAW, EU?

Comment

Wow! This is incredible!

It's cool seeing so many characters together in one scene.


09 Oct

Comment

Originally posted by StaySticky_01

I have Experienced this bug

on Google Pixel 2 Android 10 on Wifi Signed with Google

AJM12354

Are you still having this issue or has the issue been fixed? If you do not mind me asking who provides your internet and what region are you currently in, NAE, NAW, EU?

Comment

Thanks for the report. If this does happen again, could you also make sure to report it in game under feedback so our team can look at your logs.

Comment

Hello, do you mind sending in feedback within the game with the title "Packet Loss" so that our QA team is able to look into this issue. Also, what is the in-game username you use?

Comment

Hello, do you mind sending in feedback within the game with the title "Packet Loss" so that our QA team is able to look into this issue. Also, what is the in-game username you use?


08 Oct

Comment

The Squads playlist for NAE and OCE regions has been temporarily disabled while we perform a brief maintenance. We'll provide an update here when it is re-enabled.

Comment

Originally posted by gacko101

I had the bug when you get on a hoverboard it sends you flying. It sent me flying into the storm where I died. Reststarting the app fixed it.

Thanks for letting me know. I will send this over to the QA team to investigate.

Comment

How did you lose in the match? Did this problem fix itself if you restarted the game?