Implementing Advanced Enemy Mechanics: Zombie Tank Behaviors

Improving Gameplay Dynamics

In our ongoing work on the project '2024s2-tp-grupal-juego-grupo-1-uwu', we have been focusing on refining the tactical depth of our non-player character encounters. Specifically, we have been iterating on the logic governing our 'Zombie Tank' entity to ensure that its presence on the battlefield provides a meaningful challenge to the player.

The Challenge

Previously, the interaction between the player and the Tank-type enemy felt static. The enemy lacked a nuanced damage model, meaning encounters were predictable and lacked the intensity required for high-stakes gameplay. Our goal was to create a more reactive combat experience where damage output is tied to specific movement states and player proximity.

Implementation Approach

We introduced a new calculation layer to handle the damage output. Instead of a flat damage value, the system now evaluates the enemy's current state—specifically its movement phase—before applying damage to the player entity.

function calculateDamage(enemyState, baseDamage) {
    if (enemyState === 'advancing') {
        return baseDamage * 1.5;
    }
    return baseDamage;
}

This logic ensures that a 'Zombie Tank' in its active, advancing state deals significantly more impact than when it is idle. By decoupling state from raw damage values, we allow for more flexible balancing in future updates.

Key Decisions

1. State-Dependent Damage: By conditioning damage on movement states, we force players to identify and react to specific enemy animations.
2. Scalable Architecture: The current approach allows us to easily add new modifiers for different enemy archetypes without cluttering the main combat handler.
3. Focus on Feedback: The movement-damage integration provides immediate mechanical feedback, making the AI feel more intelligent and threatening.

Outcomes

• Encounters with high-health enemies now require active evasion and positioning.
• Combat balancing is more granular, allowing for precise difficulty tuning.
• The codebase remains clean, favoring composition over hard-coded conditional chains.

Lessons Learned

Iterating on game mechanics taught us the importance of testing AI transitions under load. Small adjustments to state logic can have ripple effects on overall game balance, emphasizing the need for robust state management.

Generated with Gitvlg.com