Dev Tracker

Originally posted by theguhnslinger

Even if you got snowflake tickets after the llama disappeared? Like after 7 est, reset time

Yep :)

Originally posted by TheRealSenoirNoNo

Any chance you can help with a support ticket gone unanswered?

Toss me a direct message with your ticket ID number and I'll do everything I can to help you out. :)

If you had snowflake tickets prior to downtime, then fear not. Unspent tickets will be redeemed automatically into Holiday Survival Llamas. Here is a direct quote from the patch notes:

"For every 1,000 unspent Snowflake tickets, a Holiday Survival Llama will automatically be granted and can be found in the Loot Tab. All remaining tickets will be lost."

Hope this clears up any confusion. :)

Originally posted by Desintegr

Hi. The game does not support vertical sound yet. It's a top 1 priority feature the audio team wants to implement for the game.

From a previous Epic comment : It's one of audio's top priorities now with the release of the new map update. We're testing some stuff internally right now (it's sounding good!) and gauging when we can get it into an update. Because this new map has so many different indoor/outdoor layouts (not to mention building) a "one size fits all" approach just isn't going to cut it without some clever tricks.

Because footsteps are such an crucial part of the game we want to make sure we're doing it right and not rushing anything out. :)

I love that we have a community where people care enough to pass this along. Was about to reply. :) Thanks!

Originally posted by gt2x

https://imgur.com/a/Lon2J (ping from each server)

thank you!

Perfect, thank you. Will share updates here as they are available.

Quick question, I should have asked before. Are you experiencing variable/sporadic latency, rubberbanding, or anything along those lines? Or is the change in experience limited to the major change in latency?

Basically, trying to understand if your experience is "much higher latency, but stable/consistent" or if you also have degraded experience in terms of stability of your connectivity. Understanding personal anecdotes like this really helps contextualize the data on our end.

Originally posted by Fixer_

issues unrelated with the quality of the backup

Did someone let the chimp into the server room again?

But it's a cute chimp!

Originally posted by DarienPrague

Can you please put time stamps on future update edits?

Great idea. Sorry about that! Going back and editing.

Originally posted by SlightlySnaked

Dang, I could only imagine the pressure from 1,000's of people just waiting to play. Good luck guys.

<3

Originally posted by ExampleV2

Thanks for the update, sucks for us waiting but shit happens. goodluck with the next restore, fingers crossed.

Thank you, it's tough. People want to play.

Originally posted by Details-Examples

Since /u/MrPopoTFS has advised that "Known Issues" will be listed in the patch notes going forward (and this isn't documented and has been an issue since launch, then the issue made worse since patch V.1.9) I'm listing it here.


For Reference (the subject matter)

Corrosion (Tactical Squad Bonus)

  • Critical hits from melee weapons deal 15% of hit damage every second for 3 seconds while reducing movement speed by 30%. Applies to all classes. Tactical bonuses are applied to your Primary Hero when this Hero is in your Tactical slot.

 

Corrosive Blade (Ninja: level 30 ability)

  • Critical hits from the Ninja's edged weapons deal 30% of hit damage over time while reducing movement speed of target by 30%. If you also have Smoke Assassin, Corrosive Blade will take precedence when it can. The damage of Smoke Assassin and Corrosive Blade will not combine.

 

Important

  • Corrosion (which is the tactical bonus) will work with all melee weapons. This includes blunt and penetrating weapon types (so if you run around on a Tank Penny, like clubbing things with your hammer and want a little bit of extra damage, this will work for you).

  • If you are a Ninja with Corrosive Blade and you crit a target with a non-edged weapon it will apply Corrosion. If you then weapon-swap to an edged weapon and crit the target it will 'override' the Corrosion with Corrosive Blade (why you would be using a non-edged weapon, or have a Deadly Blade slotted into the tactical slot if you were a Ninja with Corrosive Blade already is besides the point)


The Issue

  • The abilities do not deal (15%/30%) of the (critical) hit damage when a critical hit is applied

  • Damage is capped at 10,000 damage against normal husks (and has been this way since launch)

  • Damage is capped at 5,000 damage against 'elemental: fire, water, nature' type husks (became this way from patch V.1.9)

 

Explaining the Abilities

  • The abilities only occur on critical hits, therefore all (applicable) hits are critical hits.

  • The abilities apply a % of the critical hit damage as bonus damage (15% and 30% for the respective ability)

  • The bonus damage is to be applied each second for 3 seconds.

 

The concept: How it should work

  • If I land a critical hit on my target for 100,000 damage, then my 'hit' value is 100,000

  • 15% (using Corrosion) of 100,000 damage is 15,000 damage

  • Each second for 3 seconds suggests 15,000 damage should be applied 3 times (or 4 times, if you assume it applies at time = 0, 1, 2, 3)

  • The total bonus damage should be 45,000 damage, or 60,000 damage.

 

The Reality: The values obtained in-game

Stats and Heroes used for these Videos

 

Video 1 (Physical Husk)

  • 68,368: Cresent Kick (also stuns Blaster, applies a 40% vulnerability)

  • 33,570: Melee (light attack), does not crit

  • 112,428: Melee (light attack), critical hit

  • 14,000: Corrosion, benefitting from Cresent Kick (10,000 * 1.4)

  • 14,000: Corrosion, benefitting from Cresent Kick (10,000 * 1.4)

  • 10,000: Corrosion

  • 10,000: Corrosion

 

Video 2 (Element: Nature, Husky Husk)

  • 75,297: Melee (light attack), critical hit

  • 5000: Corrosion

  • 5000: Corrosion

  • 5000: Corrosion

  • 10,000: Corrosion (unable to explain this damage value unless Corrosion can critical hit, or ability triggered without applying damage reduction due to elemental typing)

Discussion of Results vs Hypothetical

What we saw

 

Video 1

  • Corrosion damage is considered to be a 'physical' damage source: it will benefit from vulnerabilities (like debilitating shots)

  • The base corrosion damage is ticking for 10,000 damage and it occurs 4 times (at time = 0, 1, 2, 3)

 

Video 2

  • Corrosion is ticking for 5,000 damage (which is in line with a 50% physical damage reduction vs element)

  • Corrosion can apparently 'critical hit' for a bonus 100% damage (or the element damage reduction was not applied)

 

What the values should have been

 

Video 1

  • Damage of the critical hit was 112,428 damage

  • 15% of 112,428 is 16,864.2 (rounding down, the base value of each corrosion tick should be 16,864 damage)

 

Video 2

  • Damage of the critical hit was 75,297 damage

  • 15% of 75,297 is 11,294.55 (rounding down, the base value of each corrosion tick should be 11,294 damage)

  • Physical attacks vs element are reduced by 50% (property of the husk). Before patch V.1.9, this did not apply to Corrosion/Corrosive Blade

  • Applying a physical reduction, the base value (rounded down) for each corrosion tick should be 5,647 damage


Heroes affected by this issue

  • All Heroes who equip a Deadly Blade for the Tactical Slot Bonus

  • Variants of the Assassin, Deadly Blade and Alchemist Heroes (for which Corrosive Blade is supposed to be a powerful level 30 ability, just like "Keep Out!!!" is for Master Grenadier and Urban Assault Soldiers)

 

Is the damage loss really that significant?

  • For the Ninjas with Corrosive Blade the bonus damage is supposed to be 30% of their critical hit damage per second.

  • A 100,000 damage critical hit should produce a 30,000 bonus damage tick per second (literally 30,000 dps)

  • The current maximum Corrosive Blade bonus damage 'tick' is 10,000 (minimum loss of 20,000 dps)

  • 10,000 * 4 = 40,000, 30,000 * 4 = 120,000, that's a difference of 80,000 additional damage.

 

In more simplistic terms

  • The value of Corrosive Blade is (supposed) to be worth 120% of the damage of a Critical Hit

  • If I critical hit for 100,000 damage, Corrosive Blade should deal a total of 120,000 damage (against non-element targets)

  • As a % of a husks health pool, as long as 1 critical hit sword swing would deal approximately 46% of a husks total health pool, the husk will die after 3 seconds with no further attacks required from the Ninja (100,000/220,000 is approx 45.45%)


Desired Outcome

Either of these would be acceptable, it should be obvious which would be preferable but the main point is to have player expectations match the descriptions provided to them by the game environment (i.e. descriptions from the UI)

  • 1. Fix the damage calculations (modify the code) so Corrosion/Corrosive Blade actually provide the 15%/30% damage as suggested by their tooltips
  • 2. Change the tooltips to document that damage values are capped at certain values (15%/30% of a critical hit, or 10,000/5,000 damage, whichever is smaller).

Looking into this now so we can add to known issues, in a more condensed fashion. :)

However, I do want to say solid job on providing all this information for us to review!

Originally posted by iFlak

Downtime has started for Patch V.2.3.0. What’s new? See for yourself in this weeks patch notes! https://www.epicgames.com/fortnite/en-US/news/v-2-3-0-patch-notes

Update: Downtime is going longer than expected. We will update players as soon as we have more information.

UPDATE: All, we're making changes to the backend systems to handle growth and it has extended the downtime beyond what we expected. More updates as we have them.

UPDATE: Hi all, it is looking like we are going to be down for at least a few more hours as we scale our backend systems. We're very sorry and we're working on it.

UPDATE: Sorry everyone, it's looking like the Fortnite servers will be down for at least a few more hours. More updates will follow.

UPDATE 11:15 AM EASTERN: "During our downtime to upgrade to 2.3, we were performing recommended tasks to resolve a lingering database issue. Those tasks ended up causing the database to go into a bad state. After significant consideration, we decided our best option was to restore from a backup at the moment we took the servers down for the patch. Our first restore failed (due to issues unrelated with the quality of the backup) and we're working on a second attempt at the restore. We're on it and it will be up as soon as humanly possible."

Update from the team working on the servers.

"During our downtime to upgrade to 2.3, we were performing recommended tasks to resolve a lingering database issue. Those tasks ended up causing the database to go into a bad state. After significant consideration, we decided our best option was to restore from a backup at the moment we took the servers down for the patch. Our first restore failed (due to issues unrelated with the quality of the backup) and we're working on a second attempt at the restore. We're on it and it will be up as soon as humanly possible."

Originally posted by iFlak

Downtime has started for Patch V.2.3.0. What’s new? See for yourself in this weeks patch notes! https://www.epicgames.com/fortnite/en-US/news/v-2-3-0-patch-notes

Update: Downtime is going longer than expected. We will update players as soon as we have more information.

UPDATE: Hey all, We're making some changes to the backend systems to handle growth and it has extended the downtime. More updates as we have them.

UPDATE: Hi all, it is looking like we are going to be down for at least a few more hours as we scale our backend systems. We're very sorry and we're working on it.

UPDATE: Sorry everyone, it's looking like the Fortnite servers will be down for at least a few more hours. More updates will follow.

UPDATE 11:15 AM EASTERN: Update from the team working on the servers.

"During our downtime to upgrade to 2.3, we were performing recommended tasks to resolve a lingering database issue. Those tasks ended up causing the database to go into a bad state. After significant consideration, we decided our best option was to restore from a backup at the moment we took the servers down for the patch. Our first restore failed (due to issues unrelated with the quality of the backup) and we're working on a second attempt at the restore. We're on it and it will be up as soon as humanly possible."

Update from the team working on the servers.

"During our downtime to upgrade to 2.3, we were performing recommended tasks to resolve a lingering database issue. Those tasks ended up causing the database to go into a bad state. After significant consideration, we decided our best option was to restore from a backup at the moment we took the servers down for the patch. Our first restore failed (due to issues unrelated with the quality of the backup) and we're working on a second attempt at the restore. We're on it and it will be up as soon as humanly possible."

Fortnite @fortnitegame
Here is a brief explanation of our extended downtime. We're working to get you back in the game.… https://t.co/9Bfuo9qNB1
Originally posted by arbyandthebeef

I mean it would be cool, if they actually said something helpful other than “the servers are down, no ETA”. If they aren’t giving any actual update, it sort of defeats the purpose of employing customer reps to be active on messageboards and such...

Also, not sure if you saw this: Hey all, We're making some changes to the backend systems to handle growth and it has extended the downtime. More updates as we have them.

Originally posted by MoonLiteNite

ETA on the downtime?

It is looking like it's going to take a while

Originally posted by arbyandthebeef

I mean it would be cool, if they actually said something helpful other than “the servers are down, no ETA”. If they aren’t giving any actual update, it sort of defeats the purpose of employing customer reps to be active on messageboards and such...

We don't really know anything other than it is taking longer than expected. I'd ask one of the backend people to post, but they are working to get everything back online.

Originally posted by Evernaila

Yea! Same! XD

The patchn notes are great (for once) in that they look as if they have tried to fix actual problems this time.

But until I playtest it, I am cautiosly optimistic about the state of the game! XD

We'll keep working at it.

Originally posted by HughPackage

You said a few more hours over an hour ago so now the "few more hours" started again =/

Yes :( I don't have an ETA, it is taking a lot longer than expected.

Originally posted by brankoz11

And to the people who downvoted this epic have just said there is no timeframe more or less like what I said.

We're not sure at this point. Likely a few more hours.

Originally posted by Seditian

Out of curiosity, what kind of backend changes? Something we might notice or just laying some groundwork/improving server stability?

Expanding for increased player numbers.

Originally posted by McCarryLadd

Just back from a half day, is it still down?

No update, it is still looking like a few hours.

Originally posted by mephisto1990

Sorry about being picky, but i purchased the battle pass a week ago only after i had calculated that i will reach exactly level 70 on the last day if i do every daily quest and buy 10 lvls in the store (which i already did). It's 4 pm where i live now and i have been waiting to play since 1 pm and won't be able to play after 5pm. Will there be any compensation for battle pass owners? ( Like 150 Vbucks or one additional battle pass quest tomorrow?)

Thx for the updates btw

It's fine. :) If you feel you should have a refund, please use this form to request it.

http://fortnitehelp.epicgames.com/customer/en/portal/articles/2313879-how-do-i-request-a-refund-?b_id=9729

Originally posted by Hregrin

It means working on the servers to allow more people in at the same time, the way I read it.

This is correct

Originally posted by teriety

You guys are doing great, thank you :)

<3

Originally posted by powdashrooms

Why is there never an ETA? NotLikeThis

:(