You might be asking: Why did you add a custom teams module if there’s already Teams.
Basically, you can’t really do much with the normal teams. So the best way to add more to it, is by adding a new one!
I’ve planned stuff for the module for example: IsLocked. If the team’s Attribute (IsLocked) is set to true, then no players can join in. (The attribute is in the Folder, except I just haven’t worked out with that part yet.)
Don’t worry! This module will not only be based off of my ideas, but your suggestions as well! Really looking forward to your amazing ideas!
Looking through the code you’re not really doing anything that normal Teams can’t,
you can already add players into a team by setting their team property to the team instance, and if you need to keep track of players you can always call Team:GetPlayers() or listen for Team.PlayerAdded and Team.PlayerRemoved events if you want to go fancy.
I’d go for for Team:GetPlayers() but I won’t go for Team.PlayerAdded or Team.PlayerRemoved, since when calliing ___.new(), it basically returns the team folder. And there are already similar functions to it, for example: Team.ChildAdded and Team.ChildRemoved. But, still thanks for giving the suggestion!
Edit: I might go for PlayerAdded and PlayerRemoved since sometimes people might add other instances to the teams’ folder.
could u explain the capabilities of this better in this post itself so tht i cn get a better idea of why i should use this since there are many team systems already out there