Applyterra is in public betaRules still move and games may break. You are playing v107.
It's Always DNS
› bugS2 major
2 GOODIES · +1 LVL
+4 vs SRE. TTL 3600. Eight-minute incident. The maths, however, are perfect. +4 vs SRE.
SIDE EFFECT NXDOMAIN on your ego. -1 level. The cache, though, is warm.
You checked everything. Except DNS. It was DNS. It's always DNS. Write it down. You'll forget.
6SP2+1
BUG
It's Always DNS
Bug · play it on your turn
The bug's story points6 SP
“
You checked everything. Except DNS. It was DNS. It's always DNS. Write it down. You'll forget.
On the card
TTL 3600. Eight-minute incident. The maths, however, are perfect. +4 vs SRE.
DomainGlitchPileTicketsVersus+4 vs SRELoot2 goodies · +1 level
How it plays
01
When
Drawn face up → the debug starts at once. From your hand: you can play it on your turn.
02
Story points
6 SP. Your velocity must be strictly higher. A tie means the bug wins.
03
Win
2 goodies and +1 level. A pair takes 1 goodie, you take the rest and the levels.
04
Reassign
Roll 1–6, you need 5 or more (shifted by your gear / role / profile, minimum 2). Refused = the ticket comes back to you and you take the hit.
05
Versus
+4 vs SRE — added to ITS story points.
SIDE EFFECTNXDOMAIN on your ego. -1 level. The cache, though, is warm.
What it's really about
The situation
Eight minutes of incident, three hours of post-mortem. The cause is three letters long, and everybody said them in the first minute, laughing, not believing it. The TTL was 3600.
Why those numbers
Six story points, two goodies, and +4 against the SRE role: the card punishes precisely the people who should have seen it coming. The side effect costs a level, roughly the going rate for a public incident.
How to play it
An average bug for everyone, a wall for an SRE. It is the one card in the deck where switching roles before drawing would be rational.
Bugs
What you pull from the Tickets pile. Your velocity has to land strictly above their story points — and your friends will inflate them.