Thanks for the feedback. The issue with team algos is that we definetly want them to be integrated into the terminal ranked-game ecosystem, so they can play against other algos. However, this means they are affecting the rating of these algos. Because they are part of this ranked ecosystem, we decided they should be on the leaderboard.
The problem comes in from the fact that many team and solo algos are very similar, and are often represented by the same user icon, which makes it appear to the public as though that user is on the leaderboard twice. In addition, it creates an inconsistency with how we distribute leaderboard based rewards - if a player and their team are in the top 10, who should we promote to the finals? Should we pass over the solo algo and put #11 in? If so, why did we display the solo algo on the leaderboard in the first place.
Additionally, some players play Terminal primarily as a team, and these players need their best team algo to show up.
We considered a number of situations - including the one that you are now in - when reworking the way we integrate teams into the leaderboard last week. We know it’s not perfect, but there are contradictory objectives involved and we think we made a reasonable compromise. We are open to more conversations and feedback, and if a number of users agree with you here, we would consider changing it back.
One hypothetical solution: We could have a toggle to ‘Show Redundant Solo/Team algos’ and ‘Show all algos’ or similar filters/toggles which would let you see the leaderboard the way you want, without affecting the ‘main leaderboard’. There are some leaderboard changes slotted for the next few weeks, I can probably throw it in with those if there is interest.