"Starfall Tactics": How We Saved Our Vision with Paper

Starfall Tactics: How We Saved Our Vision with Paper

Developing an ambitious indie game is like navigating a dense fog. You have a destination in mind, but the path is obscured by countless challenges. For our team working on Starfall Tactics, a real-time strategy game with complex fleet customization, that fog threatened to consume us. We were drowning in systems, losing sight of the core fun. Our savior? Surprisingly, paper.

The Problem: Complexity Creep and Vision Drift

Starfall Tactics was conceived as a deeply strategic experience, where players could build fleets from scratch using modular ship components. We envisioned endless possibilities, but the reality was overwhelming. Players struggled to understand the system, progression felt slow, and the core gameplay loop became muddled.

We spent countless hours debating mechanics, implementing features, and iterating in-engine. The problem was, we were iterating on top of a shaky foundation.

One major issue was the sheer number of ship modules. Each had stats, abilities, and interactions. The sheer volume of information made it difficult for players to grasp the overall strategy. It was like trying to assemble a jigsaw puzzle with a million pieces and no picture.

Another hurdle was unclear player progression. We had different tiers of ships and modules, but players weren’t feeling a sense of accomplishment as they unlocked new options. The progression curve felt flat and unrewarding.

We were so focused on the technical aspects of implementation that we lost sight of the player experience. Our grand vision was slipping away.

The Paper Solution: Stripping Down to the Essentials

Realizing we needed a radical shift, we decided to embrace paper prototyping. It felt counterintuitive at first – going back to basics after so much development. However, it proved to be the most effective way to clarify our vision.

Our first step was to create a card-based system representing each ship module. Each card contained essential information: name, stats, a brief description, and resource cost. We printed dozens of these cards and started experimenting with different fleet compositions.

We used a large whiteboard to represent the battlefield. We moved cards around, simulating combat and testing different strategies. This low-fi approach allowed us to quickly iterate on module stats, costs, and abilities without spending hours coding.

We also used paper to prototype different progression systems. We created flowcharts outlining the unlock paths for ships and modules. We playtested these systems with our team and external testers, tracking their reactions and feedback.

The key was to focus on the core mechanics and player experience, abstracting away the technical complexities. Paper allowed us to do that.

Data and Insights: Regaining Focus

The paper prototyping sessions generated a wealth of data and insights. Most importantly, they revealed that many of our original module designs were redundant or unnecessary. We were able to identify the modules that were truly interesting and impactful, and prune the rest. This significantly simplified the game for new players.

We discovered that players responded positively to a more linear progression path early in the game. This allowed them to gradually learn the mechanics before being overwhelmed by choices. We adjusted the progression system to introduce new modules and ships in a more controlled manner.

Another key insight was the importance of visual clarity. Players struggled to differentiate between modules with similar stats. We realized we needed to improve the visual design of the modules to make them more easily recognizable. We were able to define these visual improvements by observing player behavior during our paper prototyping.

We learned that simplicity is key. Complexity is good, but only when it emerges from simple, understandable components. The paper prototypes helped us strip away the unnecessary layers and focus on the core strategic choices.

Concrete Improvements: From Paper to Production

The insights gained from paper prototyping directly translated into tangible improvements in Starfall Tactics.

We drastically reduced the number of ship modules, focusing on those that offered unique strategic options. This made the game more accessible to new players and improved the overall balance.

We revamped the progression system to introduce new modules and ships gradually. This created a more satisfying learning curve and gave players a sense of accomplishment.

We improved the visual design of the modules, making them more easily recognizable and visually appealing. This enhanced the player experience and reduced cognitive load.

The result was a game that was more focused, more engaging, and more aligned with our original vision. Players found it easier to learn, more rewarding to progress, and more satisfying to master.

Avoiding Common Mistakes: Lessons Learned

Looking back, we made several mistakes that could have been avoided. One was waiting too long to embrace paper prototyping. We should have started with this approach earlier in development, before investing significant time in coding complex systems.

Another mistake was being too attached to our original designs. We were reluctant to cut modules or change the progression system, even when the data suggested otherwise. It’s important to be objective and willing to make tough decisions based on player feedback.

Don’t treat paper prototyping as a one-time fix. Integrate it into your development workflow. Regularly test new features and mechanics with paper before implementing them in-engine.

Actionable Advice: Integrating Paper into Your Workflow

So, how can you, as an indie game developer, integrate similar low-fi prototyping techniques into your workflow?

Start simple. Don’t try to simulate every aspect of your game with paper. Focus on the core mechanics and player experience. Use index cards, whiteboards, and dice to represent game elements and simulate interactions.

Playtest frequently. Get feedback from your team and external testers. Observe how they interact with your paper prototypes and listen to their comments.

Iterate rapidly. Don’t be afraid to make changes based on feedback. Paper prototyping allows you to quickly experiment with different ideas without investing significant time in coding.

Document your findings. Keep track of your test results and the insights you gain. This documentation will be invaluable when you start implementing the features in-engine.

Remember, paper prototyping is not a replacement for in-engine testing. It’s a complementary tool that can help you refine your vision and make better design decisions. It is a vital step in ensuring that your game is fun, engaging, and aligned with your original goals. Embrace the power of paper, and you might just save your game too.