Jump to content

Stick.

Members
  • Posts

    3863
  • Joined

  • Last visited

  • Days Won

    2

Everything posted by Stick.

  1. @The Known Novel does a roleblock cancel both a passive soothe and a Night Kill if we’re talking about a hypothetical e!Soother submitting the kill? @Amanuensis I targeted you and no one visited you Edit: tbh I was half joking with the cycle shortening comment but the fact that Silho immediately agreed is not a village look
  2. What kill xD Aman could be elim tbh based on what we’ve got but I personally don’t see it
  3. I was implying that perhaps we ought to shorten the cycle You know, to make it more special!
  4. Time for the birthday exe then happy birthday Silho one vote equals one present
  5. I’m assuming Silho was roleblocked? Shining Silhouette
  6. It's funny cuz this quokka right here is the first quokka to bless this game Clearly it's too powerful
  7. Hm. I did consider this, but I didn't put a lot of stock in it since I thought you might have been busy IRL and perhaps did not have time to coordinate the kill submission. Silho is already dying to the filter We might get both flips! idk if that's good or bad tho Edit: Nope im dumb the inactivity filter is 2 cycles not 1!!!
  8. If Silho doesn't get exed Aman can roleblock their soothe next cycle (right?) if he lives. idk they're gonna die to the filter I think xD
  9. VC: JNV(1): Stick Silho(1): Aman, Alpha Alpha(1): Mat Lookin good tbh
  10. Another problem with e!Silho is their C2 vote tbh. They knew were likely to successfully soothe a vote off themself, in which case DeTess was the lead exe as far as the elims were concerned. Why wouldn’t e!Silho vote for DeTess at that stage? They instead voted for JNV around 1.5 hours before rollover. That vote achieved nothing for e!Silho- voting DeTess would’ve left them with some distancing and voting me (or v!Aman) would’ve given their partner a 50% chance of survival. Edit: Considering the C1 vote in an e!Silho world: It's reasonable to assume that DeTess would have agreed on an NK target with their teammate before logging off for the cycle, yes? Scenario A: The elims had intended to kill Araris. But around 2 hours to rollover, e!Silho for some reason adds a second vote to Araris, bringing him into the 3-way tie. Instead of adding to any of the four village wagons present, e!Silho decides to attempt exeing their NK target. As Silho is a soother (passive action) and created no PMs D1, perhaps at this point they go and override the Araris kill order and change it maybe Mat or JNV as everyone else was pretty much on the table realistically. Around 40 minutes later though Silho changes their vote to Archer cuz Aman asked (?). They indicate that this is their last post for the cycle, locking that vote in as their final. At this point they go and place the kill back on Araris, despite the possibility of that wagon actually taking off while Silho was away. Scenario B: The elims had intended to kill Archer (possible, as the Archer wagon did not exist while DeTess was here, and they had him in their positive/neutral pile). e!Silho votes Araris over Archer cuz why not but panics at the slightest inquiry regarding this and quickly switches to Archer. At this point they override the existing Archer kill order by one on Araris and turn in for the day, despite the possibility of the Araris wagon actually taking off while Silho was away. Scenario C: The elims had intended to kill someone other than Araris/Archer. Perhaps Mat or JNV. It doesn't matter to e!Silho who dies to the exe now, so all their actions are justifiable as elim apathy. But for some inexplicable reason eSilho overrides the existing kill order and changes it to Araris. idk none of these scenarios are particularly convincing
  11. Oh, sorry xD I just think that e!Silho would have remembered to create his PMs if DeTess was submitting the kills like that's a waste of a solid alibi Edit: There's also the argument that e!Soother in a 9 player game with two village factions playing against each other is a little questionable
  12. I know what you're trying to say here, but funnily enough it sounds like a Mobborn claim xD Alpha/Aman Mobborn partners - feels different than before cuz you just got recruited But anyway - why do you think Aman is DeTess' teammate? Because he voted on the counter wagon last cycle? It's possible, ngl. Just unlikely, imo.
  13. Here, they said they don't suspect DeTess anymore: Will note that this was 16 minutes after Mat had moved his vote to DeTess. Yeah, I haven't played with DeTess (E or V) in probably I think 5 years o.O So idk what their level of distancing is like. They voted Alpha well after rollovet so maybe they were banking on people being too caught up with other more popular exe targets at that stage in the cycle. They had a brief exchange here: But it would've been too easy had DeTess unvoted Alpha after this little back and forth xD
  14. Hm. I think I 100% believe that claim, but it doesn't alleviate my suspicions because DeTess presumably had been submitting the kills. That said, I'm open to e!Alpha - I recall them saying their DeTess suspicion had died down last cycle around the time I started pushing for the DeTess exe. In addition to that, they also PM'd me asking if I thought Mobborn!DeTess made sense.
  15. A little risky, given that people were ready to vote Silho out but no one was really elim-reading Alpha
  16. Mat's gotta be the tineye - in that case it all works out. why would you think that's the implication? Edit: didn't they? last cycle when they said they can wait for my exe till C3?
  17. That leaves Silho as the tineye Edit: NO cuz theyre the soother so somebody's lying tehe
  18. BTW I scanned you and found that Silho targeted you so I guess RNG picked you for the soothe. Which means if Mat tried to recruit you again he failed again fr rip
  19. That means we can't clear JNV for making a PM with me tbh hard to do that with the free tineye PM existing anyway
  20. Good So Silho’s a soother. Which means a smoker probably exists. I wonder why the elims didn’t have DeTess send in the kill? Aman was less likely to roleblock somebody already slated to die. Unless that’s exactly what he did.
  21. It’s straight up wrong for me it says 8:30 am yesterday but it’s past 12 am now so it shouldn’t say yesterday anymore and it had my head spinning for a minute. Weird.
  22. what ._. I don’t think so The time posts on this thread are messing with my perception of time but I’m sure it was two days ago that I was preparing to die to the tie
  23. It’s tied at 2/2 now? That sounds okay to me and the two will probably self pres onto each other bringing it to 3/3 leaving it up to Alpha to break the tie if they want to, and if the game’s got any vote manip at all I suspect we’ll see it in play this cycle. Edit: that’s me for the cycle, probably
×
×
  • Create New...