Tag: Game Design Brain Dump

Game Design Brain Dump: September 4, 2026

Published on by KyraLeave a comment

Hey, hey, Geekly Gang! Kyra Kyle with another board game design brain dump. I’m still submitting designs to various publishers. I’ve received a couple of rejections. Brotherwise Games gave me a prompt response. I’ve given up on a handful of publishers (like Lucky Duck Games), marking them down as “never responded” in my spreadsheet. Seriously, I wish there was a submission tracker like Duotrope for board games, so designers could share notes on which publishers are more responsive than others. I guess I can do that here. While I don’t particularly care for Brotherwise Games’ submission manager (they use Google Forms and pics), I do like how prompt they were with a response. And that’s another thing the board game community could use, a more standardized online submission manager program like Submittable.

Anyway, I’ve made tweaks to Spill the Beans. My goal is making Spill the Beans more enjoyable at lower player counts, and I think I’ve accomplished this by having players “bust” if they spill too many of the same bean type. Love it! Spill the Beans is still a party game at its core, but I’ve playtested multiple smaller player count games at designer meet-ups and received good feedback. You would think a player may get lucky, pushing their luck by spilling out more beans and not busting, and that does occur, but the game evens out over time. And smaller player count games take little time at all. Spilling out more beans per turn means that the game concludes a lot faster at smaller player counts (a problem the game had before this change). Players are just as likely to run out of beans as they are to fill two jars.

Enough about Spill the Beans, I’ve also been submitting Whirligig Pets to various publishers. I’ve had fewer responses for Whirligig Pets than Spill the Beans. I may be submitting to the wrong publishers. Or I may need to submit games during conventions. Or it could be something else entirely. Again, board games need a submission tracker and submission manager program like Duotrope and Submittable.

Monster Chef 01 Board Game Logo

I wrote the Monster Chef rulebook. It’s up for review with multiple design groups. I’m getting close to submission with this title. I can’t wait. Monster Chef has plenty of theme and could tie in well with the upcoming season of Delicious in Dungeon (2027). I’m also exploring expansions for this title. Monster Chef is a joy to develop.

The same isn’t always true of Rustbucket Riots. I’m still playtesting this game’s shift from dice placement to bag builder. I like what I’ve seen so far, but balance has become an issue. If I can unknot Rustbucket Riots’ balancing issues, it could proceed to a similar state to Monster Chef.

Mechanisms

And we come to two newer designs that don’t even have names–yet–and I may want to help a fellow game designer get one of their title’s published. I won’t name her design here, but I love the game’s quilting theme. One of my new titles doesn’t have a theme. Well, I don’t care for the theme of flowers that it currently has. Too many games use a flower theme, so I may need to shake up a few things. My second title is fallout shelter game includes multi-use tetrominoes and spinners. Oh, yeah. We’re gonna get freaky.

That second title has been on the backburner for over a year. I wanted to get Spill the Beans, Whirligig Pets, and Monster Chef to good states before starting another project. I can’t wait to take the fallout shelter game to conventions. Woo hoo!

That’s all I’ve been working on over the past month. I should have more updates next month. Nuke-Con (in Omaha) is on the horizon. I’ll be attending with Spielmasons. If you’re going, stop by and say hi. Thank for reading, and wherever you are, I hope you’re having a great day.

Game Design Brain Dump: August 7, 2026

Published on by Kyra2 Comments

Hey, hey, Geekly Gang! Kyra Kyle here with another board game design brain dump. This month’s game design dump will mostly be a status update with a tip of the hat to a new productivity tool: a dry-erase calendar. I know. I know. Dry-erase calendars are old news, old tech, but it worked wonders.

New Calendar

The calendar proved necessary because I had become trapped with the idea that everything for Geekly, this blog, was easier and faster than anything else I could do for my career (both board game design and writing). The calendar has spots for weekly items, and I do use these for quite a few things, like my weekly menu (I cook for my household) and other events that occur on specific days of the week (like game design meetups and write-ins, both great resources for game designers and writers).

But the “To Do” section has given me the most focus. I write down the six to seven most important tasks and mark the two quickest/easiest tasks to accomplish first. This keeps me on task. Geekly projects don’t always top the list for quickest or easiest tasks, and I find myself finishing most projects. I do have one item listed for a specific day because that day will be the best time to attempt the project. Overall, this new calendar has streamlined my creative process. I’ve mentioned this in various posts (specifically my Autism Representation Deep Dive series), but I’m neurodivergent. The calendar limits my number of choices. So often, I’ll become paralyzed and continue with what I was working on before, which, for a time, was nothing but Geekly content. This visual reminds me of other goals and gives me a handful of options.

I’ve gushed about my new calendar for long enough. Let’s get to the game updates for this month.

Monster Chef 01 Board Game Logo

Monster Chef works as a hand management game. I’ve playtested it numerous times over the past month. The new butcher knife ability works well. I noticed the decks running out of cards far quicker than before, and added back in one extra copy of the Groceries cards for each monster. I’ve seen multiple playthroughs where gamers complained that they didn’t see enough of the Grocery card abilities. This solves both potential issues.

Monster Chef also plays at a tight thirty minutes or so. I’m happy with that approximate play time. Now, all I need to do is playtest Monster Chef at various designer meetups and conventions. Nuke-Con (in Omaha, Nebraska) won’t occur until early October. I’ll definitely have a playtest or two or three of Monster Chef planned for that convention. I’ll keep you posted if I attend any other public events before Nuke-Con.

After codifying the game’s ruleset, one of the goals I have set for myself is finishing Monster Chef’s rulebook. Oh, yeah. I see some blind playtests in the near future.

I knew Rustbucket Riots would prove more difficult to complete. It is. But I’ve made plenty of progress. Rustbucket Riots works as a bag building game. Yay! Two major issues cropped up: minions added to player bags is brutal, and gamers felt weaker than they did when the game was strictly dice-rolling (with the lock a result mechanism). Both problems were easily fixed. I lowered the number of minions added by boss robots each turn. Done. That was easy. Making the players feel more powerful was a little difficult to pinpoint, but I’m tackling the issue in two ways. First, increase the number of tokens players grab from their bags each turn. This was easy enough. But drawing fewer tokens was only part of the problem.

When players could reroll dice (dice rolling mechanism), Rustbucket Riots players had more control over their results. Do you really need to roll a Jump result? Reroll any dice that don’t show Jump until you lock in every result. Pulling from a bag is a little trickier. The tokens you pull are the tokens you pull. So, I added a mechanism that allows players to trade in any two tokens for a token of their choice. You’ll need to pull more tokens from your bag, but as I mentioned, players will be pulling more tokens from their bags.

I’m excited by the direction Rustbucket Riots is taking. Now comes the long road of balancing the mechanisms so most games conclude with a tight outcome. Fingers crossed.

That’s all I have for this month’s game design brain dump. Thank you for reading, and wherever you are, I hope you’re having a great day.

Game Design Brain Dump: July 3, 2026

Published on by KyraLeave a comment

Happy Friday, Geekly Gang! Kyra Kyle here with another board game design brain dump. I’ll be honest. This past month, most of my focus has been on writing my personal fiction, blogs, and tabletop RPG. I haven’t even had a chance to playtest the changes I made (to Monster Chef) during the previous game design brain dump. Today’s game design brain dump will center on Rustbucket Riots. Ah! Rustbucket Riots has seen plenty of changes throughout the year and a half I’ve been developing the game. And it looks like Rustbucket Riots could see another change in the near future. Let’s talk about it in today’s Board Game Design Brain Dump.

I’ve already made changes to Rustbucket Riots. For those of you who didn’t check the previous link, the above image is what the Rustbucket Riots game board used to look like. This was the board for a good many months–years–until I had it upgraded. I’ll share that picture in a bit, but gaining some space gives anyone perspective.

For the months I haven’t been working on Rustbucket Riots, I’ve been working on Monster Chef. This gave me two things: cognitive distance from Rustbucket Riots, cross-pollination of ideas with Monster Chef. Rustbucket Riots and Monster Chef are nothing alike. One is a cooperative, dice placement game with interlocking gears (Rustbucket Riots), while the other is a competitive, card management game with a cook timing mechanism (Monster Chef). But working on Monster Chef, figuring out how to make that game easier to teach and faster to play made me view Rustbucket Riots in a new light. I needed to look at Rustbucket Riots through the same lens as Monster Chef.

Ah. The board above is beautiful. I forgot how pretty Rustbucket Riots’ current board is, and it’s functional. The board illustrates which region a die belongs. Whatever color the die rests is the region it belongs to, so a die placed in the yellow wedge (of the large gear) will touch the orange and yellow regions. Easy! Before this change, playtesters would complain it was too difficult to tell. I haven’t received that feedback as much after this change. So, it might be time for more change. Players are supposed to simultaneously roll dice, lock them in, place them, and remove the dice from the gear spaces to use the die.

That’s a lot of mechanical things going on at once. The rolling, locking, and placing can get long and difficult to explain. The change I’m thinking of making is replacing dice with tokens, converting Rustbucket Riots from dice placement to a bag builder game. If I do this, this will fundamentally change the game. I won’t change the board, at least not right away. If I go through with this, I’ll make the tokens die-shaped. No. I’m concerned about how this change will affect Rustbucket Riots’ flow. I’ll need to rebalance the game. Some boss robots may need new abilities (many of their current abilities revolve around dice manipulation). And how does busting work in this new setup?

I don’t know. I guess this post lives up to its title of a game design brain dump, emphasis on the brain dump. In the coming weeks, I’ll playtest the current version of Rustbucket Riots and see where these changes could be implemented. Thankfully, I won’t need to change any of Rustbucket Riots’ major set pieces. I can produce die-shaped tokens and alternate cards. We can play the game both ways. See which one flows best. My guess will be the tokens. I’ve spent so much time explaining how die rolling and locking die faces work. Explaining that you just pull out X number of tokens will be a relief. And I could see minions (the orange and pink dice) finding their way into player bags. Perhaps that’s the bust trigger.

Thank you for reading this week’s game design brain dump. You’re awesome. And wherever you are, I hope you’re having a great day.

Game Design Brain Dump: June 5, 2026

Published on by KyraLeave a comment

Happy Friday, Geekly Gang! Kyra Kyle here with another board game design brain dump. I’m trying to get back on track with these, and since I’m rusty at writing a game design brain dump, I’ll be jumping topics a bit with today’s post. We’ll begin with Monster Chef. Yes! I’ve kicked around Dungeon Chef and Dungeon Gourmet for this card game, but I Monster Chef fits. Plus, I love this simple logo for Monster Chef.

So Cute! Anyway, several game design brain dumps ago, I mentioned a card-drafting game based on the anime, Delicious in Dungeon. Monster Chef is that game. I just cut the card-drafting aspect of the game, and that led me to board game development. If board game design is like writing a story, board game development is editing that story. So, today’s game design brain dump leans into a very important aspect of design: development.

Sure, some people make a living editing and don’t write as much original material. The same can be said of board game developers. Plenty of developers can make a living (or at least some extra spending cash) by developing other designers’ work. But like writing, a board game’s first developer will be its designer. No matter how much I’d love to hand off Monster Chef to a developer and move on to my next game, I need to find a happy place for Monster Chef. And like writing, often game designers need to “kill their darlings.”

I love card-drafting games. Heck, Monster Chef began as Food Court Hustle, which had an interesting–to me at least–twist of dual-purpose cards. Players would play a card for one effect and discard a different card for another effect, before passing their hands to the next player. With Monster Chef, I took the concept further by allowing players to draw cards into the hands they inherited from other players, giving players more control over the chaos caused by card-drafting. Despite all these factors to “solve” my perceived problem with the card-drafting games, I learned card-drafting was holding back Monster Chef. Card-drafting breeds upheaval. Monster Chef needed stability.

The game wanted to use hand management (players don’t change hands and keep the ones they have dealt to them) instead of card-drafting (in this case, closed card-drafting). Players would often forget to pass their hands after their turns. The physical act of drafting cards meant that players couldn’t preplan their following turns, which slowed gameplay. Some of the choices felt as if they lacked consequences because you didn’t know what your hand would eventually look like, so one wouldn’t care what remained in their hands. And Monster Chef had plenty of other random elements (like not knowing which recipes would get drawn for the display). Hand management affords more control.

With hand management, I added card draw to the Monster Chef’s design space. The game has a faster run time. Players can cycle through the draw decks (dungeon floors) more quickly. And I was able to get rid of the cards few players used, except in edge cases. I may have eliminated most edge cases, which are mechanisms that either have limited viability or can only be used in specific situations. All of Monster Chef’s main actions have obvious usefulness. It depends on how and when players use these actions. That makes for a better game.

I’ll definitely come up with a card-drafting game in the future. I love these types of games. But I must “kill that darling.” Doing so made Monster Chef a better game.

Here’s where I bounce. I’m giving a brief update on the Marvel Multiverse Role-Playing Game module I’m writing for Comic-Con: Nebraska (CCN). I didn’t need to create my own module. Just trying out a few things. Running the Marvel Multiverse Role-Playing Game at last month’s Aftershock event got me thinking that the game could be geared for true RPG beginners. Some of my players had never played a tabletop role-playing game before, or they had played once or twice. While the Marvel Rivals Timestream Adventure is great for a one-shot to introduce new players to the Marvel Multiverse Role-Playing Game, it could do more to welcome truly new role-playing game players.

I was reminded of Legend of the Five Rings. When I ran a game for younger players (who had never played an RPG before) with that game, I resurrected the Rokugan Tournaments (like an Olympic Games for samurai) mentioned in the game’s lore. I had players participate in non-combat events, learning how checks worked in a pseudo-video game tutorial manner, and of course, something fishy was going on with the tournament. Once players discovered the threat, a battle occurred, but this only happened after players knew their characters and how the game worked. I want to do the same for the Marvel Multiverse Role-Playing Game.

So, I chose Mojo and his Mojoverse. X-Men ’97 Season Two will begin releasing soon, so gamers may be familiar with Mojo by the middle of August (in time for CCN). Players will participate in Mojo’s reality TV show-like events (similar to the Legend of the Five Rings tournament), and I can tailor the game to a two-hour window. Perfect for a Comic-Con. If I get players for the Marvel Multiverse Role-Playing Game at CCN, most likely, they will have limited (if any) experience with tabletop role-playing games. Who knows? A quick session with a tutorial may get more potential players interested in the game.

I’ll keep you updated on my progress. Hopefully, I will have finished the module before CCN. I’ll also be working for Extra Life, so if you’re in the area, stop by and say hello.

That’s all I have for today’s game design brain dump. Thank you for reading, and wherever you are, I hope you’re having a great day.

Game Design Brain Dump: April 3, 2026

Published on by KyraLeave a comment

Hey, hey, Geekly Gang! Kyra Kyle here. I’m just checking because this is when I would typically post a board game design brain dump. I’m skipping this week, but I have a good reason. This week (and next week) are crunch time for my board board game designs. I’ll be submitting them to Great Plains Game Festival’s (GPGF) Playtest to Win event. So, if you’re in the Lincoln, Nebraska area and you’re attending GPGF, you can play Spill the Beans, No Kings, and Whirligig Pets.

I may or may not post a game design brain dump next week either, as I will be attending GPGF. If you’re attending stop by and say, hi.

Game Design Brain Dump: March 6, 2026

Published on by KyraLeave a comment

Hey, hey, Geekly Gang! Kyra Kyle here with another brain dump. Today’s post will be about board game design, but these brain dumps have a nasty habit of crossing over from writing to game design and back again. I may have found my stride. We’re averaging a brain dump (alternating between game design and writing) every other week. That feels good, so the next writing brain dump should occur on March 20, 2026. Yay! But let’s go to a macro look at game design. That’s right. We’re zooming out and potentially talking about the creative process as a whole.

I read another game designer’s (Ann Journey’s) game diary. She likened her design technique to her writing process, and it rang true. There’s a lot of crossover between game design and writing as both are creative endeavors. She would brainstorm, create an outline, and build her board game based on the outline. This resembles the Plotter approach to writing. Plotters are at one extreme end of the writing spectrum.

Yes. Like most things in life, writing can be depicted as a spectrum. In fact, the opposite extreme ends of the writing spectrum tend to get as hotly debated as political factions. When I say Plotters are at one end of the writing spectrum, we’re talking Ultra Conservative or Wacky Liberal levels of extreme. Plotters like JK Rowling insist that writing without an outline would be like taking a trip without a map. You’ll get lost. That makes sense. Pantsers are at the other end of the spectrum. They never use outlines. Stephen King may be the most famous Pantser. King wrote in On Writing, “Outlines are the last resource of bad fiction writers.” King suggests outlines limit inspiration and the joy of creativity. This also makes sense.

And like most things (like gender identity and sexual orientation), I fall somewhere in the middle. Pantsing and Plotting aren’t the only ways to write or design games. They’re the ones that get all the attention.

I’m somewhere in the purple. I like purple. Yay! We discussed how Plotting works within board game design. Ann Journey uses this method to great effect in Cretaceous Rails. Brainstorm, create an outline, and build a game based on the outline. Euro Games may insist on this method of board game design. Euros lend themselves to following a well-crafted outline and often feature distinct beginnings, middles, and ends.

But you could Pants your way to a good game. In the past, Molly Johnson, Robert Melvin, and Shawn Stankewich shared that they threw various ideas at the wall while designing Point Salad. If it’s cool, it rules, and if it rules, it makes it into the rulebook. That sounds akin to Pantsing. The Point Salad series of games (which also includes Point City and Point Galaxy) tends to be adaptable and demands that players remain flexible. This could be a feature of this method of board game design. I’m just throwing something against the wall here.

Then we get to two alternatives to Pantsing and Plotting: Lighthousing and Blotting. Are these two methods in the purple, or is there a Y-axis to this spectrum that I don’t see? I’m unsure, but I do know that Lighthousing and Blotting are two major alternatives to Pantsing and Plotting. There may be others.

While writing, whenever I Lighthouse, I usually know where my story begins (the opening scene), and I know a Lighthouse scene for the future, a poignant scene I know will make the final story, but I don’t know how to get there yet. This Lighthouse scene informs my decisions, but it also gives me leeway to explore. Early into Mysterium’s development, Oleksandr Nevskiy and Oleg Sidorenko knew how the game would begin and the game’s final turn. Most–if not all–of Mysterium’s design choices were in service of the game flowing from its beginning to that final turn. Lighthousing may be the method you’ll want to use if you have planned an epic final turn or series of turns.

Finally, we get to Blotting. I picture myself with a blank canvas whenever I Blot while writing. In my hand, I have a sopping wet paintbrush, like Bob Ross and his wet-on-wet painting method. I slap a scene on the blank canvas, and it causes a blot. Then I add another and another, and after I’m finished, I have to make sense of the mess by molding these Blots into a cohesive whole. While designing Marvel United, Eric Lang suggested that he knew his theme (Marvel Comics, obviously) and a handful of the game’s mechanisms. He just needed to take those elements and sculpt them into a cohesive gaming experience. Sounds like Blotting to me. Blotting can lead to fun and exciting fusions of disparate elements.

Word of caution for Blotting (and for designing games in general): One can add too many elements to a game. Typically, the fewer gaming elements, the better. The old adage “Less is More” is key.

I’ve used all of these methods for game design and writing. There are some I prefer and others I don’t. I wouldn’t say one method for a creative endeavor always trumps another. Your goal is to find which method works best for you and for your project.

And just because you Pants or Lighthouse your way to a story or game, doesn’t mean you can’t use a reverse outline. Have I talked about reverse outlines? Yes, in a previous writing brain dump. I’ll leave that link right here.

Remember, Stephen King subscribes to Pantsing. He has suggested that one’s reader won’t be surprised if you’re not surprised as the writer. Pantsing induces moments of surprise in King whenever he writes. But King is also known for horror fiction. The element of surprise is important for horror stories. There may be a reason Stephen King chooses the Pantsing method.

If you’ve made it through my rambling, you’re awesome. We all know it. Thank you for reading, and wherever you are, I hope you’re having a great day.

Game Design Brain Dump: January 30, 2026

Published on by KyraLeave a comment

Happy Friday, Geekly Gang! Today may be the first month where I had two game design brain dumps. Let’s keep the streak going. Yay! Thanks to everyone reading. You’re awesome. We all know it. The past couple of weeks were eventful for a couple of my board game designs. I’ll save Rustbucket Riots’ updates for a future game design brain dump. Instead, let’s discuss the changes for Spill the Beans. I can sum up all the updates in two words: production considerations.

Originally, Spill the Beans featured double-sided jelly bean tokens where most beans had different bean types on both sides. Players would pick beans from their supply, add them to the bean jar, shake beans from the jar, and shed cards from their hands. The game was dumb fun.

Despite being a card-shedding game (like Uno) with extra steps, Spill the Beans worked well. But I thought of how the game worked. I marketed Spill the Beans as a party game. Party games usually accommodate at least six players should be able to play the game, and if I include enough cards for six players, I would’ve needed 120 cards. That’s a lot of cards for a party game. It could work if Spill the Beans only included cards. But I intend on having jelly bean tokens. The card-shedding mechanism also took away focus from the jelly beans. At first, this wasn’t that big of a deal. The jelly bean tokens were flat and circular with jelly beans printed on them. And then, I 3D printed the jelly beans.

The original game had too many cards, and I couldn’t have the cards upstage the cute jelly beans. So, I cut the game mechanisms that no longer worked and reduced Spill the Beans’ game components to the jelly bean tokens, the jar to shake them from, and five mason jar (point-value) cards. Players still shake the jar and try to get so many beans from the jar. Then, they place at least one bean on one of the jar cards and eat the rest (add them to their score pile). As soon as three of the five mason jar cards are filled, play ends. Whichever bean has area majority in each mason jar card, claims that jar’s point value. Then, players score their “eaten” jelly beans. Whoever has the most points wins.

This new ruleset is simple. It puts emphasis on the jelly beans, not card shedding. And the new Spill the Beans scales well at higher player counts. Perfect for a “party game.” And the new game’s toy factor is through the roof. I can’t wait to codify the rules, pitch to publishers, and see Spill the Beans on shelves. Yay!

That’s all I have for this week’s game design brain dump. If you’ve made it this far, you’re awesome. Thank you for reading, and wherever you are, I hope you’re having a great day.

Game Design Brain Dump: January 16, 2026

Published on by KyraLeave a comment

Happy Friday, Geekly Gang! Kyra Kyle here with another game design brain dump. Our first of the year. Yay! Recently, I watched Netflix’s Delicious in Dungeon. I even shared it during one of our Watcha Watching posts. And instantly, I had a new idea for a board game. Well, Dungeon Chef is a variant of an old game design idea I had years ago. Let’s dish. Great. Now, I’m hungry.

Above is an image of Food Court Hustle’s most recent iteration. Yes, Food Court Hustle was the game’s original name. Food Court Hustle was a card-drafting game where players manage restaurants in a food court. It played quickly, had plenty of Take That elements, and never took itself too seriously. I liked the concept and loved the name. But food courts are a little dated. That was the biggest complaint I heard from playtesters. The concept for Food Court Hustle’s game mechanisms was to give players more control during card drafting. Each round, players would choose one card to play (for its effect) and then choose a card to discard for its ingredients, only every player–not just you–gains the ingredient.

Like most card-drafting games, Food Court Hustle plays swiftly. Simultaneous play helps with game speed. Seriously. This was one of the few games I never felt the need to incessantly time. And that’s a good rule of thumb when designing games. Always time your games. You want to waste as little of your players’ time as possible. I’m not saying you can’t design a two-hour or longer epic board game, but the game should earn its play time. Getting back to Food Court Hustle, something beyond the theme was missing.

Tangent: the image above is Dungeon Chef’s player board, and the previous image was of a Food Court Hustle player board. The scale of these two images is almost what it should be, so I managed to shrink the player’s space while ditching customers. Yes. The original game included customer cards that wouldn’t always appear when players wanted to make a dish. Another gameplay gripe. You could have the ingredients and not be able to make a meal. Dungeon Chef gets rid of that layer of randomness. I also got rid of a lot of the Take That mechanisms and replaced them with global effects.

Above is a sample Dungeon Chef card. The top half is the action you may choose to play. The number indicates the player’s initiative for that turn. All cards in the three day decks are numbered 1-50. The higher the number, the quicker the action. I’ve seen players choose a card for its initiative, which is wild. The bottom half is the monster parts you may add to the communal ingredients. You wouldn’t be the only one gaining a man-eating plant. Everyone at the table gains a chunk of man-eating plant. And returning to the action on this card, you can turn up the temperature of the communal stove. That’s right. Most game elements in Dungeon Chef have global effects. Half the game is steering the game state in your direction.

Players can select a recipe by spending the ingredients on the recipe card. Then, they add the recipe to their player board, lining up the wok with the flame. And near the end of each turn, move the recipe card up the number of spaces indicated by the communal stove’s temperature. Players can take their active recipe off the stove and claim the victory points indicated on the card at any time. But beware, if a player leaves their meal on the stove too long, they could burn their meal, and it goes into the trash, costing them 10 points at the end of the game. Whoever has the most points at the end of three days wins. There’s little more to Dungeon Chef. I tried to keep it short, easy to understand, and stick to the Delicious in Dungeon theme as best I could.

We’ll see where this design goes. And who knows? Perhaps I’ll be at a gaming convention near you. Let me know which convention I should attend. If you made it this far, you’re awesome. We all know it. Thank you for reading, and wherever you are, I hope you’re having a great day.

Game Design Brain Dump: November 21, 2025

Published on by KyraLeave a comment

Happy Friday, Geekly Gang! Kyra Kyle here with another board game design brain dump. I’m taking a break from Rustbucket Riots—which I covered in last month’s brain dump–and discuss a Blackjack Deck Building game I originally made in 2018. Seven years! Yikes! Guess I got the seven-year itch. This Blackjack Deck Builder has gone through multiple minor rule modifications and name changes. The deck, based on a standard playing card deck, doesn’t have jacks and kings, so it’s had the name No Jack and No Kings.

Play Faster

My oldest daughter had a high school friend, who will remain nameless. We’ll call her C. C loved deck building games, but she wouldn’t draw her hand at the end of each turn (allowing her to plan her next turn), and every time she drew cards into her hand, she’d act like she was reading them for the first time. This frustrated my daughter and her friends. I thought of No Jack or No Kings to fix this issue.

A quick explanation of deck building card games: each player begins with the same (or at least similar) small decks and purchase cards from a supply to add to their decks, making each deck unique.

While many starter cards in a deck building game have limited text, cards one would add to their hands could contain a heap of text. This would cause C’s turns to last three minutes or more, as she read the more complicated cards that she added to her deck. So, I took out most text. Standard playing cards have little to no text. Next, C had the issue of not drawing her hand at the end of her turn. What standard card game doesn’t require a hand? Blackjack.

The above sample card (Page of Coins) is a prototype. The end product will hopefully look a lot better. Lol.

I merged deck building with Blackjack and came up with No Jack or No Kings, and it worked. With the exception of changing the suits, the only cards that look different from a deck of standard playing cards are the face cards. C knew how to play Blackjack. Players would draw cards from the top of their decks, following the standard rules for Blackjack. If you drew over 22 points of cards, you’d bust and lose your turn. If a face card remains in play (without busting) at the end of a turn, the player can move the face card to their tableau and gain its ability. In the case of the page above, every time that player draws a coin suit card, they gain one extra money to purchase other cards. No Jack/No Kings starter decks begin with one face card from one of the four suits. Each suit has a different power.

Trouble with Asymmetry

Most players in deck building games begin with the exact same cards. Choosing to go with asymmetric powers at the onset of this game, however slight, proves difficult to balance. Brushes allow players to cull cards from their discard. Deck building experts see this as overpowered. But Diamonds and Cups have better win percentages. Diamonds allow players to manipulate decks (take cards from a discard and placing them on the bottom). If you’re good at counting cards, you can induce more 21s (or Blackjacks). Cups let players discard a drawn card and draw a new one. This is also strong.

The first page I showed, the Page of Coins, is the weakest of all four. But perception matters. Even though I’ve playtested No Jack/No Kings hundreds of times and found Cups and Diamonds win more often than not, players still “feel” more powerful with Brushes and, to a lesser extent, Coins. Granted, one of my playtest weekends was with someone at a Protospiel. He played No Jack/No Kings throughout the entire weekend (like a few dozen times), hoping to sculpt a deck of only Tens and Aces. This gamer played Brushes in each game and lost every time. Winning didn’t factor into his enjoyment. He wanted to build a near-perfect deck. So, the numbers may be a little skewed.

Does anything need to be changed? Honestly, I don’t know.

How to Win at No Jack/No Kings

I just realized we discussed No Jack/No Kings mechanisms without sharing how to win. There’s a separate deck of Patrons. Every patron can be claimed with a Blackjack (21), but each patron also gives discounts to two suits. If you have a face card from either suit in your tableau and you reach the lower number, you can claim the patron. Every turn, you can either claim a patron or purchase cards from the supply. That’s how the gamer (Protospiel) lost so many times. He would purchase cards if they fit in his “perfect deck” instead of claiming a patron. The first player to claim six patrons wins.

No Theme and Simple Mechanisms

I don’t know why I shelved No Jack/No Kings for almost a decade. My best guess is that I wanted No Jack/No Kings to have more theme or more complexity. I no longer care if No Jack/No Kings has a theme, and any additional mechanisms I added to the game diluted the core gameplay. I was obsessed with everything No Jack/No Kings didn’t have and failed to see what it did have. That same Protospiel (seven years ago, I’m guessing), I only taught the game once. Other gamers taught No Jack/No Kings to the rest of the convention, and the game was played consistently for two and a half days. I need to get out of my own way. Ugh!

I’m finalizing the starter decks and the cost of cards. But there are shockingly few things to balance/tweak after I pin down the starter decks, so I’m left with one question. Which name do you like better, No Jack or No Kings?

Let me know in the comments. Thank you for reading, and wherever you are, I hope you’re having a great day.