Apex Legends Dev Tracker

crap. sorry. :( I only tested one match as I was focused on getting the actual fix implemented ASAP.

Have seen a bunch of posts about this, and since this reasoning behind this doesn't reveal any great secrets and I think players generally appreciate some insight into the process and since it's entirely my fault and therefore I won't seem to throwing anyone else under the bus...

Anyway, it's a bug related to the new Artifacts. Basically, unlike every other skin in the game, Artifacts aren't a single skin; they are three - blade, power source, and theme. Making that system work in parallel alongside regular heirlooms - which are a single skin - was a unique challenge. And in testing, there were quite a lot of bugs - most (probably all) of which came from the DEV environment being different. Trying to split the difference between testing the flow as players would experience and also not making every artist who wanted to make a change have to buy each component one-by-...

Queue times can be a factor, but bringing it back in this way also allows for monitoring and data collection on this new variant and Solos as a whole. Can't make any guarantees, but wanted to let you know that we see the comments and appreciate all of the feedback, and it does get shared with the team at large.

Have you gotten drops since cross prog? Also, want to drop me your tag? No guarantees, but trying to look into this.

As a temporary workaround until we can push a fix, if you do NOT go back into character customization for that specific character *after* equipping your Heirloom, it will stay equipped.

Basically:
- do whatever customization you want for a character
- equip your heirloom
- hit ESC (or back button on console) to return to the lobby character select menu
- hit ESC to return to the lobby and play your match as normal.

If you do go back into customization for that character, you will need to equip your heirloom again.

Now back to being waterboarded...

Known issue, fix in progress.

Known issue, fix in progress.

Known issue, fix in progress.

Working with Valve/Proton to get an update out for this.

Known issue, fix in progress.

Known issue, fix in progress.

Known issue, fix in progress.

Reset should be live now.

Hey there.

This was fixed, so if you login, you should your Ranked rewards appear, and your Rank reset.
Let us know if you still have issues.

~ Mack.

in this case, yes. But - per your bank example - your bank basically knows that (almost) every number they are every dealing with - at least every number that might need to be formatted - is a currency. So they can apply rules accordingly. Like, because it's currency, your bank is rarely going to - if ever - truncate a number for UI "neatness." Your bank is always going to favor absolute precision in every case. But we use the same rounding and truncation logic for basically everything. Damage, kills, games played, KDR, and currency. And yes, we could "always round down." But does that make as much sense for games played? Or damage? I am less sure. And yes, you can make it like an optional arg - round down/round up - but then you have to think through what's "best" in every case, and then make sure you have test cases for all those things, and ... Well, that's why I had found this be such a whack-a-mole type of debugging process to get right.

So, like officially, i have literal nightmares about situations like this. I wrote - or at least inherited and rewrote - most of the original number shortening and formatting logic in Apex. It's been mostly replaced by a new system now, but the guts are mostly the same, so I have great empathy both for my teammate who wrote this code and for you having experienced what I guess I'd call a "quirk" of the system.

And - having done number shortening and formatting on another game as well - I can say that is probably one of the most complex and most "GOTCHA!" prone systems you can imagine. Largely because there's way, way more subjectivity than there might seem. Truncating trailing zeros, for example. 1.20K makes sense. But 1.20 makes less sense. Sometimes you want to round up.

This was probably a case where round down was better, but like, let's say you were 1 CM short, would 1,199 really make sense to round to 1.19 rather 1.20? It makes sense but also doesn't. It's m...

Hi, all. Thanks for the continued DMs - even if you haven't had a direct reply, know that I've been compiling these. One last update from me on this: if you have not seen progress restored for your Breakout Challenges, please create a ticket so that the team can manually look into your account.

Flagged with team. Will add to Trello if/when we can.

Cheers for the usernames, all. If you're still missing Breakout Challenge progress after our latest update and have not yet sent me your gamertag, please do. (here or chat)

If you're missing progress other than the Breakout Challenge, that is separate. Please create/add to a thread with EA so that your account can be looked into.

Pubs should be back up, let us know if you're seeing otherwise. May need to restart the game.

If you're still seeing your account reset after updates over the last few weeks, please create a post with EA so that they can look into your account manually.