Hey there!
Since recently (I think Sep.4th update) the plugin incorrectly attributes every player with a "T" even though they're not in a team. Hence now you can no longer tell solo players from teams. It seems Facepunch has changed something in the way team membership is handled, and Admin Radar can't handle that.
How to reproduce:
Fire up Admin Radar on a vanilla Rust server. See that everyone has a "T" next to their name. Choose any player you know who is not in a team. enter "teaminfo playerName" in console and verify "Player is not in a team"
V5.4.1 -> all players incorrectly attributed "T" even though they're not in a teamSolved
hi thanks, I've noted it down
I'm not having this issue. If the player is not in a team then I don't see a T next to their name. If they join a team then I see it. If they leave, then the T disappears again as expected. So either it was fixed or something else is causing your issue :p
Thanks nivex. For one I'm on Carbon - that might have to do with you being able or not reproduce. Then the last game update seems to have changed something with how players are handled, which caused a number of plugins to break or need updates. Not sure, but maybe that somehow corrected the problem if - as you say - you *now* can't reproduce. I will remove my patched AdminRadar and check the official plugin and see if the problem persists. For me this ticket is solved and can be closed - I've done my deeds by reporting.
Merged post
Hey nivex, for me (on Carbon) the new version 5.4.2 still incorrectly attributes players (sleepers) with a "T" even though they're not in a team.
For me this little change from line 1636 solves the problem:
Before
if (instance._teamColors.TryGetValue(target.currentTeam, out var team) && !config.Settings.ApplySameColor)
{
team = $"<color={team}>T</color>";
}After:
if (target.currentTeam != 0UL &&
instance._teamColors.TryGetValue(target.currentTeam, out var team) &&
!config.Settings.ApplySameColor)
{
team = $"<color={team}>T</color>";
}
else
{
team = string.Empty;
} not sure how I missed your next response but thanks minimerust, I will have that in the next update!