📄️ The minimum concepts you need
For designers: you do not need to understand code generation. Remember the points below so you can talk with engineering and avoid common mistakes.
📄️ Header meanings and common mistakes
Header rows at a glance
📄️ Client / server field groups
In the same table, client and server can receive different columns. This is controlled by ##group (and table-level groups set by engineering).
📄️ How to fill complex structures
Coordinates, costs, reward lists, skill effects (polymorphism), and similar fields have headers more complex than “one number per column.” Fill from the sample sheet engineering gives you; the patterns below explain how to read them.
📄️ Collaboration checklist with engineering
Quick self-check before submit or QA. The more you tick, the less rework.