I was in the middle of designing the construction contribution system when I caught myself doing the thing I specifically built Sol Fracta to prevent.<\/p>\n\n\n\n
Let me back up.<\/p>\n\n\n\n
Construction projects in Sol Fracta<\/a> run on EV: \u00c9nergie Vitale<\/a>, the game’s unified resource that functions as hit points, stamina, time, and narrative currency simultaneously. The colony sheet tracks EV per project. The loop is clean: cycles pass, EV accumulates or drains based on what the players do, buildings rise or collapse accordingly.<\/p>\n\n\n\n The question I was wrestling with: how do player characters actively contribute<\/em> to a construction project? Not passively \u2014 not just “your faction controls this building, so it progresses” \u2014 but actively<\/em>, with rolls, with stakes, with the feeling that what your character does during a cycle actually matters to the thing being built.<\/p>\n\n\n\n My first instinct was wrong in a very predictable way.<\/p>\n\n\n\n I started drafting something like: “The player declares how many EV they’re investing in the project this cycle. They allocate from their pool. Done.” Clean, transactional, simulationist. Also completely dead at the table. No tension. No decision. You’re not playing a character; you’re moving a resource from one box to another. Nobody signed up for spreadsheet management.<\/p>\n\n\n\n So I pivoted: “What if it’s a roll? The player makes a skill check. Success = EV added to the project. Failure = nothing, or partial contribution.”<\/p>\n\n\n\n Better, but immediately I hit something uncomfortable. The EV cost on a roll, the 1 EV that a consequence pulls from you, didn’t quite fit. If you’re contributing<\/em> EV to a project, and you also spend<\/em> EV as a consequence on the roll… what does that mean? Are you spending yourself to give to the project? Are there two economies here? Is the consequence EV a tax<\/em> on top of your contribution?<\/p>\n\n\n\n I wrote, to myself: “Rather than making this clunky, ‘I’m putting my 5 EV into this project this cycle’, shouldn’t we just use rolls, but rolls that don’t necessarily cost EV? I have a bit of a coherence problem.”<\/em><\/p>\n\n\n\n That last sentence is doing a lot of work. “A bit of a coherence problem.” It’s the polite version of: I’m about to bolt a new system onto this game because I forgot how the existing one actually works.<\/em><\/p>\n\n\n\n Here’s what happened next, and it’s a little embarrassing.<\/p>\n\n\n\n I was walking through the mechanic with the AI, using it as a sounding board, a design partner, a way to stress-test ideas without calling a playtest session at 11pm on a Tuesday, and it reflected back at me something I had written. Months ago. The consequence system.<\/p>\n\n\n\n “If there’s a consequence, you can charge 1 EV per roll to the characters.”<\/em><\/p>\n\n\n\n Oh.<\/p>\n\n\n\n Right.<\/p>\n\n\n\n The 1 EV on a consequence isn’t an arbitrary cost. It’s the game asking: what did this action cost you? Stress. Physical effort. A close call. Something you burned through to make that moment happen. That’s what EV represents, the totality of a person’s capacity to act under pressure. And when a player makes a roll to actively contribute to a construction project, and it’s hard, and they barely pull it off? Yeah. That costs something. It costs exactly 1 EV.<\/p>\n\n\n\n I hadn’t invented a coherence problem. I’d invented a solution to a problem I’d already solved.<\/p>\n\n\n\n The design insight here isn’t complicated, but it’s worth sitting with: a well-designed Rule-Lite system has more depth than its creator keeps in their head at any given moment.<\/em><\/p>\n\n\n\n That’s really incredible. After realizing it, you feel a bit dumb and smart at the same time.<\/p>\n\n\n\n Sol Fracta runs on one mechanical language. One D10. One threshold. Three outcomes. Consequences that pull from a unified list. No subsystems. No special cases. The discipline of building that way: refusing to add a new rule every time a new fiction demands resolution, means that when you need to handle construction contribution<\/em>, you don’t build a Construction Contribution Subsystem. You ask: how does the existing language apply here?<\/p>\n\n\n\n And the answer is: a roll. With consequences, like every other roll. Including the 1 EV cost if it’s not clean. Which creates exactly the texture you want: the engineer who pushes too hard this cycle and arrives at the next one slightly more depleted, slightly more worn down. The game represents that. It always did.<\/p>\n\n\n\n The AI didn’t invent the solution. It reminded me of my own system. That’s a different thing. That’s the value of having an external voice in your design process, not to generate ideas you don’t have, but to hold the whole system in view while you’re tunneled into a specific problem.<\/p>\n\n\n\n I was in the tunnel. The tunnel was “how do I make construction contribution feel meaningful?” The answer was two meters to my left. The 1 EV consequence on a consequential roll already does exactly that.<\/p>\n\n\n\n This keeps happening with Sol Fracta, and I think it’s a sign that the core is actually solid.<\/p>\n\n\n\n Every time I feel the pull toward a new mechanic \u2014 a new subsystem, a new exception, a new rule to handle an edge case \u2014 The discipline of rule-lite JDR <\/a>design means asking one question before building anything new: does the existing language already handle this? Usually it does. Sometimes it handles it in a way I’d temporarily forgotten.<\/p>\n\n\n\n Rule-Lite design isn’t minimalism for its own sake. It’s not about being clever or constrained. It’s about building a system that’s complete enough to reuse, rather than one that grows a new limb every time it encounters friction. <\/p>\n\n\n\n
\n\n\n\n
\n\n\n\n
\n\n\n\n
\n\n\n\n