{"id":15290,"date":"2025-12-03T17:41:55","date_gmt":"2025-12-03T21:41:55","guid":{"rendered":"https:\/\/rmu.andrewyames.com\/?p=15290"},"modified":"2025-12-04T08:37:22","modified_gmt":"2025-12-04T12:37:22","slug":"final-thoughts-about-reactor-21","status":"publish","type":"post","link":"https:\/\/rmu.andrewyames.com\/?p=15290","title":{"rendered":"Final Thoughts About Reactor 21"},"content":{"rendered":"\n<p>Reactor 21 changed quite a bit as I tested different versions of it. The basic idea was always there\u2014two players trying to keep a failing reactor stable\u2014but it took some back-and-forth to figure out what actually made the game interesting. Early versions had the right intention, but some of the mechanics didn\u2019t create the amount of teamwork or pressure I wanted. The game felt like it needed a bit more structure around how instability spreads, what happens during a meltdown, and how the players recover from setbacks.<\/p>\n\n\n\n<p>Most of the improvements came from simply seeing how people reacted to certain moments in the game. Some rules felt too loose, and others were a little unclear in how they resolved. Adding the Nuclear Waste pile, tightening the meltdown rules, and clarifying how cards move between piles helped everything feel more intentional. The goal was always to keep the experience focused on communication and shared decision-making, and those adjustments moved the game in that direction.<\/p>\n\n\n\n<p>During all of this, ChatGPT was helpful for keeping things organized. Any time I adjusted a rule or tried a different way of handling a reactor event, I used ChatGPT to help rewrite the sections cleanly, make sure the terminology stayed consistent, and compare versions so nothing got lost. It also made it easier to step back and look at each revision as a whole instead of just patching small pieces. The mechanics themselves still came from testing and intuition, but having a tool to structure everything made the development process a lot smoother.<\/p>\n\n\n\n<p>Reactor 21 ended up feeling more balanced and readable because of that steady cycle of testing, revising, and tightening the language around the rules.<\/p>\n\n\n\n<p>The three acts of the game are as follows:<\/p>\n\n\n\n<p>Act 1 &#8211; Getting your footing<\/p>\n\n\n\n<p>The game starts off pretty gentle. You\u2019re drawing cards, placing them where they fit, and getting a feel for how the reactors behave. Most cards go somewhere without much trouble, and the token tracks are empty, so nothing feels dangerous yet. This is where you learn the rhythm: keep totals tight, stabilize when you can, don\u2019t waste options.<\/p>\n\n\n\n<p>Act II &#8211; Things start heating up<\/p>\n\n\n\n<p>Now the reactors are filling up, and suddenly every card matters. A placement that was easy earlier now feels risky. You\u2019re choosing between Instability and Meltdown more often, and both choices actually hurt. The Nuclear Waste Pile kicks in and you start to feel the deck thinning out. This is where the team talks things through, plans moves, and tries to stay one step ahead of the system.<\/p>\n\n\n\n<p>Act III &#8211; Hold it all together<\/p>\n\n\n\n<p>By the end, everything\u2019s tense. One bad draw can end the whole run, and every card feels like it might be the last piece you need\u2014or the thing that breaks the grid. You\u2019re trying to lock down those last stabilizations before either track fills up. When the final reactor hits 21, it feels earned; if the system blows, it\u2019s usually by a hair.<\/p>\n\n\n\n<p>(Final thought created with the assistance of AI, using my input)<\/p>\n\n\n\n<p><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Reactor 21 changed quite a bit as I tested different versions of it. The basic idea was always there\u2014two players trying to keep a failing reactor stable\u2014but it took some back-and-forth to figure out what actually made the game interesting. Early versions had the right intention, but some of the mechanics didn\u2019t create the amount &hellip; <\/p>\n<p class=\"link-more\"><a href=\"https:\/\/rmu.andrewyames.com\/?p=15290\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Final Thoughts About Reactor 21&#8221;<\/span><\/a><\/p>\n","protected":false},"author":298,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[47,150],"tags":[154,139],"class_list":["post-15290","post","type-post","status-publish","format-standard","hentry","category-game-design","category-prototype","tag-documentation","tag-marked"],"_links":{"self":[{"href":"https:\/\/rmu.andrewyames.com\/index.php?rest_route=\/wp\/v2\/posts\/15290","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/rmu.andrewyames.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rmu.andrewyames.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rmu.andrewyames.com\/index.php?rest_route=\/wp\/v2\/users\/298"}],"replies":[{"embeddable":true,"href":"https:\/\/rmu.andrewyames.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=15290"}],"version-history":[{"count":3,"href":"https:\/\/rmu.andrewyames.com\/index.php?rest_route=\/wp\/v2\/posts\/15290\/revisions"}],"predecessor-version":[{"id":15307,"href":"https:\/\/rmu.andrewyames.com\/index.php?rest_route=\/wp\/v2\/posts\/15290\/revisions\/15307"}],"wp:attachment":[{"href":"https:\/\/rmu.andrewyames.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=15290"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rmu.andrewyames.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=15290"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rmu.andrewyames.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=15290"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}