In partnership with
Designing games. Reviewing new games. Browsing games in Micro May.
Such have been my days of late.
But one new thing that got added to my days is witnessing the dawn of a new format of gaming.
Dynamic Print-and-Plays.
In a line, imagine your game sheet can be configured in a near-infinite number of ways. That’s awesome.
And I’ve got Jack and Robin, the founders of Pagepunk, to thank for that.
BYTE:SHIFT was my first taste of it, and I loved what it brought to the table. The configuration-meets-nostalgia-meets-drafting stuff really hit the right spot for me.
But more than the game itself, Jack and Robin’s little mission struck a chord:
One Dynamic PnP. Every month.
Because sure, the first one worked. It was fresh, it was different.
But what happens next?
How does the second one look?
Does it push things further?
And more importantly… can this actually hold up as a monthly thing?
Well… looks like I don’t have to wonder anymore!
Minomancer just landed in my hands. The second DPnP. Exactly a month after BYTE:SHIFT.
As promised!
Lo and behold- Minomancer!
And once again, we’ve got a fully configurable sheet.
This time, you’re invading the domain of a rival necromancer, raising skeletons, hunting for keys, dodging tricks, and trying not to become another nameless bone in someone else’s army. That sounds like fun!
Also, there’s a deck of cards involved.
And that always gets me a little extra excited. Some of my best print-and-play experiences have come from games that knew how to weave cards into the system, so I’m very curious to see if Minomancer follows that same path.
Two games in, and this whole Dynamic PnP thing is starting to feel a lot less like an experiment… and a lot more like something that’s here to stay.
Safe to say, I’m watching this closely. And so can you.
More on Minomancer soon!
- Tas.
We hired one colleague for every department.
Last Tuesday, marketing asked Viktor to write the weekly campaign recap, pull performance from Google Ads and Meta, and format it as a PDF for the exec team. Done in four minutes.
That same afternoon, engineering asked Viktor to review three open pull requests on GitHub, cross-reference with the Linear sprint board, and flag anything blocking the release. Posted to private channel before standup.
At 9pm, ops asked Viktor to draft a vendor contract summary from three Notion docs and send it to the team. It was in #ops by morning.
None of them knew the others were using it.
Same colleague. Three departments. That's what changes when your AI coworker lives in Slack, where your whole company already works. It's not a tool one person logs into. It's a teammate everyone messages.
5,700+ teams. SOC 2 certified. Your data never trains models.
"Viktor is now an integral team member, and after weeks of use we still feel we haven't uncovered the full potential." - Patrick O'Doherty, Director, Yarra Web
