Solo Game Developer Faces Dilemma | Tactical RPG Vertical Slice Chaos
Edited By
Sarah O'Neil
A solo developer is grappling with the overwhelming task of creating a vertical slice for their tactical RPG, which features village management and emotional consequences. After a year of development, they have 14 systems in place but lack clarity on what to showcase.
Context and Challenges
The developer's game centers around a prince tasked with managing a village before war, featuring permanent villager deaths that affect families. Aiming for feedback, the creator is unsure about including combat, building, or relationships in the vertical slice.
Overarching Systems Implemented
The project boasts several core functionalities:
Grid-based movement with pathfinding
Turn-based combat akin to Fire Emblem
Building placement and construction
Resource production cycles
Inventory and equipment management
Skill progression with over 25 skills
Dynamic job roles for villagers
Resource management for gold, food, and wood
Character animations and visual feedback
Developer's Dilemma
In seeking advice, the developer raised critical questions:
What aspects truly demonstrate the game’s identity?
Is it necessary to show all systems, or can he focus on one polished mission?
As they ponder these questions, comments from fellow developers offer insights and possible solutions.
Community Insights
Focus on Essential Features: One contributor suggested starting with a battle tutorial, which would highlight important combat mechanics, followed by village management tasks afterward. This way, players can experience the interconnectedness of the gameplay.
"Show all important systems and add a time limit to keep pace."
Risk Mitigation: Another commenter emphasized that initial testers who are familiar with indie titles are aware that they might risk their time. Creating a gameplay scenario where players can quickly explore core mechanics could alleviate this burden.
Long-term Systems: The community recognizes that early players are unlikely to invest time without seeing potential payoff. A short demo showcasing essential elements will help engage early feedback from potential players.
Sentiment in the Community
Overall, the sentiment among responses is constructive. Developers are eager to assist, sharing experiences from their own journeys, which portrays a collaborative effort to aid the solo dev.
Takeaways
🔹 Engaging early players is crucial to reduce perceived risk.
🔸 A polished demo focusing on essential mechanics might appeal more.
🔹 "Creating a focused slice can help players intuitively grasp the game’s essence."
Curiously, as this solo dev navigates the complexities of game design, many in the community echo similar sentiments, highlighting the shared struggles faced by indie developers.
What's Next for the Indie Developer?
Looking ahead, the solo developer faces critical decisions. There's a strong chance they'll narrow down their focus based on community feedback, possibly opting for a polished combat demo to showcase gameplay identity. Experts estimate around 70% of indie devs encounter similar crossroads, emphasizing the importance of clear communication of their vision early on. Additionally, engaging with experienced testers can help refine their game mechanics before launching a more extensive demo. By prioritizing essential features, the developer may secure stronger interest from potential players, setting the stage for future success.
Echoes from Gaming History
A striking parallel can be drawn between this developer's situation and that of early arcade game creators, like the developers behind 91's Street Fighter II. Initially, they faced immense pressure to deliver a comprehensive game but opted to commit to refined core mechanics instead. This singular focus not only defined their game's success but also revolutionized fighting games as a whole. Much like that era, today's indie developers can find strength in clarity and precision, reminding us that sometimes less truly is more in the chaotic world of game creation.