and now that thatās overā¦
This post wonāt be pretty. I donāt want anybody Iām talking about to feel like this is a witchhunt, but there are lessons to be learned from this. I apologize if anyone feels targeted from this, as my intent here is to stop bad things from happening again. Most of these lessons arenāt exclusive to this game.
Disclaimer: I do not claim to have all of the right answers. This post is highly subjective. I do, however, believe that all of the main points are approaching objectivity.
PLAY THE GAME YOU SIGN UP FOR
The fact that not once, but twice during this game we had villagers submitting night actions too late in VERY pivotal moments isā¦ sigh. I get that things happen. Things come up. Life gets busy. Shit happens, Iām not going to pretend that this is a crime nobody can ever commit for a reason literally ever. But when your night action is decided before night even starts, taking a minute aside to submit your already predetermined action (or pre-queueing it before the day ends if the host allows it) shouldnāt be that much to ask of a player in a span of 23 hours. Relevant video.
KILL OUTTED WOLVES
This is somewhat less excusable. This should be common sense. When somebody is literally openwolfing, especially in a setup that is guaranteed to have no funny third parties, you kill them. We had two situations where lolcatters escaped the execution. Both times the suggested counterwagon hit a villager. TWICE.
The first time it happened it might have ended up being +EV, but this was because of a hero play that removed said playersā death immunity and the fact town had ~5 KP that night. You canāt account for that in other games.
The second time was an outright fucking atrocity. The game was solved. The team was in your hands. One of them starts openwolfing and lolcatting. Town has no killpower outside of the execution today. KILL THE OPENWOLFER!!!
Unless thereās a mechanical advantage to not killing a very specific wolf (eg: FoL Unseen), there should never be a debate here. In this scenario there was no advantage to killing one wolf over the other. The outcome was the same, the Scum Killer would promote into the Converter if you killed the Converter, and the Converter would stay as the Converter if the Killer died.
READ YOUR NIGHT ACTIONS AND RESULTS CAREFULLY
This applies tenfold if youāre attempting to solve a game mechanically.
This specific note may not have had noticeable impact to the players, because nobody actually knew it happened, but this mistake was likely the nail in the coffin for town.
To avoid naming names, a certain player (player ) thought they used a night action on player Y when they actually acted on player X, which, when paired with another night action being used on them in attempts to confirm the other player (player ), made player think that they were unable to confirm player s action. They were.
To be clear, this is a very valid and easy mistake to make. But itās an easy one to fix. Double check that shit.
TIME FAVORS TOWN, USE IT
This applies more and more the longer a game goes. The fact that the game deciding execute was done three hours into the day is ridiculous.
You have 48 hours. Not using even 24 is unacceptable when youāre approaching MyLo. The only exceptions to this would be likeā¦ executing a literally outted wolf. Too bad you guys had none of those, right? wait
DONāT THROW THE GAME
I donāt think thereās more to even say here?
SCUMSLIPS ARENāT REAL ā¦except when they are
This one is hard to go into specific without using player names, but Iāll try.
Iāll use , , and in replacement of players for this.
Player speculates that a player (letās call them ) cannot be aligned with a dead wolf because player is claiming to have used a tracker ability on a player. However, player explains their case in a way that, at a glance, appears to be TMIing the dead wolf (who flipped as Generic Scum Killer) to having been exactly a specific wolf.
The issue lies in language barriers, as Player is not a native english speaker. Player is called out for TMIing the dead wolf. Coincidentally, Player had appeared to correctly guess the class of the dead wolf.
However, if you read their post closely, itās a speculation post, clear as day. Their logic makes sense.
"Player cannot be the BD, because Player is claiming to be [CLASS]
, and the [BD CONVERT OF
[CLASS]]
would not have any information worth claiming because of the D1 execution.
However, not a single villager tried to consider this stance, and only saw it as TMI.
Player was sentenced to death for this, and was town.
Lesson: Coincidences happen. Speculation is not TMI. The language barrier between players can make posts appear different than intended, and when youāre accusing a post of TMI, you need to consider that deeply.
Player mistakenly makes a post that they would be a not match to a parity cop with a player who, while they flipped wolf, were tailored to appear as town.
The case against player is that they were either TMIing the wolf as not being tailored that night, or were TMIing themselves as the godfather of the other scum faction, although this doesnāt make very much sense as theyād view themselves as always appearing town to investigative checks regardless.
To defend town for a moment here, this kind of slip is possible to come from a wolf. Hell, Iād say this is a reasonable case to bring up. But in these circumstances, itās shaky at best.
The problem here is that this is the type of slip a villager is prone to making. Instinctively, as a villager expects to not be a match with a wolf. And, even worse, for player to be a wolf TMIing the tailor as fake, theyād have to be exactly the wolf who was executed the day before player was vigged. Which means the case on them is ātheyāre godfather who slipped forgetting they were a godfatherā andā¦ this is confusing.
I feel like Iām remembering this case wrong, because if not then the vig shot on them is even worse than I remembered.
Either way. Player flips town.
Lesson: Town can make posts that look like slips. The more investigative altering abilities in play, the more confusing they can be and reasonable it is to mix them up.
Player fails to comment on feedback the class player claims to be getting informed about something they arenāt informed about.
When called out, player immediately tells the accuser theyāre wrong and that theyāre just RTing them, and quotes the classcard of said class.
This is a slip that is more likely to come from a wolf. They never explicitly stated they were informed of this fact, but itās heavily implied they believed they would be.
Player , as the emoji applies, was converted into being a wolf.
Lesson: Just know when scumslips are real!
Real Lesson: A slip along the lines of claiming something happened that just doesnāt happen is something that might actually be a real slip.
READS! USE THEM!
This is like, the entire basis of FM, but specifically, the above 3 cases could all easily be solved if some reads were incorporated into their situations.
If we want to use meta, both player and were fairly deep into their townmetas ā but if you set that aside, the intentions of player especially were significantly more pure than wolves are usually capable of.
Player , on the day they āslippedā, did several wolfy things, and made a few contradictions.
But the case on all 3 of these players didnāt really consider any macro readings of the player at all. They were just āscumslip = badā except when the āscumslipā actually equaled bad.
PRs DO NOT NEED TO CLAIM ON DAY 1 OR 2
Additionally, regardless of the circumstance, you also shouldnāt out PRs if youāre a villager, either.
Especially when they convert into incredibly strong classes.
Iād say āmassclaim badā, but once the PRs were outted it had merit, and at that point I donāt think many people had claimed.
If I pretend this entire post isnāt about specifically SFoL63, a majority of this site really sucks at PR cover as a whole.
I think this is about everything I noticed go terribly wrong for town in SFoL63. Might have missed something since Iām bad at keeping my thoughts in my head when I write long posts like this.
TL;DR: read the big text and then read all of the not big text