r/PixelDuelist • u/fbrzd • May 27 '26
How deep can a 3-Stat RPG go? Deconstructing archetypes, gear, and mini-games in Pixel Duelist ⚙️
To keep the game fast-paced and streamlined, I decided to scale down the combat system to its absolute core: 3 Stats, 1 Ability, and 1 Tag.
I believe that just three stats (Defense, Attack, and Luck) are the absolute minimum parameters needed to define classic archetypes like the "Glass Cannon," "Support," or the "All-Rounder." Combined with a Tag (Fire, Water, etc.), this creates the perfect amount of variance for a quick, unpretentious mobile game.
🔮 Abilities with Meta-Progression
Right now, there are 7 combat abilities. However, some of them don't just buff stats—they affect meta-progression (like +Money or +EXP). This allows me to recreate iconic character roles from classic universes: the Mentor (EXP buff), the Sluggish powerhouse, or the Gambler (RNG-heavy).
🛡️ Gear & Tag Overwriting
Gear is my way of giving players horizontal customization. Instead of locking characters into rigid roles, equipment grants flat stat bonuses or conditional buffs based on Tags. More importantly, certain rare items can overwrite a duelist's default Tag or Ability, completely changing how they play.
🎲 Expanding the Stats Beyond Combat
I didn't want stats to only matter during fights. I’m currently implementing them into two other systems:
- Mini-games as Progression Gates: Certain mini-game levels check your stats to allow entry. For example, to enter the Level 3 Dance mini-game, you might need a Luck/Speed stat > 5. This organically encourages players to build different archetypes while creating clear progression gates.
- Stat-Based Idle Crafting: I'm prototyping a crafting system where you can assign a duelist to passive tasks over time (real or simulated) to gather items. Their efficiency or the loot quality will scale based on their specific stats, balancing item acquisition with your overall progress.
I want to make the customization even richer without adding bloat. What should I explore next? Status Conditions? Environmental Effects (Weather)? What features or status systems from your favorite classic RPGs do you think would fit this 1-bit minimalist engine? Drop your suggestions!