Make your own comparison

Run it

1. Install Python 3.10 or later and Poetry.
2. Get the code: git clone https://bitbucket.org/wotr/martial-bench.git, then cd martial-bench, poetry install and poetry run fetch-pcgen --accept-license.
3. Start a build from one on the roster: poetry run breakdown --new my_build --from sword_saint_elf. This writes resources/data/user/my_build.yaml.
4. Edit it: classes per level, ability scores, feats and other picks, weapons and gear. The file format is in docs/BUILD_FORMAT.md; the roster builds are good examples.
5. Make its page: poetry run breakdown my_build --open. It checks the build and every party member first (names, with the closest one on a typo, prerequisites, mythic ranks, unique items against where and when they can be found) and lists every problem at once. It also tells you when your build commits to the same classes as a roster build.
6. Pick the party by name: poetry run breakdown my_build --party Nenio Seelah Ember. A character is any YAML in resources/data/user, found by file name or by its name:. The page says which party it used; without --party it uses the default formation's.
7. Keep it open while you edit: poetry run breakdown my_build --watch checks and rewrites the page every time you save the build or a party member.
8. For the charts across builds, poetry run regen; to rebuild this site, poetry run site --out ../site.

Send it back

• Fork the repository, add your build file, run the tests (poetry run pytest) and open a pull request.
• A build joins the roster when it commits to classes no roster build does, or beats the roster build that does.
• Rule corrections are welcome too: say what the game does, with a source (a wiki page, a screenshot or a combat log).
• A new class or archetype needs its wiki page; it is added as data first, then the build that uses it.