SFoL 61.5 - Dead Chat

Forum Matches Completed
#601

listen there’s convincing claims
and then there’s claiming priest who won’t out any info because the chronomancer has info that “shouldn’t be outed” and also alice doesn’t want to be revived

1 Like
#602
i’m self-resolving
2 Likes
#603

Why do I get the feeling this claim isn’t the most trusted?

#604

Want to argue with me about why Arete being converted was a moderror or should we do that postgame?

#605

What???
What happened?

#606

Apparently Guardian stops Archdeacon SF.

#607

Like, it shouldn’t have failed.

#608

Like, why would Gaurdian be able to prevent something that isn’t a visit?

#609

It’s not a visit only for tracking purposes as you shouldn’t be able to use mech to read the King.

#610

It says it doesn’t count as a visit, so Guardian shouldn’t be able to prevent it.

#611

Well, also for Frostwalker’s Ice Spikes and probably other things.

#612

I agree. I would resolve it like you’re saying. Wording is king.

1 Like
#613

Factional biases aside, the wording clearly doesn’t imply that there are exceptions. Ninja means ninja.

#614

Would be funny if the pity conversion randed to Arete anyway.

#615

Well, in that case they wouldn’t count as a convertable player, right?

#616

I think scum wins this game regardless if the conversion happens or not, but I think it’s still not the correct way to resolve it. But I’m not the host, so.

#617

Because of this, SF continues to be a meme.

1 Like
#618

I think this is the first ever instance when it would have actually stopped a conversion, but didn’t because of lolactionresolution.

1 Like
#619

Ah, right. Yeah, it would rand to someone else.
At this point I feel like any convert is good. Town has no cohesion and no idea where the wolves are.

#620

Y’know what sucks? After this game a lot of people are going to completely ignore associative reads for a with the justification that “bUsSiNg ExIsTs” nevermind that the reason this bus was flawless was because it was completely accidental.

3 Likes