Apex Legends Dev Tracker

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

That's soooo cool. I would wear that everywhere! The people on the bus would be mad :)

Thanks. Forwarding this on.

Hate to break it to you, that's a bug sitting in the backlog for a few months...

Ah yes. This is how I found out about the harvester beam too. It was a ranked game too.

So I'm gonna sign off, but I did want to say thanks to everyone who responded. It's a pretty amazing community here, but also one that's a bit intimidating. And also a bit like drinking from a firehose, so I apologize for people who asked questions that I didn't respond to. I read all the replies, and I'm sorry I couldn't answer all of them. There were also some pretty great suggestions about things that I had not thought to test that I will try before S11.

Prior to becoming a game dev I worked in a field where "effort" didn't matter much. It was purely about results. So I can appreciate that saying, "I tried to fix this but couldn't..." doesn't necessarily mean much. But when I see bugs like this one - or more major ones like someone missing a 20 Bomb or 4K badge - in areas of the game that I am one of the main devs for, it bothers me a lot. I play this game a lot (I'm still pretty bad though), and it bothers me as a player. I care deeply about the areas of the g...

Gross

Firing range bug was a separate one. And it was unique to Valk. Basically, if you triggered Valk's ultimate, we assumed it counted as a "landing" - same as if you jumped out of a plane. And so once you jumped, it was like being in a match.