The contains original synthetic text data and reports. It contains no game client, server binary, private serverfiles, credentials or third-party assets.
Inside the archive
README.md
LICENSE.txt
broken/item_proto.txt
broken/item_names.txt
fixed/item_proto.txt
fixed/item_names.txt
expected/broken-report.json
expected/fixed-report.json
manifest.jsonThe broken example intentionally contains a duplicate VNUM, a missing refine target and a names mismatch. The fixed example removes those particular problems. They are tiny teaching tables, not complete engine-ready exports and not a server installation.
Use it in three steps
1. Keep the broken/fixed folders separate. Open the free checker and select the two files from broken.
2. Compare the findings with expected/broken-report.json. Then select the two files from fixed and rerun.
3. Make one deliberate change and explain what changed in the report. Do not replace production data with these fixtures.
The manifest records SHA-256 checksums of the sample data and expected reports so you can identify the exact fixture being discussed. The included licence applies to this original kit; it does not grant rights over another project's serverfiles.
Build your own small reproduction
Reduce a real problem to the minimum necessary rows and use invented names/IDs where their values are not essential. Include the format, encoding, expected result and exact steps. Verify that the reduced example still fails in the same way.
This approach makes support threads more useful than posting an unexplained large archive. Reply with an improved synthetic fixture if it demonstrates a genuinely different parser case. Describe whether the test concerns data structure, a reference or an engine-specific runtime rule.