Okay, to take the spotlight away from the Ox Farmer vs. Goat Doctor debate for a second.
Now that baud has compiled their version of a tallying program compatible with the forums (thanks, mate!), how about we automate the process a little? Our flipping-flopping tendencies make counting votes a mess, and mistakes are inevitably made. Not to mention it creates weird ties that resolve differently depending on how you count flops. Like currently if one counts Bull->Fish, you get one winner, but if you count Fish->Archer, you get another.
Can we institute a unified vote format? NetTally comes with a wiki, and anyone interested can read about it here:
https://github.com/Kinematics/NetTally/wiki/Writing-Votes
Basically, the choices at the end could be written in the following format:
[ ] Choice 1
[ ] Choice 2
[ ] Choice 3
And then the players can copy their preferred choice and vote like this by putting an "x" or "X" mark inside:
[x] Choice 1
(It needs to be on a new line, and the exact match, the "[x]" tells the program that it is a vote)
If there are multiple things to vote for, votes can be done in categories:
[ ] [CLASS] Adjutant
[ ] [CLASS] Doctor
[ ] [CLASS] Farmer
[ ] [SIGN] Tiger
[ ] [SIGN] Goat
[ ] [SIGN] Ox
and the players can "x" the ones they want. The program can count a winner in each category separately.
Finally, if we are talking preferences, there is a ranked vote, which means something close to flopping, except it isn't. Flopping means switching a vote entirely; ranked means assigning the vote a weight. Assigning the vote any weight at all props it higher than not voting for the entry. So one could vote:
[1] [SIGN] Tiger
[7] [SIGN] Goat
[2] [SIGN] Ox
and that would mean something akin to Tiger>Ox>>>>>Goat (>everything else), but without creating complicated situations with uncertain outcomes. At any point the program would know what the most popular consensus is. If you only want Tiger, just leave it at [1] [SIGN] Tiger
Ranked votes (numbers) should not be mixed with regular ones ('x'). The program doesn't know how to weigh an "x", though I suppose we could make it default to [1]...
This is something that needs to be prompted by GM themselves, since they are the only person capable of defining a standard for their vote. Tagging
treave to take a look at this. Perhaps we can cast the next vote using this system, and see if it works better?
It should, in theory, eliminate the underlying
cause for flopping:
Quest voting has the additional issue that all votes are explicitly non-anonymous, and fully visible to all users, and thus quite vulnerable to certain types of exploits, and to encouraging users to vote for non-preferred options simply to stop a least-preferred option from winning.