Spring RTS Engine

Thanx for explaining vbs & andrej.

dansan wrote:

the above wrote:Good starting point would be to just make upping !teamsize require a vote.

That would be a rule in spads/springie, right? That would mean it'd be mod-agnostic and thus would have to be configurable (to not impose rule on other mods.. ah.. games :) Is this right? Bibim / Licho - any of you reading this, and can confirm?
If it'd be configurable, then host-admins could just disable it, and we'd be back to zero... or not?
IMO 8v8 happens on 8v8 hosts because ppl want to play 8v8 - so the !teamsize-vote will go "yes" -> Not sure if it's worth to invest resources into this.

8v8 happens already when one person wants it and does not get kicked immediately. If it is voted for, fair enough.

I do think it is sensible option for each and every autohost there is though. Yes it is already configurable, but the default should definitely be changed.
Even if some autohost owner would be sad enough to force (instead of letting them vote, or putting it high when they personally want it) their players to play big games by changing Teamsize back to freely settable, well whatever. Would say a lot about their attitudes and motives for hosting.

Just to be clear about SPADS default configuration, and the historic reasons behind it:

bibim (28 Nov 2008) wrote: Initially I planned to prevent changing the autolock number (i.e. "teamSize" parameter in Spads, when autolocking is activated) directly, forcing people to call a vote when they need to change it. The goal was to prevent people from unlocking a battle just because they have friends who want to join, thus transforming a ready-to-launch 5v5 game into a 8v8 mess on a small map... But I realized people were too much used to being able to change the autolock number as they want, so finally I kept Springie behavior by default...

In other words, at this time SPADS wasn't popular (not even released publicly), so players were used to Springie only and didn't want to play on autohosts where they couldn't change autolock/teamsize directly as they want.

Later however, I added a functionality in SPADS which improved the freeSettings system, allowing autohost admins to limit values which can be set directly for each free setting (other values still require a vote). At the same time I also changed default configuration so that only values 1 to 6 for teamSize can be set without vote (that was the main motivation for this new functionality actually)

bibim (28 Apr 2011) wrote:Default configuration was to allow changing teamSize value directly. This has changed more than 6 months ago, to make it require vote for values greater than 6 (values 1-6 can still be set directly without vote).

So currently (and for more than one year now), default SPADS configuration only allows changing teamSize directly (without vote) if the new teamSize value is < 7.

tbh play Zero-K.. community is comparatively very friendly to new players