Elemental Echo Dev Blog_1: Concept Development and Core Gameplay Design
1. Project Background and Design Intent
For this semester’s Connected Games group project, our team is developing a 2v2 third-person multiplayer combat game titled Elemental Echo. As the game designer on this project, I am responsible for gameplay mechanics, system structure, and supporting the coordination between design and technical implementation.
2. Gameplay Prototype: “Crown Control” as the Core Mechanic
The central mechanic in Elemental Echo is Crown Control: A powerful object—the Crown—spawns periodically at the center of the map. The team holding the Crown gains 1 point every 5 seconds. The first team to reach the target score wins.
This mechanic creates multi-layered battle dynamics:
-
Initial contest and suppression: The Crown zone naturally becomes the focal point of combat.
-
Scoring under pressure: Crown holders gain stat boosts but suffer reduced movement speed and visibility penalties. If eliminated, the Crown drops and can be claimed by others.
-
Push-and-pull strategy: Holding the Crown increases your score, but leaves your base vulnerable. Teams must decide between maintaining control or defending their own territory.
-
Real-time decision-making: Opponents may sacrifice Crown fights to flank and destroy your base, cutting off respawns and forcing long-term consequences.
This is not a standard King-of-the-Hill mode. It’s a shifting, high-stakes system that requires teams to constantly balance pressure, support, and defense.
3. Supporting Systems: Respawn Bases and Role Differentiation
To support the core loop of “Control + Support + Disruption,” we designed two key systems:
-
Respawn Base System: Each team has a destructible respawn base. If destroyed, that team can no longer respawn. This creates high-risk scenarios where even a team controlling the Crown can still lose if their base is wiped out.
-
Role Diversity Across Elemental Classes:
-
Fire: High-damage DPS for zone control and burst pressure.
-
Water: Short-range support with healing and sustain, crucial for extended engagements.
-
Wind: Agile disruptor focused on flanks, repositioning, and interrupting enemy strategies.
-
These roles naturally align with the broader game flow—each one contributing to different parts of the battle loop: contesting, supporting, or sabotaging.
4. Design Decisions and Inspirations
When deciding on this gameplay structure, we studied several reference games:
-
Overwatch: for team synergy and role-based ability structure.
-
Control Point modes in competitive FPS titles: for dynamic objective pressure.
-
Dota 2: its multi-priority map control inspired our “Crown vs. Base” trade-off system.
In the end, we chose a structure built around one high-value, visible scoring objective balanced against multiple hidden or delayed risks, allowing for complex tactical variations.
5. Current Progress and Next Steps
Completed this sprint:
-
Defined core gameplay systems: Crown scoring, win conditions, respawn mechanics.
-
Drafted elemental class roles and tactical implications.
-
Aligned on early map functional zones with the team: Crown spawn zone, respawn bases, elemental zones.
Plans for the next two weeks:
-
Finalize input model and pacing for each elemental class (5-skill layout).
-
Begin wireframing the in-game UI layer (status display, objective tracking, skill readiness).
-
Assist in early prototyping and test scoring tempo vs respawn frequency.
6. References
-
Blizzard Entertainment. (2016). Overwatch
-
Valve. (2013). Dota 2
-
Schell, J. (2008). The Art of Game Design: A Book of Lenses
-
Unity Asset Store – Elemental VFX Pack

评论
发表评论