Dota 2 Build and Playstyle Coach

Problem

New Dota 2 players often get item advice without context: a list of items, no version basis, and no explanation of why the items fit the hero. dota2-coach targets that workflow by answering hero-specific build and playstyle questions from local JSON data, without calling external APIs by default.

It is not a generic strategy page. It focuses on win-rate status, recommended items, the reasoning behind the build, and the key execution points for a hero. Broader sections such as hero overview, ability data, talent tree, or laning advice are included only when explicitly requested.

How it works

The skill reads four local data files:

• heroes_db.json: hero stats, win rate, pick rate, and warning flags
• abilities_db.json: hero abilities, Q/W/E/R, and innate abilities
• talents_db_cn.json: Chinese talent trees
• item_popularity.json: per-stage popular item statistics for each hero

When generating a build, it first looks up the hero's hero_key in item_popularity.json, compares stage-level top-3 items, then filters the result using hero role, ability cooldown, mana cost, cast range, innate ability, Aghanim's Scepter, and Shard effects. Crystal Maiden uses a fixed build path; other heroes select the most representative item from the popular list as the recommendation.

Typical output includes:

• Win rate: Medium ranks by default, with higher ranks available on request
• Regular build: stage-aware item suggestions
• Build reasoning: core path and situational replacements
• Playstyle notes: execution priorities based on full ability data

Boundaries

The content is based on Dota 2 7.41 data and should be recalibrated after hero, item, or mechanic changes. It is useful for build direction, counter-item suggestions, and explaining hero mechanics, but it is not a replacement for live match data, precise win-rate models, or full draft analysis. Data updates are expected to be written back into the corresponding JSON files by field.