Doomrocket Debut on TTS: When One Skaven Shot Costs 300 Points
We had one of those tiny hobby-news moments that instantly turns into a full story.
Michał dropped into chat with a very Skaven-sounding discovery: Doomrocket, a new rule/weapon option apparently pulled in from Total War, available to a Warlock in r2.0. On paper, it already sounded like exactly the kind of thing Skaven players would love and everyone else would fear for at least a few minutes.

The basic pitch was beautiful in that classic Skaven way:
- 35 points
- one shot per game
- 36” range
- large template
- D3+1 Strength 10 hits in the center
So yes, naturally, our first reaction was basically: that sounds hilarious.
But this is Skaven, so of course there is a catch. Actually, there is a very Skaven catch: Skaven Misfire.

And the misfire results are exactly the sort of thing that make these weapons memorable:
- on a 1: everything explodes in a 3” radius
- on 2–5: the rocket fires off in a random direction
So even before seeing it happen, we already knew this was not going to be a boring story. It was either going to be devastating, embarrassing, or both.
That same day there was a Tabletop Simulator event, and they were allowing r2.0 content. Which meant, naturally, someone brought the Doomrocket.
And then Skaven science did what Skaven science does best.
The Skaven player’s Doomrocket shot ended up costing almost 300 points.

We love this kind of moment because it captures the whole charm of the faction in one go. The weapon sounds absurdly dangerous, the upside is real, the downside is catastrophic, and somehow that makes it even more appealing. It is hard to imagine a more Skaven tournament anecdote than a one-use wonder weapon immediately turning into a disaster big enough to swing hundreds of points.
Honestly, this is exactly why event stories from TTS and experimental rulesets are so fun to follow. Somebody sees a spicy new option, somebody else actually puts it on the table, and then the dice write the punchline.
If Doomrocket is going to keep appearing in r2.0 events, we are absolutely here for more reports. Preferably from a safe distance.