A printable Gloomhaven attack log lives or dies on the one claim nobody can prove from a finished scenario, because the whole game runs on one record nobody keeps: the order in which each attack was resolved, which modifier card was drawn, and how much shield was left standing when the damage finally landed. The scenario ended with Rowan's party clearing the room, and by the time the table argues about it nobody agrees on whether Rowan's attack really did 3 damage or 5, whether the guard's shield really counted before or after the modifier card, or whether the guard really survived with hit points left at all. A log sheet that records each attack's base value, each modifier applied, the modifier card drawn, and the shield subtracted, in that order, is the only record that settles those arguments, and it is a record no one at the table is keeping, because the players are busy choosing two cards and tracking initiative at once, the monsters are busy activating in standee order turn after turn, and the scenario is busy ending the instant the last monster falls.
Gloomhaven, for the seller who has never played it: a cooperative dungeon-crawling card game in which each character plays two ability cards per turn, resolving the top action of one and the bottom action of the other, in initiative order from lowest to highest. An Attack X ability deals a base X damage to an enemy within range and line of sight, and every attack is resolved in the same fixed order, which is where the arguments start: first the attacker's own modifiers are applied, then one attack modifier card is drawn from the attacker's deck and applied, and only last are the defender's defensive bonuses, such as shield, subtracted. Shield reduces damage from attacks only, and a monster whose hit points reach zero is immediately defeated and removed from the board, which is why the order matters so much: the same base attack can kill, wound, or bounce off entirely depending on what was drawn and what shield was standing.
The log your buyer actually needs has one row per attack, not one total per scenario, because Gloomhaven arguments are always about a single attack's order. Each row records the base attack value, the attacker's modifiers, the modifier card drawn, the defender's shield, the final damage dealt, and the monster's hit points before and after. The modifier-card column gets its own space, because the drawn card is the step players misremember: it is applied after the attacker's bonuses but before the shield, so a plus card inflates the total before the shield eats it, not after. The shield column gets its own space as well, because shield is subtracted last, and a log that shows only the final damage will restart the argument instead of settling it.
Here is the worked attack the log is built to settle, with every number checked. Rowan plays an Attack 3 against a guard with shield 2, and the guard has 6 hit points left. Rowan's active bonus adds 1, taking the attack from 3 to 4. Rowan then draws a +1 attack modifier card, taking it from 4 to 5. Only now does the guard's shield 2 apply, taking the damage from 5 down to 3, and 6 minus 3 leaves the guard on 3 hit points, alive. Without the log, that single attack is two arguments at once: whether the damage really was 3 rather than 5, the total if the shield had been ignored, and whether the guard really survived at all. With the log, it is one row. Note the knife edge the log protects: had Rowan drawn a -1 modifier card instead of +1, the attack would have run 3 plus 1 minus 1 minus 2, dealing just 1 damage and leaving the guard on 5 hit points; and had the shield been subtracted before the modifier card, the table would have argued the order instead of the outcome, which is exactly why the log records the steps in resolution order and not just the numbers.
For the seller, the pitch writes itself, because the buyer is not buying a scoresheet, they are buying the end of the argument. A Gloomhaven group argues about exactly this kind of attack every scenario, and the game is famous for modifier cards that quietly change a kill into a scratch while both players watch the monster's hit points, which means the log gets used, argued over, and used again, which means the buyer comes back. Sell it as a pad of fifty, one full scenario per sheet with a row per attack and the resolution order pre-printed at the top, so nobody has to remember mid-game whether shield comes before or after the modifier card. Price it like a campaign accessory, not like a board game, and show the worked attack above on the listing images so a buyer sees in five seconds exactly which argument the sheet settles. The game has a loud, loyal campaign audience, so the listing should speak to the group that just lost a scenario to a disputed shield, not to the collector.
This log is an unofficial fan-made accessory. It is not affiliated with, endorsed by, or connected to the publisher, and Gloomhaven is a trademark of its respective owner.
Top comments (0)