-
Notifications
You must be signed in to change notification settings - Fork 5
Contributing to the Wiki
Authored wiki source lives in wiki/pages. Generated reference pages must not be edited by hand; they are rebuilt from Java registries, source-backed feature details, current command registrations, the Java scripting API, and the retained non-map Fandom audit snapshot.
Run the same validation as CI:
python tools/wiki.py check
python tools/wiki.py build --output build/wiki
python tools/wiki_quality.py sources wiki/pages
python tools/wiki_quality.py quality build/wiki --minimum-pages 250
python -m unittest tools/test_wiki_quality.py tools/tests/test_wiki_script_api.pyThe generated native-wiki checkout is written to build/wiki.
To refresh the page-level Fandom inventory deliberately:
python tools/wiki.py sync-baseline
python tools/wiki.py checkReview baseline changes before committing them. A changed Fandom page remains historical by default; moving information into a current page requires evidence in this repository.
Community-built map pages, download pages, and legacy map catalogs are outside this wiki's scope. The baseline synchronizer removes them before writing the snapshot. Do not recreate them as authored pages, aliases, screenshots, or imported media.
When adding or changing an authored page, update wiki/page-metadata.json with its evidence. Current feature documentation belongs in wiki/feature-details.json. Record any accepted screenshot in wiki/assets/media.json, including the source commit and confirmation that no community map artwork is present.
See wiki/README.md for deployment setup and ownership rules.
Applies to AC-Legacy 0.6.0 at source revision 439dbe5b157d. Current documentation is generated from the AC-Legacy-Mod source. Historical baseline links point to the AdventureCraft Fandom wiki, whose text is reported as CC-BY-SA. See Fact Checking and Provenance and Verification Status.
AC-Legacy Wiki
Use and authoring
Generated reference
Project and provenance