Class/role systems
Characters are assigned to distinct archetypes — tank, healer, damage dealer, support — each with a defined function in group content and a kit built around fulfilling that role. World of Warcraft's tank/healer/DPS trinity and Team Fortress 2's nine distinct classes both structure team play around complementary, interdependent roles rather than every player doing the same thing. Designers use class/role systems to create team-composition strategy (you need the right mix of roles to succeed), to give players a clear identity and specialization to master, and to enable asymmetric, non-interchangeable gameplay within a shared match. Key decisions: how rigid roles are (hard-locked classes versus flexible hybrid builds), balance across roles so none is strictly mandatory or useless, role queue systems that manage matchmaking around role scarcity, and how deeply each role's mechanics differ (surface reskins versus genuinely distinct playstyles). Pitfall: roles so narrowly defined that off-meta compositions are unviable removes strategic diversity — the healthiest systems allow some flexibility while still rewarding coordinated team composition.
- Dev effort: Large
- Timing: Real-time or turn-based
- Common in: mmo, hero-shooter