by ZeroKnight » 06 Aug 2012, 10:12
My vote went to option 2. It is my belief that this would probably be one of the least difficult solutions, as it's simple, and if I do say so, quite logical.
If a map only has affinities for 2 teams, then the map can't support multi. If a map only has affinities for 3 teams, then multi can be played, but Kappa (or whatever the "fourth" team is (don't drop sigma!!! D:)) gets excluded, and only 3 teams are available. If a map has affinities for all 4 teams... (you see where this is going)
It just seems logical and simple that way. No need to obfuscate (and therefore slow down) the (usually) quick vote process by allowing a number of teams to be specified when voting multi. No need to potentially break maps by controlling the number of teams via server-side var.
I do somewhat fancy the idea of having the map set the number of teams through affinities, as you could create maps specifically designed for a specific number of players, which would be pretty cool. However, that at the same time restricts you from playing with less teams than the set amount, and preventing playing said map with more teams than the map defines essentially accomplishes the same thing that option 2 does, in more or less the same way. (so it's clear that some of these options have overlapping effects)
I'd like to see some other peoples' opinions, and not just a tally in the vote count ;)