Movement and technique access
Start by identifying which current actions visibly consume Chi and whether they change movement or technique behavior.
Resource systems · two official tutorials · checked July 28, 2026
Short answer: Chi and Chakra are separate gauges. Official text defines Chi as a maneuvering and hidden-technique resource with an overextension risk; the Chakra tutorial confirms a separate gauge but leaves its exact build, spend, and recovery cycle to the current in-game lesson.

| Question | Chi | Chakra |
|---|---|---|
| Official tutorial status | Dedicated Chi Gauge tutorial | Dedicated Chakra 101 tutorial |
| Confirmed purpose | Maneuvering and hidden techniques | A separate gauge; exact lifecycle is not enumerated in public text |
| Confirmed risk | Overextension can leave the fighter unbalanced and vulnerable | No equivalent public-text warning captured |
| Best first test | Spend toward depletion and observe current movement, techniques, defense, and recovery | Reset, change one action, and record what visibly builds or spends the gauge |
| Do not assume | Universal costs, recovery time, or character exceptions | Gain sources, costs, duration, recovery, or a relationship with Chi |
This comparison states only what the linked official text supports. “Not enumerated” does not mean a mechanic is absent; it means the current public text is not enough to publish it as fact.
CHI
The official tutorial gives Chi a concrete identity: it is a spendable resource tied to maneuvering and hidden techniques. Its unique learning problem is not merely “how do I fill a bar?” but “how can I test the official overextension risk without assuming a specific warning state?”
Start by identifying which current actions visibly consume Chi and whether they change movement or technique behavior.
The official wording supports a risk/reward test, but not an invented warning icon, disabled-action list, or numeric punish window.
CHAKRA
The public Chakra post confirms the separate gauge and tutorial, but does not provide the same purpose statement or overextension warning as Chi. Chakra therefore has a different evidence task: document its lifecycle before assigning it a universal role.
Reset Training, then test movement, normals, specials, taking a hit, blocking, and support calls one at a time. Record the first visible gauge change.
Use only a command named by the live lesson or command list. Record fighter, input label, starting gauge, cost, and result.
After spending, stop changing variables. Watch whether recovery is automatic, action-driven, round-driven, or absent in that exact test.
A useful result reads like: “On this build, with this fighter and support, action X changed the Chakra display from state A to state B under hit/block condition C.” It should not read like a universal mechanic definition after one observation.
The separate tutorial names are not proof that one gauge feeds, blocks, replaces, or converts into the other. Record the two displays independently, then connect them only when one controlled action visibly changes both.
For movement and support context, continue to the Flow System guide. Flow, Chi, and Chakra should remain separately labeled in notes and search pages.
The official tutorial series treats them as separate gauges. Chi is explicitly described as a resource for maneuvering and hidden techniques, with an overextension risk. The public Chakra post confirms a separate Chakra Gauge lesson but does not publish its full gain, spend, or recovery rules in text.
The official Chi tutorial connects Chi to maneuvering and hidden techniques and warns that overextending it can leave a fighter unbalanced and vulnerable.
The public Chakra post does not enumerate a universal build-and-spend cycle. Use the current in-game lesson and test one action at a time before recording a rule.
The linked official text does not define a universal interaction. Keep the gauges separate until the current HUD or lesson visibly demonstrates one.
No. Exact gain, cost, duration, recovery, and character exceptions require a current-build capture rather than inference from tutorial titles.
Compare the two gauges here, then use the Flow guide to place each resource inside a complete movement and support practice route.