Rpg Status Bar Blueprint

RPG-themed statusline with character progression, XP accumulation, class advancement, health points, and mana tracking.

When to Use This Setting

Apply this setting when you need to:

• Level up your coding sessions with an RPG progression system that tracks experience and class advancement
• Monitor your git working tree health as HP and project dependencies as mana in a game-inspired format
• Create a persistent character across coding sessions that evolves from Novice to Wizard to Archmage Consider alternatives when:
• RPG theming conflicts with your professional coding environment standards
• You do not use git for version control and the HP calculation based on uncommitted files would be meaningless

Quick Start

Configuration

Copy
name: rpg-status-bar-blueprint
type: setting
category: statusline

Example Application

Copy
claude setting:apply rpg-status-bar-blueprint

Example Output

Setting applied. Changes:
- statusLine.type: command
- statusLine.command: bash rpg-status-bar inline
- class_progression: Novice(1-4), Wizard(5-9), Archmage(10+)
- xp_per_interaction: 3
- level_up_formula: XP >= level * 100
- hp_source: 10 minus uncommitted git files
- mana_source: package.json existence check

Core Concepts

RPG Progression Overview

Aspect	Details
Class System	Novice at levels 1-4, Wizard at levels 5-9, Archmage at level 10 and above
Experience Points	Gains 3 XP per interaction, resets to 0 on level up with increasing thresholds
Level Up Formula	Levels up when accumulated XP reaches level multiplied by 100
Health Points	10 minus the count of uncommitted files from git status porcelain output
Mana System	Blue mana if package.json exists in the directory, empty white otherwise

RPG State Architecture

+-------------------+     +---------------------+     +------------------+
| Session Cache     |---->| XP Accumulator      |---->| Level Up Check   |
| /tmp/rpg_*        |     | XP + 3 per tick     |     | XP >= level*100? |
| level, XP, class  |     |                     |     | advance level    |
+-------------------+     +---------------------+     +------------------+
                                   |                          |
                                   v                          v
                          +---------------------+    +------------------+
                          | HP Calculator       |    | Class Evaluator  |
                          | 10 - git changed    |--->| level thresholds |
                          | from git status     |    | Novice/Wizard    |
                          +---------------------+    | or Archmage      |
                                                     +------------------+

Configuration

Parameter	Type	Default	Description
xp_per_tick	integer	3	Experience points gained per statusline refresh interaction
level_up_multiplier	integer	100	Multiplied by current level to determine XP threshold for next level
class_tiers	object	{"Novice":1,"Wizard":5,"Archmage":10}	Level thresholds for class advancement
max_hp	integer	10	Maximum health points before subtracting uncommitted file count
mana_indicator_file	string	"package.json"	File whose existence determines mana state

Best Practices

1. Adjust XP gain for your interaction frequency - If your statusline refreshes very frequently, you may level up too fast. Reduce xp_per_tick to 1 for rapid-refresh environments so level progression feels earned over the course of a full session.
2. Use HP as a commit reminder - When your HP drops below 5, it means you have more than 5 uncommitted files. Treat low HP as a prompt to commit your work, creating a natural rhythm of small, frequent commits tied to the game mechanic.
3. Customize class names for your team - Replace Novice, Wizard, and Archmage with role-appropriate titles like Junior, Senior, and Principal, or use fun alternatives like Padawan, Jedi, and Master for a themed variant.
4. Extend mana to track multiple dependencies - Beyond package.json, add checks for Cargo.toml, go.mod, or requirements.txt so the mana indicator reflects your actual project dependency management status regardless of language.
5. Persist character across sessions - The default caches by session ID which resets for each new session. Change the cache key to use the project directory path so your RPG character persists across multiple Claude Code sessions within the same project.

Common Issues

1. HP always shows 10 - You either have no uncommitted changes or git is not available in the current directory. Verify with git status --porcelain that changes are detected and the output is not empty.
2. Level never advances - The XP threshold grows with each level. At higher levels, reaching the threshold takes many more interactions. Verify the cache file is being updated by checking its contents.
3. Class stays as Novice despite high level - The class update only triggers at the exact moment of leveling up to 5 or 10. If the cache was manually edited or corrupted, the class field may be stale. Delete the cache file to reset the character.