RobotHavGunz

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...

Just ammo on the ground? Or perhaps you'd also like to know the amount of ammo in a deathbox or blackmarket as well? ;)

On a personal level, I agree with this. Tracking this does become a much more complex task, though; doable, just a bigger problem to solve. I can raise this internally. An issue like this I'm definitely not "the decider," but I can raise with the team.

That's already the case. You will NOT be penalized if you're short-squaded. Likewise, if someone else leaves your party first, they will be penalized, but if you then do not want to stay, and you leave, you will NOT be penalized.

Thanks. It's a very good list. And valid, relatable reasons for all of them. Not sure I agree on all of them, but in those cases it's just personal opinion.

Generally speaking, the "add option" is a tricky one. Option menus can easily become way overloaded and useless. Like, most people never touch their settings, and that gets worse (in general) as you add more options. Plus the more "options" you have, the more that you have to track and the more potential there are for bugs. So I definitely understand wanting options, but options are a delicate subject.

Some of the more general topics around "favoriting" is an ongoing topic. We've introduced more features around teammate status, and I think that's definitely an area to explore further. You'll note, for example, when a teammate pings ammo, we now tell you how much they have.

Regardless, appreciate the feedback and there's some good stuff in here to think on further.

Only for modes with the leaver penalty - Ranked, Arenas (both Ranked & Regular Arenas). This is NOT adding a penalty for leaving in BR pubs.

Thank you! It always makes me so happy and proud when someone is hyped for my contribution. Even if I did have to scroll an awfully long way to find it, I am honored to have delivered something that you would "YESSSSSSSS" to!

Take this Nessy (aka Snek) as gratitude.

I've got a 50% scale version with the Dragon Chaser skin on order! Can't wait to decorate my office with it.

Any interest in doing one on commission?

I actually have no idea what this would take. I've not heard anything about this internally, but it may have been tackled and put to rest before I started - I've been on the team about a year. I don't think there's a big demand here, so maybe it's just a case of being super niche. I do know that it doesn't "just work" but I have no idea how hard it would be.

So knowing that "it's complicated" responses are generally sh*tty, I'll nevertheless respond with, "it's complicated." Fundamentally, there's a very different core UX expectation with a controller. First off, you're limited to 16 buttons. And the core expectation around how those buttons work is quite different from MKB. With a mouse, there's an expectation that "clicking on a thing" will do something. Controller logic in this regard is quite different; we try to avoid having players hover-over-a-thing-and-press-a-button. Now, sometimes, that's unavoidable (e.g. deathbox looting), but it's generally not great. In most places, we try to make it so that you see that a button - e.g. X - is bound to some action, and when you press X - anywhere - something happens. Now, this leads to some weird behaviors too because of core aspects of our UI framework (and trying to support both controller and MKB simultaneously and fairly seamlessly) where hovering over a "bu...

Not my area of the game, but I agree with this and have flagged it internally to try to get some eyes on it from the Legends team. The limitations around controller buttons is definitely frustrating, and there's never a perfect way to map 16 buttons (IIRC) to the nearly infinite options offered by MKB. We try not to have options for everything, because that introduces UX issues of its own, but in some cases where it's clearly interfering with utility, I think it's warranted. I'm a console player myself, and I can say we're definitely aware of many of the common controller buttons frustrations ("I wanted to res my teammate, but instead I opened the door." and "I wanted to reload but instead I went to res my teammate" etc) and it's a constant debate between interfering with learned behavior and working to tune usability.

Core interactions in terms of controller functionality are not something we take lightly, so we tread very, very carefully, since a lot of...