Thanks! That helped make sense of what I was reading.

[X] Plan Curse your sudden but inevitable betrayal!
[X] Training Akane: Nope
[X] Training Hazou: One More Brick
[X] Training Noburi: Atherosclerosis


I'll be responsible and vote this for now, since the vote may close soon. :)
Gasp! Curse your sudden but inevitable betrayal!
 
[X] Don't Rock the Boat

I don't really get the purpose of P for Party. I dont want Noburi to progress past the conservative dating guidelines that have been set for us by their culture. I also don't want this village to be too happy with us, since that will make Kannagi more likely to capitalize on it and push the marriage through.
 
Don't rock boat will be cut again, no way it won't be, and QMs have made their preference for shorter plans clear. Be kind, vote for Sudden inevitable betrayal. It doesn't hurt that it has fewer opportunities to go horribly wrong.

E it also makes use of mew/Vd in a great way to give us earlier warning if someone shows up on our doorstep
 
Last edited:
[X] Plan Curse your sudden but inevitable betrayal!
[X] Training Akane: Nope
[X] Training Hazou: One More Brick
[X] Training Noburi: Atherosclerosis
[X] Training Keiko: Whatever Takahashi Says
 
omg i actually woke up in time to see the vote.

Too bad nobody liked my plan :(

[X] Plan Curse your sudden but inevitable betrayal!
[X] Training Noburi: Atherosclerosis
 
omg i actually woke up in time to see the vote.

Too bad nobody liked my plan :(

[X] Plan Curse your sudden but inevitable betrayal!
[X] Training Noburi: Atherosclerosis
I liked it, we just need to (collectively) work on shortenning our plans without making repeats of the Kouta debacle. On which note, @eaglejarl @Velorien pretty please be moderately generous (with regards to what might be considered obvious, at least) with plans so we don't feel the need to elaborate every little detail.

e: We could also separate sections between what we do (in broad strokes) and how we do it. This way the QMs would have more freedom but still have insight on our thought processes (and hence, what things Hazou has thought of)), maybe.
 
Last edited:
Voting is closed.

Action Plan: Don't Rock the Boat is victorious.

Training Keiko: Whatever Takahashi Says
Training Noburi: Atherosclerosis

Are also victorious.

Training Hazou: One More Brick and Research Hazou: casino light seals are tied. Training Hazou: One More Brick has been selected.

Training Akane: Float like a Firefly REDUX and Training Akane: Nope are tied. Training Akane: Nope has been selected.
We are chickens with our heads cut off.
 
What would have been the total amount of votes for the lore update if [] Action Plan: Lore Update and [] Lore Update had been combined?
 
I think @Muer'ci means the votes after the deadline but before the "VOTING IS CLOSED" post not being counted.

I have no opinion either way. Both the temporal deadline and the post are convenient schelling points.
I see.

This definitely isn't the first time that voting has been handled like this, although I suspect we've done it the other way before as well. Either way, I think this is the way we should be doing it. There's no point saying "voting closes at 12 London time" if we mean "voting closes at whichever point after 12 London time Velorien is available to make the closing post". Also, there are some pretty obvious failure modes for the latter version.
 
Actually... it would have been tied for winning plan. I'll need to speak to @eaglejarl about this.

CounterBot goes to fairly long lengths to match up slightly differing plan names when counting votes. There are limits, however. I'm not going to implement predictive matching, Levenshtein distance, or typo correction. As a general rule, if you want your votes to count together you'll need to use the same names.

That said, I do already trim /Plan:?/i off the front. I can change that to /(?:Action|Training)?\s*Plan:?/i and then things like this will be combined in future.
 

I think @Muer'ci means the votes after the deadline but before the "VOTING IS CLOSED" post not being counted.
Yeah, pretty much this.

This definitely isn't the first time that voting has been handled like this, although I suspect we've done it the other way before as well.
Can't say I recall the former happening before, but if lost votes didn't change the outcome I probably wouldn't've noticed. The latter I'm fairly certain did happen, but I'm not going to search the thread to make a comparative analysis or something.

Either way, whatever you say is fine, as long as the rules are explicit and consistent. Tie-breaking rules are weird enough already.
 
Back
Top