Modding Best Practices: One Player's View

[somestrangeflea]

votecount as of post 233

with 12 alive, 7 will lynch before deadline

˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚

¬Jopoho

: 5: CoolBot, Khelvaster, jmar, Hjalti, Frostypants

izak013

Khelvaster

: 1: Numenorean7

not voting

: Sir Tornado, death_oman, Jopoho, Sir Wario, spurgistan, DGMavn
˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚˚

deadline is November 11 at 0100 GMT

In my games I use "¬" as a flag for who will be lynched at deadline. The flag only moves to another player once that other player has more votes than the current vote-flag holder. I came up with this system after reading a game where player X had five voes and player Y had four votes. Right before deadline, someone unvoted player X, and player Y was then lynched because he had been at four votes for a longer period of time.

I used to use "If deadline hits and there is a tie for the highest number of votes, then votes

and unvotes

will be reverted in reverse order from their placement until there is a clear leader, who will then be lynched". The italicised part is what makes the rule act in the same way as Adel's.

Now, however, I simply use "no majority = no lynch".