DanDaDaDanDan

Looking into it.

The addition of the flare gun to Arenas was a mistake that is being corrected.

Here is some technical background information:

We upgraded to the Android SDK 29 with v16.20 to address some bugs and also the OS prompting that the app was out of date.

On Samsung Phones we need access to the “GET_ACCOUNTS” permission to verify purchases on the Galaxy Store. This is a permission we have always asked for on all devices at install time. With v16.20 and the new Android SDK however we only need to ask on Samsung phones using runtime permissions.

The Android SDK as of version 23 lumps “GET_ACCOUNTS” into the permission group of “contacts” so us asking for the “GET_ACCOUNTS” permissions results in the player now facing a prompt for “contacts”.

Fortnite is NOT asking the OS for access to your contacts. You can verify this yourself by checking the APK manifest with tools such as ...

It’s a shame they break :-/ Feel free to drop me an email and I’ll escalate and dig into process more to see what can be done to reduce cosmetics breaking.

Daniel dot Vogel at epicgames dot com

Please drop me an email at Daniel dot Vogel at epicgames dot com if you have a frustrating experience with Epic / player support. That goes for anyone :-)

(Please do not DM me on Reddit as I don’t check them)

It is compiling shaders and should get much faster in chapter 2 season 2.

Let me ping our art producer

Thanks - escalating

The fix requires a client update and we already have 10.31 in flight.

Fixed in v10.31 next week.

We are aware. Fix should be in 10.31. An attempt to hotfix off new audio mixer failed as it resulted in crashes :-/

I want to say this is fixed in v10.30 but let me check.

https://trello.com/c/1JgV6NQ9

We wanted to drop in and provide some context for the changes to the Turbo Build timer.

What Changed in v10.20?

We returned the time between subsequent Turbo Build placements from 0.05 seconds to 0.15 seconds in v10.20. This was the value used up to v4.30.

Why Change Turbo Build?

We did so as a first step addressing several problems:

• Rapid Turbo Building favors players with low ping in disproportionate ways.
  • Taking walls (racing with another player to place a wall before them)
  • Turtling (continually rebuilding a wall that is taking damage)
• Turtling disproportionately favors defender
  • E.g. holding mouse button vs. squad shooting at 1x1
• Building piece placement accuracy
  • Easy to accidentally place multiple pieces “at once”
• Spam building
  • Easy to spam build
  • We want building to be a bit more ...

We wanted to drop in and provide some context for the changes to the Turbo Build timer.

What Changed in v10.20?

We returned the time between subsequent Turbo Build placements from 0.05 seconds to 0.15 seconds in v10.20. This was the value used up to v4.30.

Why Change Turbo Build?

We did so as a first step addressing several problems:

• Rapid Turbo Building favors players with low ping in disproportionate ways.
  • Taking walls (racing with another player to place a wall before them)
  • Turtling (continually rebuilding a wall that is taking damage)
• Turtling disproportionately favors defender
  • E.g. holding mouse button vs. squad shooting at 1x1
• Building piece placement accuracy
  • Easy to accidentally place multiple pieces “at once”
• Spam building
  • Easy to spam build
  • We want building to be a bit more ...

Thanks - we are working on getting this fixed.

Can you send me a DM with your display name and more context on issue - I’d like to understand it so we can address it.

Thanks. Looking into it.

With 8BitMemes help (thank you!) we were able to locate all of the solo matches they played in 10.00.

We took all of the players that loaded into any of those games, and found their cause of elimination.

We were able to confirm that every player had a valid elimination cause and we weren’t missing any players’ data.

We categorized the distinct elimination causes into the larger buckets that 8BitMemes used (ie Shotgun, SMG, etc).

For the B.R.U.T.E. the possible elimination causes that show in the elimination feed are: * B.R.U.T.E. Missiles * B.R.U.T.E. Shotgun * Stomp/Jump * Self-Destruction

We compared those results to our total population and found that they match our previously reported numbers.

In 8BitMemes summary both B.R.U.T.E. and pickaxe eliminations are too high and shotgun eliminations are too low relative to what we are seeing for their matches.

We verified that the B.R.U.T.E.’ shotgun is attributed to the B.R....

There was a code change that broke an entire class of them - looking into why that was not caught before ship.

I make no such assumption - I seek to understand the discrepancy, and if our data collection mechanism matches up with submitter, how that fits in the broader data set. And if it doesn’t match up, figure out why not :-)

Or in other words, I want to rule out issues with our data collection (we triple checked already, but this is another opportunity to do so) etc.

Some subreddits shadow ban posts hat contain email addresses re: why written out.