About Recon characters

xfunax​ 

Could you be more specific about which RECON legends are no longer needed and why you think that.

Providing more to the point info would really help as feedback. 

Thanks for your post.

Looking forward to your reply. 

Bloodhound and Shea. If you check the enemy's location with a survey beacon, you can predict the enemy's location to a certain extent, so the priority of choosing them is low. This is assuming that you are familiar with Apex.　It's not like they're strong in battle. In battle, assault characters with grenades and short reload times are overwhelmingly stronger.

xfunax​ 

Thank for your reply. 

BH and Seer can both be beasts at tracking down other Legends that are near them especially if they had used a beacon before to get their general location in the first place.  This allows them to provide more detailed info with their abilities in CC to their own teammates so as to quickly swarm an out of pocket opponent putting the rest of that team at a 2v3 disadvantage. 

I apologize if there are some mistakes because there are some parts that cannot be understood by machine translation.　You're right that both Bloodhound and Shea excel at detecting nearby enemies.　Being able to grasp the position of nearby enemies during combat is useful, but this can be compensated for to some extent by individual combat skills.　However, without a survey beacon, the chances of unexpected encounters with enemies increase, making skills that can instantly notify allies of enemy locations more valuable.　If a survey beacon can show enemy locations to all allies and make it easier to predict their approach, I believe you will have a better chance of winning a battle if you prioritize characters with skills that give you a direct advantage in combat, rather than characters with survey skills that can be compensated for by personal technique.　Currently, Sparrow or Crypto have strong ultimate skills in battle. If you want to stabilize your ranking, Valkyrie is the way to go. Pathfinder can take high ground. Mirage is an all-rounder.　As for Shea, if the perfect combination could be achieved, she would be strong, but it would be very difficult.　Bloodhounds lack combat skills, and their detection skill is useless in battle unless it is used in conjunction with the movements of their allies.　Basically it will depend on the player's skill level, but if they have the same skill level, it is thought that Bloodhound and Shea will have a lower priority.　Sia will need to improve her skills to maintain her defensive position, while Bloodhound will need to improve his combat skills.

You're right, the abilities of Survey Beacons and Recon class characters definitely overlap, and it's especially noticeable with Seer and Bloodhound. I'd also add that the same issue applies to Ring Consoles and Controller characters.

I think it would be better to limit those roles strictly to Recon and Controller characters. I don't think it's good for characters like Pathfinder, Alter, Mirage, and Fuse to have abilities that cross over into other classes.

I also think the scan animation should be removed. It would be much more convenient and smoother if Survey Beacons and Ring Consoles could be used just by aiming your cursor at them, similar to how Skirmishers scan care packages.

There are now so many examples of duplicated abilities, abilities bleeding from one class to another... it's as if the trajectory, plotted out to the end, leads to a place where any legend can pick up any other legend's ultimate from the ground. Hey, wait a minute. They've already done that in an LTM. And, hey wait another hot minute. Garbage ideas from LTMs often make their way into the main game over time. You like Valk's ultimate but don't want to play Valk? Just pick her ult up off the ground. You want to run fast like Octane but don't want to play Octane? Just have a... skirmisher class teammate... skirmisher, right? Whatever. Doesn't matter. It's dumb. And I'm sure there are a lot of other examples I'm not thinking of at the moment. What honestly is even the point of any of this? Change for the sake of change. And moreover, changes that are easy to make because they don't require any major overhaul in coding or therefore in budget. Cheap and easy. And I mean "cheap" in every possible sense of the word.