RobotHavGunz

Should self-correct next time you hit the lobby. If your client is having connectivity issues with Marketplace, it may take a bit of time as it needs to connect to a separate service (unrelated to gameplay). But as soon as that happens, it should self correct. No one was getting rewards, and everyone I've spoken to since has gotten them (and the root cause was clear). Marketplace sees a big spike in traffic on patch days, which might be why it's delayed. Message me directly if it doesn't correct within the next day or so.

when you give a mouse a kill leader

this is gold. take my nessie (snek) award in honor of this brilliance.

Was a bug. Fixed.

Fixed.

Storm Point is really fun, there’s a lot of verticality which made for awesome plays

From my July 30th internal playtest notes:

Vertical movement.This map seems like the "tallest" of any map. Characters with a lot of vertical mobility - horizon, valk, revenant - all seem like they are super well suited to this map. I played Valk mostly, but also horizon one game, and appreciated the mobility even more than on other maps.

I love Ash, but as with Revenant, I am somewhat intimidated to play her. I am not very good so I always feel like I'm letting her down. Like, who is this pitiful human attempting to play as me... The anxiety is real.

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.

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.

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.

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.

Really, really, really awful; though it feels a bit less bad because I was doing a refactor to try and fix one of longest running issues. Ideally, after we patch, both this bug AND that bug will both be history.

To give some more detail on this. There is a bug - *my* bug - on the gladiator card presentation screen. It will be fixed in the upcoming patch; it was already fixed before I saw this post, but I wanted both to comment and also ask for feedback on whether or not this fixes things. From reports internally, it doesn't *seem* to matter if OTHER people have the animated banner pose; only if you do; we had a group of other devs playing where 2 of 3 had animated poses - and both froze - but third with a rare pose did not; but that might just be luck. This makes me think it's not. But I'd love to get more feedback on if that's the case. Even if non-Epic poses trigger this, it seems to be much, much less often.

There's no obvious reason - looking at the code - why epic (animated) banner poses should trigger this more often - I never saw this bug in testing, nor did QA, but I know the bug is happening. And I can definitely believe this post - that ...

I didn't do the original deathbox. But I did do a bunch of reworking of it to simplify it - there were some pretty substantial under-the-hood changes to deathbox menus between some of the early seasons, so I did a bunch of work to simplify and unify all of that in S9. In the process, I managed to break looting for a surprisingly big group of players. We tested this a TON, but people who bound "alt-use" to A-Button (on XBox; i forget the equivalent on PS... Square?) and then had "activate" (normally "A") as D-pad right couldn't loot. Who knew that people ever setup their controllers in this way... But they do. I ended up needing to override that particular mapping - A will always activate in a deathbox, which is a big part of what gave me perspective on the challenges with controller button mappings and how it's a huge can of worms that is not to be opened lightly. I can say that the overall deathbox system is one of the more complex systems within the game (at least that I've touch...

I'll put a bug in for this. This SHOULD not happen.

So this has been asked a couple times. It's a mix of technical and UX decisions. Essentially, the system has to be 100% automated; it's not something like content moderation where having some human oversight is practical or reasonable. And, really, it ought to be simple. Because the more complex it gets, the more likely that something goes wrong. That's why even though I like the idea of something like penalties for frequent leavers, it's also potentially worrisome to add even more complexity into a system. So basically, the system - as it exists - penalizes you if you leave. It doesn't care WHY you left. And that's because 1) it's quite hard (impossible) to truly know why and 2) because if it tried to care why, people would exploit it. So basically, if you leave - whether by accident or because your power went out or your internet went down (has happened to me, and I was penalized for it, as I should have been) - you will get a penalty. Because the impact on your squad is...