Ross Esmond Notes

MsRyan Comment on Strike Twelve

OVERALL THOUGHTS 💭
The cards feature a simple, clean design with symbols that are easily identified and distinguished. The game seems to be highly replayable, and I love that there's not a need for many other assets other than the cards (including optional/preferential items). Once I got past comprehending what the rules relayed about gameplay, I quickly found myself enjoying the game and would recommend it, if basing that recommendation on gameplay alone.

GAME INSTRUCTIONS
I struggled to interpret the instructions. I found understanding the expectations for playing, combined with the theme-specific language used, incredibly frustrating, and had I not been compelled to playtest, I would've easily passed on playing (glad I didn't, because I like the game, it plays well). I thought the guidance at the start of the digital version of the game would be better, but it wasn't; it presented the same confusing language and disorderly explanation as the rulebook. For example, Midnight cards are described as "the thing in the works" instead of something as simple as stating how it intends to function, or its purpose as being the obstacle. A lot of language was introduced early with no explanation as to what it meant in the context of the game; this was the main cause of my frustration and confusion. Even simpler subtitles would help that clearly state intent, like "What night demands" vs "Win/Loss Conditions" or "The Shape of a Round" vs "Actions Taken Each Round" or "Setting the Scene" vs "Setup" - Much of the instructions reads like someone already familiar with the game.

POINTS OF CONFUSION 😖
Contradictory losing conditions between documents. The rulebook states only one losing condition, clearly: losing on the 4th strike. The player-aid card, however, introduces a second losing condition involving the deck running out combined with a round passing with no repair made. This second condition is never mentioned or explained anywhere in the main rulebook, so I couldn't tell which document was correct, or whether I was missing a rule entirely.

Unclear carry-over of the Tension token into the Safety Catch. The rule for whether the token's current state (rather than a fresh/reset state) is what applies the moment Hour 3 is repaired is technically stated in the rulebook, but it's buried inside a sentence about something else and never called out as its own rule. This made it easy to miss and left me unsure whether I needed to reset or re-earn the token's state right at the moment Hour 3 became fixed.

CONSIDERATIONS/SUGGESTIONS
Much of my confusion came from theme-first language introduced before its mechanical function was ever explained. References like "the thing in the works" but told me nothing in the way I should consider it as part of the game. I'd suggest leading every new concept with a plain, functional definition first, and reserving the flavor language later (ex. introduce concept, define/explain its function or purpose in the context of gameplay, and lastly, reiterate its significance or relevancy). This alone would resolve most of my early frustration.

Regarding the two points of confusion: the rulebook and player-aid should be reconciled so they state the same losing conditions, since right now they contradict each other with no acknowledgment. And the Tension token's carry-over behavior into the Safety Catch deserves its own standalone callout — even a single bolded sentence — rather than being implied through a subordinate clause in an unrelated rule.