New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Give each member of FT a color in scoreboard, on mini-map and command map #1271
Labels
Milestone
Comments
ETLegacyTeam
added
cat: mod CGAME
Category mod (cgame)
💡 Feature
New feature or request
labels
Mar 5, 2020
From: @rmarquis (Spyhawk) {TODO} We can do something similar for:
Also:
Check how the existing FT selection members feature can be leveraged/improved upon with that idea. |
rmarquis
added a commit
that referenced
this issue
Apr 28, 2020
rmarquis
added a commit
that referenced
this issue
Apr 30, 2020
rmarquis
added a commit
that referenced
this issue
Apr 30, 2020
rmarquis
added a commit
that referenced
this issue
May 30, 2020
rmarquis
added a commit
that referenced
this issue
May 30, 2020
rmarquis
added a commit
that referenced
this issue
Jun 4, 2020
rmarquis
added a commit
that referenced
this issue
Jun 4, 2020
rmarquis
added a commit
that referenced
this issue
Jun 4, 2020
Apparently, selected members should have been colored on map since vanilla, but that never worked.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Author: @BystryPL (Bystry)
Date: 2019-05-01
Redmine Issue: 1271, https://dev.etlegacy.com/issues/1271
An interesting feature from CS:GO matchmaking. It consists of giving each player from your team a color (green, yellow, blue, etc.) on both mini-map, command map and scoreboard. It would be especially convenient for mixed matches and future matchmaking system, in which case you play with random people. That way you don't have to pronounce weird nicks and also you can see where exactly each player is at any given time.
Related commit(s):
44ba59a - mod: reverted max members per fireteam to original..
The text was updated successfully, but these errors were encountered: