Skip to content

Cowculator

Turn battle plans into battle stories

Cowculator is a turn-based battle calculation engine for game developers. Send in two fighters, their stats, and their skill rotations. Cowculator handles the clash from the opening move to the final moo-ve.

You get the winner and a structured battle log that your game can replay, animate, or narrate. No mid-battle button mashing required. The strategy lives in how you build each fighter before the battle begins.

Why Cowculator?

  • Keep battle logic out of your game

    Send fighter configurations to one API instead of rebuilding turn order, damage, healing, statuses, and battle endings in every client.

  • Focus on the fun parts

    Spend more time designing fighters, skills, progression, visuals, and game feel. Let Cowculator handle the number-crunching behind each fight.

  • Get the whole battle in one response

    One request runs the battle from preparation to the final outcome. Use the summary for a quick result or the battle log for the full story.

  • Build replays without reading tea leaves

    Structured events and fighter snapshots give your UI concrete data for animations, combat logs, and post-battle explanations.

Where Cowculator shines

Cowculator feels at home in games where:

  • Fighters follow a skill rotation planned before combat
  • Speed and turn timing shape the outcome
  • Stats, buffs, debuffs, and resource management matter
  • Battles run automatically
  • The result needs to be replayed, animated, or explained

That makes it a natural fit for turn-based RPGs, card battlers, idle games, and PvP simulations.

How the battle unfolds

  1. Bring your fighters

    Configure fighter_1 and fighter_2 with their stats, active skills, passive skills, and zero-cost fallback skills.

  2. Let the turn meters tick

    Each fighter builds turn meter from their speed. When a fighter is ready, Cowculator selects the next skill in their rotation.

  3. Watch the fur fly

    Attacks land, heals restore resources, statuses change the matchup, and shields soften the blows until one fighter wins or the turn limit decides the outcome.

  4. Tell the battle story

    Read the winner directly, or process the structured events to build a replay, combat log, animation, or post-battle breakdown.

Chance-based mechanics remain part of the fun. If a skill, action, or critical hit has a chance below 1, the same fighter setup can produce a different battle next time.

Pick your next stop

Looking for exact fields?

Use the OpenAPI reference for complete endpoint, request, and response schemas, defaults, and validation rules.

Ready to put two fighters in the ring? Start with the Quick Start. No cattle prod required.