Originally posted by Aetherimp
Thanks again for the reply. I know it's not your job to assemble the actual patches, but it would be great if the people who DID do that would hear the community outcry on issues like this.
I don't expect you guys to fix things over-night nor am I demanding "MORE CONTENT" or "FIX EVERYTHING NOW"... Just would be nice if some key issues were actually fixed, and furthermore, pushed to the patch when they are fixed!
Is there any reason why they may have held this feature back in the last 3 patches? Maybe it caused other issues?
Oh, they definitely know and they're all working their butts off to make it better. Apex is a very different game to Titanfall (single huge map, character-based, F2P, etc.), so I'm personally not surprised we're having growing pains. A lot of this stuff is new to us, even to the old hands.
If you're curious about our process: we have a dev and release branch. Before a big patch, we copy dev to release, work on stabilizing release and then... release it. (I've left out a lot of the finer details.)
These past few patches have not been the copy kind. Only very specific changes were made. We're due for a copy real soon. When that happens, that release will have this fix, along with all the other fixes that have accumulated since. I don't envy whoever needs to come up with the patch notes for that!
Anyway, I hope that clears things up a bit more.