Myth: "Kill Your Darlings" Means Restarting. It Doesn't.

Title: “Kill Your Darlings” Isn’t a Scrapyard. It’s a Forge.

The phrase “kill your darlings” echoes in every creative field, a chilling reminder that sentimentality can strangle a project. In game development, however, it’s often misinterpreted as a license to scrap entire systems or mechanics. That’s wasteful. It misses the point entirely.

“Killing your darlings” shouldn’t mean restarting. It should mean refining. It’s about ruthlessly assessing what actually serves your game. This isn’t about tearing down. It’s about building better.

The Misinterpreted Mandate

The common, destructive interpretation is that if something isn’t working perfectly, it must be eradicated. This leads to endless cycles of prototyping and discarding. We see this especially in indie game development, where resources are scarce and momentum is critical.

Imagine spending weeks perfecting a complex inventory system, only to realize it slows down the core gameplay loop. The knee-jerk reaction might be to trash it completely. But that’s akin to demolishing a house because one room has a leaky faucet.

The problem isn’t necessarily the system itself. It might be how it’s implemented or integrated. A better approach is to identify the bottlenecks and address them directly.

Refining, Not Restarting: A Practical Approach

Instead of defaulting to annihilation, view “killing your darlings” as a sophisticated editing process. This involves critical analysis and creative problem-solving. It’s about making smart cuts, not blind slashes.

Start by identifying elements that drain resources without providing commensurate value. This requires honest self-assessment and, ideally, playtesting feedback. What features consistently confuse players? Which systems take the most time to maintain but contribute the least to the core experience?

Cost/benefit analysis is your best friend here. Quantify the development effort (time, money, lines of code) and weigh it against the perceived player value. Is that incredibly detailed character customization system truly worth the weeks of animation work?

Common “Darlings” and Creative Solutions

Let’s look at some common areas where game developers fall prey to “darling” attachments and how to avoid the scrapheap mentality.

One is over-scoping. Early on, many developers attempt to cram every idea they’ve ever had into a single game. This results in a bloated, unfocused mess. A better solution is to prioritize core mechanics and cut features that don’t directly support them. Defer those cool ideas to future projects or DLC.

Another trap is unnecessary complexity. A perfect example is overly elaborate AI. Do your enemies really need to simulate complex emotional states? Probably not. Simplify the AI until it serves its purpose: providing a challenging and engaging experience. Focus your efforts where it matters most - the core gameplay loop.

Story elements can also be darlings. Perhaps you’ve written pages of intricate lore that no player will ever read. Instead of deleting it entirely, consider streamlining the narrative. Integrate the lore into environmental details or optional dialogue. Reward players who seek it out without forcing it upon them.

An Indie Horror Case Study

I worked on an indie horror game where we became enamored with a complex crafting system. It involved scavenging resources, combining ingredients, and managing limited inventory space. We thought it would add depth and tension.

Playtesters, however, found it frustrating and tedious. They spent more time managing their inventory than actually being scared. The problem wasn’t the idea of crafting, but its implementation.

Instead of scrapping it, we drastically simplified the system. We reduced the number of resources, streamlined the crafting recipes, and introduced a quick-crafting option for essential items. This preserved the core concept while eliminating the friction that was detracting from the horror experience.

Avoiding the Restart Trap

To avoid falling into the “restart” trap, implement these strategies:

• Prototype extensively: Before committing to any major feature, build a quick prototype to test its core mechanics. This allows you to identify potential problems early on, before investing significant resources.

• Embrace iteration: Game development is an iterative process. Expect to revise and refine your designs as you go. Don’t be afraid to experiment with different approaches and discard ideas that don’t work.

• Get feedback early and often: Show your game to other developers, friends, and potential players. Collect feedback on what works, what doesn’t, and what needs improvement. Listen to this feedback.

• Focus on the core experience: Always keep the core gameplay loop in mind. Every feature should support and enhance this experience. If a feature doesn’t contribute to the core, it’s probably a darling that needs to be sacrificed or radically altered.

• Set realistic goals: Avoid over-scoping your project. Be honest about what you can realistically accomplish with your available resources. It’s better to release a polished, focused game than a bloated, unfinished one.

The Forge, Not the Scrapyard

“Kill your darlings” is not an execution order. It is a directive for creative problem-solving. It’s about transforming raw ideas into refined, impactful experiences.

Embrace the challenge of refining your work. You might be surprised at how much potential lies hidden within those seemingly flawed “darlings.” View your game as a forge. Heat, hammer, and shape your ideas until they take their final form. Don’t throw them into the scrapheap. Transform them. The result will be a stronger, more focused game that truly resonates with players.

It’s a difficult, necessary process. But ultimately, it’s what separates good games from great ones.