Always exclude GTV's from voting participants.
As an addition:
- always exclude GTV's from speclock lists
- add new referee command to manage speclock background message, like 'No spectators allowed\nPlease connect GTV:\n127.0.0.1:27970'

- add new referee command to manage speclock background message, like 'No spectators allowed\nPlease connect GTV:\n127.0.0.1:27970'

Sounds like a great idea:)

- Advancing \specinvite command parameter to string, so players could use \specinvite [id] [id] [id]

Prevent in-game players from being promoted referees.
1. Referee votable affects only spectators.
2. Only in-game players can participate in voting for referee.
3. Referee joined to the game drops his status.

if i own a server i want to be able to have my ref status even if i play.

Just type \referee [password], when you're in-game.

No. Played countless matches where we didn't have a dedicated spectactor so one of the players was ref in case of something.

You are still able to make \speconly and become a referee.
Or you meant kicking players with your referee status?
Referee is to help holding matches anyways.

I don't want to be a spec since I'm playing the match. I want to be able to kick players and call timeouts when necessary.

Is that okay, if someone else is able to kick, remove, putred you without owning a referee password?

Well to be ref he has to be voted by the majority of players. I'm assuming I'm playing with mature enough players in the first place. :-)

Mature enough don't need referee player to callvote.

I didn't say everybody was mature. Or without connection problems or whatever problems can arrive that makes it convenient to have a ref!

Feels like referee status gives you +10% LG! :D

Yes, that too :-)

I don't see any benefit in this.. Players should be allowed to be refs

The benefit is to make senseless \vote_allow_referee "0" for admin, who is just concerned about the server occupation or noobish actions.

Or you could ask some friend to help you making your match fair. And after you finished, somebody next from queue could \cv unreferee him as he didn't trust.

Always exclude spectators from voting participants, if there are in-game players.

But spectators aren't excluded from kick and remove votings.

But spectators aren't excluded from map, gameplay, match, mode and restart votings, if current match state isn't WARMUP.

What?

Is that the way it is right now or the way it is supposed to be?

It is just a suggestion to prevent players from blocking servers.

Makes sense for 1v1, not for teamgames imho.

Yeah.

1) by definition, spectators are there to observe, not to participate. no specs should be able to vote.

2) only those who choose to vote should be counted when determining the outcome of a vote. those who dont vote dont get a say either way.

3) in a pickup game /cv random can be F1'd by the two in-game captains, so the specs dont *need* to have a say in that really, however it wouldnt hurt if they did.

"1) by definition, spectators are there to observe, not to participate. no specs should be able to vote."
This isn't true on 1v1 servers where specs are queued and waiting to play. But I don't know if the non-teamplay voting system is up for revision as well.

"2) only those who choose to vote should be counted when determining the outcome of a vote. those who dont vote dont get a say either way."
I can see why you'd want this, but I think it's a bad idea. You shouldn't have to vote no every 2secs on random idiotic votes.

idiots calling frequent votes is not a valid justification for keeping a retarded vote system. vote spamming should be dealt with in the correct place: the vote limiting.

the problem with the current system is that there is no distinction possible between people who dont vote because they are impartial or afk, and those who vote no - the implication of which is that some votes are impossible to pass, when they 'should' be passed.

also even in 1v1, there are few votes that the spectating players need to have a say in. for example only the 2 ingame players should have a say in which map they want to play. therefore the default state of affairs should be that specs cant vote - and if there are any specific votes in specific gamemodes that need to be excepted from this rule, then so be it.

We need a better vote spamming system. If your votes fail it should get throttled much more quickly, if your votes are passing they should not count towards the vote limit.

Player and spec only votes would quickly get messy. One concept for spec voting is AFK greying out- a vote has a 10 second period where it cannot pass and specs are not counted toward the total required to pass unless they vote. The 10 second pause is there so that votes by players don't instantly pass if specs are intended to have a say (obviously if they're not intended to have a say they wouldn't).

Most servers don't have vote limit set (if you meant vote_limit).
But yeah you might be right that the annoyance of the occasional lamer spam voting is offset by the annoyance of not being able to pass votes because of afk/impartial players/specs being treated as nay votes by default.

I suggested it ages ago on the promode forums but no-one listened, makes no sense that non-participants in votes get counted as 'no' rather than null vote.

I kind of like ix's suggestion of the 10s grace period and I strongly disagree with injx's of counting AFK votes as yes. There are situations (mostly CA but ruined pickup games as well) where people get kick voted however nobody bothers to stop playing to vote yes/no. All of these people shouldn't be kicked just because we don't bother.

I also believe that complicated spec/no spec votes will get out of hand in 1v1. For example, what happens if the active players abuse vote a new map at 0:01?

I might be wrong, but I think he doesn't want them to be counted as yes but simply disregarded.

At the moment, if a vote gets 3 yes and 2 no with 10 people on the server, the actual count would be 3-7. If those votes would simply be disregarded, the end result would be 3-2 and it would depend on the voting ratio whether the vote passed.

since you completely mis-read my post i'll give you the idiot-proof version:

1) specs do not get the opportunity to vote

2) the outcome of a vote is based only on those who have actually voted. non-voters are ignored.

Startrespawn in CA doesn't work unless windelay is >4000. Personally I think there should be a way to vote the old format back (respawn at start of round, then countdown, windelay 0).

No idea why this was changed in the first place.

You should also rename fastrail to slowrail to better describe its effects.

Try \cv roundwarmup [sec]

Fastrail is fast as it has less cooldown effect.

When roundwarmup is <=10 you don't get to move before round starts. You just spawn in, possibly surrounded by enemies. I cant for the life of my understand why countdown is added to the END of rounds.

fastrail = slower fire rate. "fastswitch" I would understand

fastrail = slower fire rate. "fastswitch" I would understand

Where did you get this?

]\callvote fastrail

Usage: \callvote fastrail <0 or 1>
Sets ProMode RG switch time
0 - Normal (1.25 sec in CPM, 1.5 sec in PMC)
1 - Fast (1.0 sec)

Fast Rail Switch is currently DISABLED

fastrail enabled in cpm = 1500ms railgun reload time
fastrail disabled in cpm = 1250ms railgun reload time

hence my issue with the name. also, switching between servers with 1500ms reload and 1250 is not fun at all.

I think the best choice is to name it OLDRAIL. Or not...
Any name won't be right whichever way you look at it.
At least FASTRAIL is historically correct.

Historically correct means nothing if the original name was stupid. It should just be named "PMC fast rail switch" or something, and not be votable in gameplay cpm.

I assume you use gameplay cpm and not pmc since the only retards that still use pmc (moronic 100dmg rg and insane high damage lg) are ra3ca'ers.

PMC - Challenge ProMode Classic (2000-2003)
100 damage
1500ms rail reload
1500ms railswitch (or 1000ms with fastrail)

CPM - Challenge ProMode II (2004+)
80 damage
1250ms rail reload (or 1500ms with fastrail)
1250ms railswitch

Before CPMA 1.44, CPM gameplay with fastrail enabled would give PMC rail reload. Ironically this meant that fastrail gave slower rail reload.

This seems to be the idiotic behaviour that has been reintroduced if you vote fastrail while using cpm gameplay (which probably ought to be disabled). Blame the German ra3ca'ers.

----

And yes, there's definitely something fishy going on with CA round ends/beginnings and we are aware of the issues. Again you can blame the German CA'ers (and sort of the dev team for not caring enough about CA to properly test it before releasing). The reason it got tampered with was that CA'ers (rightly) claimed that 5sec wasn't enough to get into proper positions on maps, meaning that rounds would get decided by spawnluck. This is utterly irrelevant at the level most sane people play CA (ie, dm6 time waste), but apparently it's a big deal at serious professional CA level.

Simply having /cv roundwarmup would have been perfectly fine. They could get their 10 or 15 seconds if they wanted and the rest of us could go on with 5 as usual. Changing the entire behaviour and adding countdown AFTER rounds feels somewhat silly.

Yes it does. No idea if ra3/osp had after-round-windelay-countdown or if some CA'ers requested it for whatever reason. But I can't see any point in it at all.