Community Library
The Community Library holds movements developed and contributed by Saberists, schools, and clubs outside the founding Core and Extended libraries. Community movements are credited to their contributing school or individual. Over time, a movement here may be promoted into the Extended or Core libraries.
Community Libraries
Each school contributes under its own prefix, so a movement's code carries its origin with it. Everything below is written in Saber Standard Notation, which is what lets one school read another's work without adopting its curriculum.
| Movement | Contributor | Focus | Reference |
|---|---|---|---|
| GCM-A-S — Swashbuckler Style | Gulf Coast Saber Training | CM-A with the attack changing hands every two steps, run as twelve | Full written notation on this site |
| GCM-A-L — Longsword Style | Gulf Coast Saber Training | CM-A carried with a blade lock on the 3 line | Full written notation on this site |
Contributing a movement
If your school or club has built its own CM and wants to share it with the wider SaberCraft community, see Contribute for how submissions work.
Schools building their own internal CM libraries first — without submitting to the shared standard — can also see For Schools and the worked example below.
Creating your own system
Build and customize your own system using your school's program, then share it with the community.
Any theatre or saber choreography club work can be converted into a library you can use to structure your classes. The same library can serve as your school's own collection of staged choreography battles, and the same approach can be used to create your own LUMINA Battles if you want to introduce game play.
To get started, use the Create Your Own CMs worksheet.
The choreography is not the standard; the notation language is. That distinction is what lets schools collaborate without becoming identical. You keep your own movement library, naming structure, ranking system, and teaching style, and still write it all in a notation any other school can read.
A worked example: NY Kendo School
"NY Kendo School" is a fictional school, used here to show how an independent group documents original movement in Saber Standard Notation. It names its movements KS-A, KS-B, KS-C under its own prefix rather than using SaberCraft's CM codes, and the notation stays readable either way.
Its first sequence, KS-A "Crosswind Exchange":
| Player | Step 1 | Step 2 | Step 3 | Step 4 | Step 5 | Step 6 |
|---|---|---|---|---|---|---|
| Saberist A | 11 | 1 | 9 | 3 | 7 | 5 |
| Saberist B | 11P | 1P | 9P | 3P | 7P | 5P |
The sequence demonstrates:
- a fixed attacker and defender across the whole exchange
- a direct attack-to-parry pairing on every step
- the three opposite target-line pairs taken in turn: 11 and 1, then 9 and 3, then 7 and 5
Saberist A holds the attacking role for all six steps while Saberist B answers each line, which keeps the pattern readable at slow speed. The point is not the choreography itself but the interoperability: a SaberCraft instructor could read this sequence, and an NY Kendo School instructor could read a SaberCraft CM.
A shared ecosystem
In a larger choreography ecosystem, schools might publish side by side:
| School | Example library |
|---|---|
| SaberCraft | CM-A through CM-X |
| NY Kendo School | KS-A through KS-T |
| Performance Team | Stage Exchanges |
Each library remains unique. The notation provides the common structure that makes choreography readable across communities.