RPG owns the numbers that make a character grow: stats, levels, damage, items and quests. The agent designs from target outcomes such as minutes per level and hits to kill, derives formulas and tables from them, and checks the tables with a script before anyone plays.
It works with any engine, including custom ones, by binding its data shapes to the project’s content format and save interface after reading the existing items and stats.
What You Get
- Pacing targets for level cap, hours to cap and minutes per level, with a minutes-based XP table
- A damage formula family with hit targets, such as 2 to 4 hits for a normal enemy
- A base stats plus modifier stack pattern that removes modifiers by source id
- Defaults for variance, crits, type multipliers, rarity weights and item level
- A balance script spec that prints one row per level and fails outside the targets
- A reference on stat blocks, damage families, XP variants, turn timelines, item shapes and quest state
Common Use Cases
- Building a JRPG or Diablo style progression system from pacing targets
- Fixing stats that stay wrong after a buff ends or gear is removed
- Stopping enemies from becoming immune through stacked defense
- Taming late-game number growth and flat loot
What Makes It Unique
It starts from outcomes and verifies them: a script prints each level’s HP, damage, hits to kill and minutes to next level, and an equip and unequip test asserts stats return exactly to old values. Its formula table explains the reason behind each default, with sources such as League of Legends armor and Path of Exile resist caps.
Under The Hood
The skill is a SKILL.md with one reference file on stats, combat and quests. The agent reads your item, stat and enemy data, edits it and writes a balance script and tests that it runs with the project’s tooling. The snippets are pseudocode. The version notes cite outside wiki pages, but the skill does not tell the agent to fetch web pages or call services.