You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, for those who do not use this system, just the .ready command to start the PUG, going live does not have a limit of players per team.
Example, my server has 12 slots, but 10 players on the server and everyone types .ready the PUG starts, it goes LIVE.
However, if players enter the server, they are not blocked from SPEC until a player who is on the teams disconnects. It would be interesting to have some cvar to control this limit of players on the team during LIVE and only allow SPEC to enter the teams if someone on the team disconnects, in this case someone abandons the match.
WarMod [BFG] plugin for CSGO had a feature like this, I believe it can help.
Apologies for delayed reply, I'll be doing some research on this feature, though locking teams in pugs is something we can do via a convar. I'll be checking on it soon.
Currently we can control the player limit on the team using the JSON file: https://shobhit-pathak.github.io/MatchZy/match_setup/
However, for those who do not use this system, just the
.ready
command to start the PUG, going live does not have a limit of players per team.Example, my server has 12 slots, but 10 players on the server and everyone types
.ready
the PUG starts, it goes LIVE.However, if players enter the server, they are not blocked from SPEC until a player who is on the teams disconnects. It would be interesting to have some cvar to control this limit of players on the team during LIVE and only allow SPEC to enter the teams if someone on the team disconnects, in this case someone abandons the match.
WarMod [BFG] plugin for CSGO had a feature like this, I believe it can help.
https://github.com/Versatile-BFG/Warmod_BFG/blob/4121c877fc8c9755ba1d46585d4a88e874f75703/scripting/warmod.sp#L527-L529
The text was updated successfully, but these errors were encountered: