VOTING_BIAS: ( default 0 )
acts like a crowd of calm players opposing every change ( so far only every kick ). Use this if you want stronger majorities required to kick someone. MIN_VOTERS should be set higher than this, since every vote with less or equal to VOTING_BIAS voters online gets rejected.
The exact formula:
PRO is the number of voters supporting a change ( the submitter is included )
CON is the number of voters opposing the change
NOT is the number of voters that have not yet cast their vote
A vote gets rejected if CON+VOTING_BIAS >= PRO+NOT ( this is checked first ) and accepted if PRO >= CON+VOTING_BIAS+NOT.
Example: If you set VOTING_BIAS to 1 and there are 5 players online, four of them have to get together to kick the fifth. If only three are in favor of kicking, PRO=3, CON=2 and 2+1 >= 3, so the vote gets rejected.
ALLOW_VOTING_SPECTATOR: ( default 0 )
allows spectators to vote if set to 1. The old behavior was that spectator voting was allowed. Note that only one vote is accepted per IP, so you have to have several pulic IPs at your disposal to vote-cheat even if this is set.
VOTING_PRIVACY: ( default 1 )
determines who gets informed about votes. If
VOTING_PRIVACY >= 2: no reports are given. This is the old behavior.
VOTING_PRIVACY <= 1: the initiator of a vote gets logged to the server console. This feature was requested by many.
VOTING_PRIVACY <= 0: the votes get logged, too.
VOTING_PRIVACY <= -1: the initiator of the vote is made public.
VOTING_PRIVACY <= -2: the votes are made public, too.
The theory here is that by making voting public, you put a higher psychological barrier up for abusers without preventing legitimate use.
SIDE EFFECT: if VOTING_PRIVACY is < 0 and ALLOW_VOTING_SPECTATOR is set to 1, the IPs of spectators who vote are published ( since they have no player name set to identify them by ). Serves them right
Could be numerous reasons, but I"m not getting any error messages or anything.
).
