Living folio · System
4. Cross-Class Skills System
What Cross Class Skills Are Cross class skills are not team techniques performed by two different party members. A cross class skill is a single character skill that emerges when one adventurer develops their base class deeply enough to begin integrating the logic of a second, specific class path. These...
Overview
What Cross-Class Skills Are
Cross-class skills are not team techniques performed by two different party members.
A cross-class skill is a single-character skill that emerges when one adventurer develops their base class deeply enough to begin integrating the logic of a second, specific class path.
These skills represent a real hybrid discipline: - not a generic multiclass bonus - not a party combo - not “class A and class B acting together” - not a borrowed trick from another guild
A cross-class skill exists when a character’s training, instincts, and recognized competency begin to form a stable pattern that belongs to the overlap between two class traditions.
That overlap must be narrow, coherent, and real.
What Cross-Class Skills Are Not
Cross-class skills are not: - teamwork maneuvers requiring two party members - broad multiclass access to any second class - temporary stance changes - item effects - spells or techniques anyone can imitate casually - generic “hybrid bonuses”
If two different party members fight well together, that is tactics.
If one character develops a stable hybrid discipline recognized by the system, that is a cross-class skill.
Core Access Rule
A character may only learn a cross-class skill from a pairing that includes their current base class.
Example: - A Rogue may learn from Hunter + Rogue - A Rogue may learn from Rogue + Vanguard - A Rogue may not learn from Mage + Alchemist
Cross-class skills do not let a character freely access all classes.
They only allow development into one of the pairings connected to their base class.
Guild Access Rule
A valid character may learn a cross-class skill through either of the two guild traditions tied to that pairing, provided they meet the prerequisites and are accepted for training.
This means the skill can be approached from either side of the overlap.
Example: - A Rogue pursuing Hunter + Rogue may begin that training through the Rogue-side guild tradition or the Hunter-side guild tradition - A Vanguard pursuing Vanguard + Ritualist may begin through the Vanguard-side or Ritualist-side tradition
This preserves social and institutional flexibility while keeping the skill itself class-bound.
Cross-Path Binding Rule
The first time a character successfully learns a cross-class skill from a pairing, they become bound to that cross path.
This is the most important rule in the cross-class system.
Once that first cross-class skill is learned: - the character is now recognized as pursuing that specific pairing - future cross-class development may only come from that same pairing - the character may not begin a different cross-class pairing later
This is not just an institutional restriction. It reflects the fact that real hybridization changes: - training habits - body logic - combat instincts - mana behavior where relevant - role identity
A character cannot meaningfully begin multiple incompatible cross paths without breaking system coherence.
What Cross-Path Binding Means In Practice
A base class has access to only the pairings connected to it, but it may only ever commit to one of them.
Example: - A Rogue has access to: - Hunter + Rogue - Rogue + Vanguard - If that Rogue learns their first Hunter + Rogue cross-class skill, they are now bound to the Hunter cross path - From then on: - they may continue learning Hunter + Rogue cross-class skills - they may not begin Rogue + Vanguard cross-class development
So the first learned cross-class skill is not just a skill choice.
It is a path choice.
Why The System Works This Way
This rule exists to preserve: - class identity - hybrid identity - setting coherence - progression weight - training consequence
Without binding, cross-class development becomes a loose shopping list.
With binding, it becomes a meaningful commitment.
A cross-path should feel like: - a secondary specialization - a transformation of fighting logic - a real branch of identity
not: - a pile of convenient extras
How Cross-Class Skills Differ From Base Skills
Base Class Skills
Base class skills define the main identity of a class.
They answer: - what this class is - how this class fights - what this class contributes normally
Cross-Class Skills
Cross-class skills define what happens when one class develops along a very specific secondary track.
They answer: - what this class can become in a narrow hybrid direction - what overlap produces a new discipline - what this person can now do that their base class alone could not
Cross-class skills should never overshadow the base class itself.
They extend identity. They do not replace it.
Cross-Class Skill Design Rule
A proper cross-class skill must feel like a true fusion.
It must not be: - class A skill plus class B skill - a lazy combination - a generic boost to versatility
It must: - require foundations from both class traditions - create a stable competency unique to that overlap - solve problems in a way neither class alone naturally does - remain narrower than a full base class identity
Pairing Map
The approved cross-class pairings are:
- Hunter + Rogue
- Hunter + Craftsman
- Rogue + Vanguard
- Vanguard + Ritualist
- Ritualist + Mage
- Mage + Alchemist
- Alchemist + Priest
- Priest + Craftsman
No other pairings exist in the current system.
Pairing Access By Base Class
Hunter
- Hunter + Rogue - Hunter + Craftsman
Rogue
- Rogue + Hunter - Rogue + Vanguard
Craftsman
- Craftsman + Hunter - Craftsman + Priest
Vanguard
- Vanguard + Rogue - Vanguard + Ritualist
Ritualist
- Ritualist + Vanguard - Ritualist + Mage
Mage
- Mage + Ritualist - Mage + Alchemist
Alchemist
- Alchemist + Mage - Alchemist + Priest
Priest
- Priest + Alchemist - Priest + Craftsman
Each base class has access to exactly two possible cross paths, but may only ever be bound to one of them.
Example
A Rogue has two potential cross paths: - Hunter + Rogue - Rogue + Vanguard
If that Rogue learns their first Hunter + Rogue cross-class skill: - they are now bound to the Hunter cross path - they may continue learning Hunter + Rogue cross-class skills - they may not later begin Rogue + Vanguard cross-class development
That does not mean they stop being a Rogue.
It means their Rogue identity now grows in a specific hybrid direction.
Practical Writing Rule
When writing or using cross-class skills, always remember: - the skill belongs to one character - the pairing explains the hybrid logic - the first cross-class skill learned determines the character’s cross path - no character may pursue more than one pairing
This keeps the system readable, grounded, and narratively meaningful.
Connected records
