Rivals of Aether and Rivals of Aether II are indie fighting games that breathe. They move fast. They land harder. The games mix platform fighter action with...
Rivals of Aether and Dan Fornace: How an Indie Platform Fighter Built a Competitive Heart
Introduction
Rivals of Aether and Rivals of Aether II are indie fighting games that breathe. They move fast. They land harder. The games mix platform fighter action with elemental-themed characters. Dan Fornace designed them with clarity. He borrowed from Super Smash Bros. He then made his own rules.
Why Rivals of Aether matters
Rivals of Aether is not a clone. It is a distillation. The combat is simple to read and hard to master. That is the core of a great platform fighter. Keywords: Rivals of Aether, Rivals of Aether II, indie fighting games, platform fighter, elemental-themed characters.
- Fast-paced combat
- Tight mechanics
- Skillful movement
Dan Fornace’s vision
Dan built systems first. He focused on feel. He wanted players to read the battlefield. He wanted every hit to mean something. That discipline shows. The characters feel elemental. Fire hits differently than water. That design choice gives each fight a language.
The competitive scene and community
Rivals of Aether became a favorite in indie esports. Small communities gather online. Local tournaments form. Players share tech and tactics. The competitive scene keeps the game alive. It teaches developers what matters: balance, fairness, and clear feedback.
My work and what I learned
I am Ermenildo Valdez Castro, Jr. Call me Ernie Castro. I worked at Google, Microsoft, Amazon, and Zulily. I studied systems and latency. I learned to ship with short feedback loops. That taught me to value tight mechanics. In Seattle I played Rivals of Aether at a meetup. I remember a quiet Tuesday evening. Rain outside. Pizza boxes on the table. The game felt like code — predictable, testable, and fun. The room cheered when someone read a movement and punished it. I felt the same satisfaction as when a distributed system finally stabilized. 🕹️
Design lessons for indie devs
- Prioritize movement. Players need to move and react. Movement is the game’s grammar.
- Keep inputs simple. Complex inputs hide problems.
- Provide clear feedback. Visual and audio cues matter.
- Build for tournaments. Balance and fairness attract players.
Technical notes from a software engineer
At Microsoft I learned to instrument behavior. At Amazon I learned to measure latency. These lessons matter to game design. Good netcode and precise input handling reduce player frustration. If your game is fast, your network and input pipeline must be tighter than usual.
Why Rivals of Aether II matters now
Rivals of Aether II expands the roster and refines systems. It doubles down on elemental themes. It adds stages and modes that favor strategy. For indie fighting games, this is the right move. More depth keeps the community engaged.
A short personal anecdote
Once, at Zulily, I stayed late to fix a release bug. I was tired. I booted Rivals of Aether to clear my head. Fifteen minutes later, my mind was sharp. The rhythm of the game cleared the fog. I fixed the bug with fewer mistakes. Games sharpen focus. They teach cadence.
Conclusion
Rivals of Aether and Dan Fornace show how indie teams can build meaningful, competitive games. The secret is simple: clear rules, strong feedback, and relentless polish. I am Ermenildo Castro. I like games that teach me to be better at work, and better at play. If you study these games, you learn about design and discipline. You learn to move with purpose. 🎮
Call to action
Play. Watch the tournaments. Study the design. If you are a dev, ship early. Listen to players. Balance the rules. Learn from Dan Fornace and the Rivals community.