Skip to content
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

REQ: Make /teamlock affect 1on1 (regarding skins) #882

Open
suddendeathTV opened this issue Dec 20, 2023 Discussed in #881 · 1 comment
Open

REQ: Make /teamlock affect 1on1 (regarding skins) #882

suddendeathTV opened this issue Dec 20, 2023 Discussed in #881 · 1 comment

Comments

@suddendeathTV
Copy link

Discussed in #881

Originally posted by suddendeathTV December 21, 2023
Hey,

in TDM, the command teamlock 1 allows you to use teamskin and enemyskin to define skins of two separate teams as a third party (observer). This is especially useful for streaming where you may want one team to always remain one skincolor and the other team to remain the other teamcolor when either floating around the map in specmode or when hopping between players' perspectives.

There is currently no similar function for 1on1/duel, except using cl_name_as_skin, but in a tournament of 100+ players that solution requires hundreds of individual skins that completely break if someone changes their nickname.

Request: make teamlock affect 1on1/duel in the same way it affects TDM. Technically this might be more difficult than it sounds depending on how the server treats the game modes (I have no idea), but I'm sure someone is smart enough for it...

Hope someone could grab this request!

@suddendeathTV
Copy link
Author

Adding to this...

HUD-related items should preferably match the skins, e.g. hud_score_team, defined by hud_sortrules_* should match teamskin in obverver mode, and hud_score_enemy match enemyskin. You can force this true in TDM using different sortrules and teamlock 1, but there's no way to do this in 1on1/duel.

The observe point of view always considers a player on the screen as enemy, regardless of what you do.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant