Issue Type: Other
Impact: High
Frequency: Sometimes
Date First Experienced: 2021-02-28 01:02:00 (-05:00)
Date Last Experienced: 2021-03-19 03:03:00 (-04:00)
Rough Reproduction Steps:
- Have at least three teams in your game - one team should have AutoAssignable set to true, the others should have AutoAssignable to false
- Change a player’s team to an non-AutoAssignable team using a script - it appears as though using game:GetService(“Teams”):WaitForChild(“TeamName”) or setting the player’s TeamColor directly is the cause of this
- Observe that the player’s team is rarely set back to the AutoAssignable team - not the team you intended
I do not have an exact repro. This bug is really inconsistent and is driving me crazy. If there’s anything I can do to help test, please let me know.
It’s a possibility that this could be an issue with my code, but I have checked literally every line related to changing a player’s team and none of the code should set it back to the starting team.
My process has led me to believe this may be an engine bug. I have used numerous print statements, tracking, log dumps - and the key factor appears to be setting the team using :WaitForChild() or setting the team using TeamColor.
Expected Behavior:
The player is joins the team you scripted them to join - they do not default back to the AutoAssignable team.
Actual Behavior:
The player rarely is set to the AutoAssignable team for seemingly no reason.
Workaround:
None.