Apex Legends Dev Tracker

Updates happen all the time—I feel like you're asking about server hardware, though, which most of our issues particularly recently have been software related. I'm not the best person to explain it like an expert but the big awful wave of issues with the 10.1 patch in particular was a series of unforeseen problems caused by the patch itself. Live service can be hard. Only thing you can do is learn from experience and look for ways to make it better going forward.

No bad vibes intended, I love the game too, man. May we both continue trucking successfully, godspeed

The server issues we've had have been a source of a lot real pain for players and for us—sometimes cracking a joke is a way to deal with the pain. All love for you guys. Hopefully some of you saw the intended self-deprecating humor in that post.

High five! :)

I vote for A Pathfinder swimsuit skin

Can’t believe I haven’t seen/thought of that before. That’s awesome

You're welcome. And, uh, "no comment..." or something.

All I will say is that the reason we had to start despawning you in the firing range was absolutely not related to issues with 3P. It had to do with issues around changing characters while still alive and, in some cases, bad things happening as a result. The fact that it broke the 3P easter egg was absolutely not intentional. Even if - hypothetically - the 3P easter egg were fixed, you'd still die when changing characters.

For the Loba bundle, that is by design. That bundle is only meant to require that you do not own either the R-301 skin or the Loba skin. I am definitely not the "decider" of such things; only one of several people who can - from a technical capability standpoint - make certain changes / fix things / etc. I can/will make sure feedback is received by the team that does make these decisions.

In the case of the Octane bundle, we did not mean for owning Octane (the character) to prevent purchasing the bundle; in the case of the Loba bundle, the exclusivity was intentional. That was the point of my edit in my OP:

EDIT: there will still be some of these types of bundles where a "core" item may be something you already own and which will disqualify you from a bundle you'd like. We are watching that feedback and are trying our best to balance how we structure these things.

Can you have a "bug" with an "easter egg"? I wonder... But, as to your question, seems like the whole point of easter eggs is to let players find things out for themselves. And that's all I'm gonna say about that. Though you might want to wait a bit (possibly until S11 launch) before testing to see if anything has changed.

This was literally a 5min fix. And it was obvious what needed to be done. Store-only fixes usually don't require a client or server update because it's just a web API. They are something we can fix on the fly, unlike most issues. This is a rare case where I can literally "push a button and fix the thing." It has nothing to do with "priorities." I wish more things were so simple and easy to change.

Fixed at about 10am this morning, as soon as we saw this. Basically, there's a functional (internal) difference between old bundles (the ones where you get a discount if you own certain items) and these "bonus" bundles, which are new, and where ownership of any of the "core" items results in a lockout. It was never our intention to lock people out in this way; just a mistake in the way we configured it as it's pretty new for the team.

EDIT: there will still be some of these types of bundles where a "core" item may be something you already own and which will disqualify you from a bundle you'd like. We are watching that feedback and are trying our best to balance how we structure these things.

Thank you for posting.

Sorry you had to experience this. I will forward this to our TOS team.

This is a potentially touchy topic, so let me try to put the appropriate caveats around this being only my opinion, etc. I love the idea. BUT I also see the impracticality of it. The term "developer" is pretty random, in a lot of ways. It doesn't really say much. But it's a fine label in so far as it goes. When you think about the team that makes Apex happen, it's a huge team. But when you think about the team that does the work outlined by something like an "Operation Health," it is a much smaller group.

I love this idea because this type of work is 1) actually a significant portion of my actual job description and 2) is also work that I very much enjoy. The big issue is not really with #2, though that does matter. But it is with #1. On both the technical and non-technical side of things, there are plenty of people who would sit idle during a period where the ONLY work that was done was, essentially, "bug fixes."

Live Operation development bears a fair amount of r...

I don't remember the underlying cause there, but I do remember that issue was with THOSE SPECIFIC frames. This bug is more general. It's not even obviously related to Epic (animated) banner frames, but it does seem that those trigger it more often, for reasons that - theoretically - make sense to me.

Skepticism is a good thing, especially when it involves potential personally identifiable information.

I work on the Apex Legends team, yes.

That's not my area at all. Probably one of the areas I know the least about, but I do know that work around super high-frame rates and the cap we have is something that's actively being worked on. You can follow one of our lead engineers Samy Duc - https://twitter.com/ricklesauceur - for actual useful info in this area.

I'm just a lowly XBox One player, happy with my 60FPS.

What is the attachment? Is there a case number? You can DM me if you want, would like to find out what happened and why our TOS team took no action.

Replaced a map with a reference to the desired information on the actual asset. The map would get corrupted in certain cases, so should be more reliable. But the details of the safeguard on checking for that info needed to be modified as a result of my change, which is what I missed and what - in some cases - causes this bug.

Not really sure about a "bug list." Mostly because it's not really sustainable to offer that. I'd say this sub is about as close as there is to a public bug list. We spend a LOT of time reading this. If there's one or two that you think are serious and which you think we're not aware of, you can message them to me, but no promises.