Dota 2 Arcade Abilities And Items
Overview
Use this skill for ability, item, and modifier work. Prefer TypeScript ability/modifier classes in modern projects, but keep KV definitions accurate because Dota still reads ability and item metadata from KV.
File Scope
game/scripts/npc/npc_abilities_custom.txtgame/scripts/npc/npc_items_custom.txtsrc/vscripts/abilitiessrc/vscripts/itemssrc/vscripts/modifiers- legacy
game/scripts/vscripts Lua ability or modifier files
Implementation Workflow
- Find the KV entry first. Confirm ability/item name, behavior flags, cast range, cooldown, mana cost, texture, and
AbilityValues.
- Find or create the TypeScript/Lua logic class that matches the KV script binding pattern used by the project.
- Put tunable numeric values in
AbilityValues unless they are purely internal implementation constants.
- Implement modifiers as separate reusable classes when behavior persists over time or affects properties.
- Keep server-side effects server-side. Send only UI feedback through Panorama events or nettable state.
- Test level scaling, special values, illusions, spell immunity, death, purge, and cooldown/charge edge cases when relevant.
KV Guidance
- Preserve exact KV nesting and quoted keys.
- Prefer
AbilityValues for values used in tooltips or balance changes.
- Match ability behavior flags to the intended targeting model.
- Keep custom item names and ability names stable once referenced by units or scripts.
- Be careful with DataDriven examples: use them as legacy reference unless the project already relies on DataDriven.
Modifier Guidance
- Declare properties and states in the style used by the project.
- Keep interval thinkers, aura logic, and stack logic isolated.
- Use server checks around state mutations.
- Handle cleanup on destroy when particles, sounds, dummy units, or timers are created.
Assets
Use snippets under assets/snippets/ for minimal ability, modifier, and KV starting points. Adapt to the local decorator/registration pattern before pasting.
Documentation
Use ModDota abilities, abilities/datadriven, and abilities/lua-modifiers articles for examples. Use local project declarations for exact TypeScript signatures.
Coordinate With Other Skills
Use dota2-arcade-units-heroes when abilities are assigned to units/heroes. Use dota2-arcade-assets-content when particles, models, sounds, or icons are part of the ability.
1---2name: dota2-arcade-abilities-items3description: Create, modify, and debug Dota 2 Arcade custom abilities, items, modifiers, AbilityValues, ability/item KV, DataDriven legacy definitions, and TypeScript or Lua ability logic. Use when implementing spells, item actives/passives, charges, cooldowns, tooltips, modifier properties, or ability events.4---56# Dota 2 Arcade Abilities And Items78## Overview910Use this skill for ability, item, and modifier work. Prefer TypeScript ability/modifier classes in modern projects, but keep KV definitions accurate because Dota still reads ability and item metadata from KV.1112## File Scope1314- `game/scripts/npc/npc_abilities_custom.txt`15- `game/scripts/npc/npc_items_custom.txt`16- `src/vscripts/abilities`17- `src/vscripts/items`18- `src/vscripts/modifiers`19- legacy `game/scripts/vscripts` Lua ability or modifier files2021## Implementation Workflow22231. Find the KV entry first. Confirm ability/item name, behavior flags, cast range, cooldown, mana cost, texture, and `AbilityValues`.242. Find or create the TypeScript/Lua logic class that matches the KV script binding pattern used by the project.253. Put tunable numeric values in `AbilityValues` unless they are purely internal implementation constants.264. Implement modifiers as separate reusable classes when behavior persists over time or affects properties.275. Keep server-side effects server-side. Send only UI feedback through Panorama events or nettable state.286. Test level scaling, special values, illusions, spell immunity, death, purge, and cooldown/charge edge cases when relevant.2930## KV Guidance3132- Preserve exact KV nesting and quoted keys.33- Prefer `AbilityValues` for values used in tooltips or balance changes.34- Match ability behavior flags to the intended targeting model.35- Keep custom item names and ability names stable once referenced by units or scripts.36- Be careful with DataDriven examples: use them as legacy reference unless the project already relies on DataDriven.3738## Modifier Guidance3940- Declare properties and states in the style used by the project.41- Keep interval thinkers, aura logic, and stack logic isolated.42- Use server checks around state mutations.43- Handle cleanup on destroy when particles, sounds, dummy units, or timers are created.4445## Assets4647Use snippets under `assets/snippets/` for minimal ability, modifier, and KV starting points. Adapt to the local decorator/registration pattern before pasting.4849## Documentation5051Use ModDota `abilities`, `abilities/datadriven`, and `abilities/lua-modifiers` articles for examples. Use local project declarations for exact TypeScript signatures.5253## Coordinate With Other Skills5455Use `dota2-arcade-units-heroes` when abilities are assigned to units/heroes. Use `dota2-arcade-assets-content` when particles, models, sounds, or icons are part of the ability.
emojiiii