[ ] Original files and database backup kept separately
[ ] Client and server versions noted
[ ] Text encoding and expected export formats noted
[ ] New VNUMs checked against existing definitions and ranges
[ ] Upgrade targets exist in the intended item table
[ ] Changed shop, drop and quest references reviewed
[ ] Diff contains only intended changes
[ ] Import/build steps tested in a staging environment
[ ] One representative in-game path tested
[ ] Rollback steps written before touching productionReview one change at a time
If you change an item's ID, its upgrade path and a drop table together, write down how they connect. When a test fails, return to the smallest reproducible case instead of applying more unrelated edits.
Make a result reviewable
Keep the input example, the output, the diff and the verification steps together. A useful forum answer should explain what changed and how the author checked it.
Start with a free proto check for the supported static checks. For problems beyond it, describe the symptom in Support. Share additions to this checklist from your own workflow.