Elemental Echo Dev Blog_6: Final Polish, Playtest Reflections, and Design Retrospective

 

1. Wrapping the System: Final Week Adjustments

As we approached the end of the project timeline, our focus shifted from building systems to refining them. This final phase was about polish, clarity, and feedback response.

Key adjustments I contributed to during the final sprint included:

  • Crown Scoring UI Update: We added a glowing pulse animation and countdown tick for every 5-second point gain. This makes scoring visible and satisfying.

  • Respawn Alerts: Introduced new visual/audio indicators when a base is under attack, increasing urgency for defenders.

  • Elemental Zone Markers: Now include a mini-map ping and ambient glow when active, helping players leverage terrain better.

Each of these changes was driven by playtest results, helping to bridge the gap between design intent and actual player experience.

2. Playtest Feedback and Response

We conducted three rounds of small-group playtests across different stages of development. Key findings included:

Player FeedbackOur Design Response
“Sometimes I don’t notice when I’m holding the Crown.”Added outline highlight, center-screen icon, and subtle vibration cue (if using gamepad).
“The map looks cool but I get lost easily.”Introduced environmental color-coding (Fire = warm lighting, Water = blue crystals, etc.) for better orientation.
“Wind class feels too slippery to hit.”Slightly reduced dash distance, added 0.25s cooldown before next cast.
“Fights feel great, but ultimates are hard to follow.”Standardized ultimate indicators with full-screen ring and announcer VO cue.

The result was a game that felt tighter, more readable, and more expressive, even within the limits of a student prototype.


PLaytest Screen

3. Personal Design Reflection

Looking back, this project helped me grow in several key areas as a game designer:

a. System Thinking

I learned how to create mechanics that don’t exist in isolation, but interact—Crown scoring, elemental synergy, and base defense all affect each other. Balancing their relationships required iteration and abstraction.

b. Player-Centered Design

By observing how real players misinterpret or ignore mechanics, I learned how critical signaling and onboarding are. A good mechanic fails without a good way to understand and feel it.

c. Cross-Disciplinary Collaboration

I collaborated closely with programmers (for mechanics prototyping), artists (for skill visual design), and sound designers (for feedback tuning), which taught me how to document clearly, iterate quickly, and respect other pipelines.

4. What I Would Improve With More Time

If we had additional development time, I would:

  • Expand the tutorial experience into a narrative-driven onboarding mission

  • Add more status effects and counters for team synergy (e.g., silences, slows, shield buffs)

  • Introduce alternate game modes (e.g., base-only siege or elemental free-for-all)

These would help reinforce the elemental fantasy while expanding player choice and meta-strategy.

5. Final Thoughts

Elemental Echo began as a simple control-point prototype but evolved into a layered, timing-sensitive, class-based tactical game. It’s still rough around the edges—but every mechanic in it was crafted with intent, tested with feedback, and tuned for interaction.

I’m proud not just of the result, but of the process—and of what I learned about clarity, systems, and the invisible language that makes games feel good.

评论

此博客中的热门博文

Elemental Echo Dev Blog_5: Combat Feedback and Tuning the Feel of the Fight

Elemental Echo Dev Blog_1: Concept Development and Core Gameplay Design

Elemental Echo Dev Blog_3: Map Design and Tactical Flow in Elemental Echo