Glossary

Terms used throughout this documentation.

Term	Definition
`spec`	A YAML file describing a set of DataSheet changes to apply.
`schema`	The set of valid attributes and types for a given entity type.
`entity`	A single game object defined by a schema (e.g., an item, quest, or NPC).
`task`	A step within a quest that defines a player objective.
`body`	The type-specific content section of a quest task, nested inside `<Body>` in XML.
`header`	The common quest task fields shared by all task types (e.g., id, name, type).
`v92`	The current supported game protocol version. Earlier versions (v90, v86) have limited schema support.
`DataSheet`	The game’s binary data format; DSL reads and writes DataSheet XML files.
`patch recipe`	An informal term for a spec file that modifies existing entities rather than creating new ones.
`flag item`	A boolean-like enum field that enables or disables a feature on an entity.
`discriminator`	The field that determines which task type variant applies (the `type` field on quest tasks).
`body element`	An XML element inside `<Body>` that holds type-specific task data.
`XML Reference`	The tab view on schema pages showing the underlying XML element names and structure.
`Korean element`	An XML element whose name is written in Korean, as used in the game’s native DataSheet format.
`package`	A named group of spec files that can be imported and reused across projects.
`definition`	A reusable YAML structure declared with `$define` and referenced with `$extends`.