Documentation notice
AI disclosure
AI-assisted tools have been used to help draft, reorganize, and audit parts of this wiki.
The documentation is a work in progress. AI-generated suggestions can be incomplete, outdated, or wrong, especially when describing platform requirements, configuration behavior, and console commands. Do not treat the presence of a page as proof that every claim has been manually verified.
This disclosure applies to the wiki content. It does not mean that the TaystJK software itself was generated by AI.
How claims are grounded
Claims backed by code link to pinned source, so you can check them. Claims that source cannot prove, such as how an external service behaves, are called out where possible.
The console reference is not written, it is extracted. All 2,017 cvars and commands are parsed out of the engine source, and each entry links to the exact line that registers it. Origin is resolved from the commit history of every upstream this fork descends from, rather than assumed. Nothing there is an AI summary of what a cvar probably does.
Hand-written pages cite source. Where a page states how something behaves, it links the line in GitHub’s blame view at a pinned commit, so the claim can be checked and so it stays attached to the code it came from. Where a page relies on someone else’s documentation it says whose, rather than absorbing it.
What could not be verified is marked rather than guessed at. 1,644 of the 2,017 entries carry a needs review status, and 774 have only medium-confidence provenance. Those figures are published on the audit page instead of being rounded away. When a page cannot answer something from source, the convention is to leave a visible note saying so rather than write a plausible sentence.
What is checked automatically
Every change runs a suite that fails on:
- reference data that no longer matches the registrations in the engine source
- generated pages edited by hand, or out of step with the data
- broken internal links, and pages missing a description
- the site failing to build
That catches drift and breakage. It cannot catch a sentence that is well-formed and wrong, which is what the needs review markers and the source links are for.
Known limits
Pages describing behaviour that cannot be read from source, such as how something feels to play or what a server operator sees in practice, rest on weaker evidence than the rest, and several were corrected after the fact when the original claim turned out to be an assumption. If a page tells you something you can test, and your test disagrees, trust your test.
If you find an error, please open an issue or submit a correction on GitHub.
Last changed History Edit this page on GitHub