-
Notifications
You must be signed in to change notification settings - Fork 10
[Feature Request] Add Minimum players to Ready up Cvar #128
Comments
Can you not just |
Bascially everytime the Admins or Casters have to keep on telling all the Users in each and every Server to type that command |
Fair point, but this isn't in my use-case since I only deal with leagues that are 5v5. PRs are welcome, but I won't be working on this. |
Question about this - do you want it defined per-match, or would you want it defined on a global basis? If the latter, this should be easy enough to implement without touching the database, even. |
To satisfy issue #128. It's global and if not found in the configs it should default back to 5.
I think per Match should be better option. |
Merge request #179 should solve this now |
Confirmed working in testing yesterday. |
i did test today with 1vs1 and it was not working for me. |
Go to your match config, (append |
Webpanel is hosted locally on LAN system and routed via hosts file properly. |
And does this config work if you just set it with get5 as a match template and load it through JSON with get5? It could be a get5 bug. |
i tried creating 1vs1.cfg and added maximum players per team as 1 instead of minimum players to ready up and it worked at that time. I think it requires maximum players per team to be the correct option instead of minimum players getting ready up.
|
That's what I was figuring. Didn't want to add it in, but I guess it may be required. I'll probably swap the text of "Min players to ready" and change to "Max player per team" on the match creation page, and call build_match_dict with both keys. Not sure why that's intended for get5 itself, but oh well I suppose. I'll change this during lunch. |
Okay, should be fixed in the dev branch now. Cheers! |
As per match config file we can define how many minimum players require to start the match, with this addition on panel it can be easily manageable with 1 vs 1 and other modes also.
The text was updated successfully, but these errors were encountered: