|
Post by Roman on Nov 11, 2010 22:05:44 GMT -5
Uhhhh....Aren't all the votes tallied after the 9pm close....?
|
|
|
Post by phyphor on Nov 11, 2010 22:24:49 GMT -5
For all days that are complete, yes
Our kill is considered to occur on the most recent day we send it in on, which won't complete for another 18+ hours after we send in the order
|
|
|
Post by Roman on Nov 11, 2010 22:26:23 GMT -5
So that means we can pick our kill 10min before they're all counted up (hence we can pick someone not dying to the vote?))
|
|
|
Post by phyphor on Nov 11, 2010 22:31:57 GMT -5
Anyway, in case we do have a kill already or something. Any objections to Diorinix?
|
|
|
Post by Roman on Nov 11, 2010 22:42:53 GMT -5
Not particularly but i think we should try and get rid of active players with a propensity for keeping track of everything...
I think we actually should kill spreadsheeters (darian). If the village doesn't 'get' the vote and how to use it effectively we stand a better chance.
Lucedes: This is a good suggestion, and lucedes should probably die for it.
|
|
|
Post by crimsoncoyote on Nov 11, 2010 22:48:22 GMT -5
Anyway, I read over the PM and we're kinda screwed for our kill too. Let's say we submit it at 8PM, before the "end of day," then the person we target would die 3 cycles later at the end of the 3pm day and I suppose we would get results at the next 9pm summary... I think This is correct. It's basically a "delayed" kill. We should be trying to hit people we think will not be voted out in the next few time-cycles. One good thing, though, is that there's the chance that the vig(s) work in a similar way. Also: what is the exact wording on the seer power? If there's a delay effect to that too, things could get interesting.
|
|
|
Post by Roman on Nov 11, 2010 22:55:53 GMT -5
Yeah, we probably want to pick our kills as early as possible. i.e. in the first 6 hours immediately following vote close...
|
|
|
Post by crimsoncoyote on Nov 11, 2010 23:58:23 GMT -5
Okay, after some clarification from Rend, the kill works like a normal kill in any sane game. The line in the PM about what day it occurs is pretty much an attribute/descriptor.
Using the example put forth before: we send in the kill at 8 PM. The kill occurs when the (full) day ends, i.e. 9 PM. However, it is listed as a kill in the 3 PM-9 PM block (which is what that line actually refers to).
Similarly, if we were to submit the order at 10 AM, the kill would still occur at 9 PM that day, but it would be listed as a kill that happened in the 9 AM-3 PM block.
EDIT: We need to make sure to be careful when we submit the order, because it can be used as information to cross-reference against online status if that's not set to invisible. We can also try to use it to attempt to frame people active in a specific time-period... but that might be difficult to pull off.
|
|
|
Post by Roman on Nov 12, 2010 0:07:37 GMT -5
Yeah that makes more sense...So it takes place in the first day to end after we send it in.
|
|
|
Post by Roman on Nov 12, 2010 0:21:59 GMT -5
Why the fuck are so many people voting for spoit?
|
|
|
Post by spoit on Nov 12, 2010 1:08:00 GMT -5
Well, if nothing else, this gambit has temporarily shifted a boatload of votes onto dunadan. Thought it may not have been worth the further clarification on how votes work
|
|
|
Post by Roman on Nov 12, 2010 3:39:19 GMT -5
Yeah....We need to kill darian...
|
|
|
Post by samurai6966 on Nov 12, 2010 8:35:10 GMT -5
I'll vote Darian next time block. I have to "grudge" simonwolf to keep suspensions off me.
|
|
|
Post by niceguy on Nov 12, 2010 9:10:11 GMT -5
yeah, let's kill darian
|
|
|
Post by Roman on Nov 12, 2010 9:39:06 GMT -5
I don't think there is any reason to vote darian... Lets just kill him...
Also, since we have a seer...Thoughts on who to target?
|
|