Getting started
SDK vocabulary
Distinguish recurring concepts in the guides and API contracts.
Read contracts unambiguously
| Term | Meaning in this manual |
|---|---|
| Kit / installed SDK | The kit builds your project; the installed SDK lets it run with the game. |
| Mod / model / instance | A mod is a package; a model describes a signal type; an instance is a signal placed in the game. |
| Indication / aspect / reason | An indication associates a displayable result with its reason. Your enums give those values meaning. |
| Observation / snapshot | A copy of requested data at a point in time. Retaining it does not update it. |
| Unknown / absent / not requested | Three distinct situations described by each contract. None automatically means zero, false or clear. |
| Identity / generation | An identifier names an object in its documented context; a generation helps distinguish worlds or sessions. Revalidate references after loading. |
| Permission / appearance | A driving instruction and an image are independent. Changing an image does not create permission. |
| Ticket / terminal result | A ticket tracks a deferred request. Wait for or inspect its result; do not repeat a mutation merely because it is still pending. |
| Simulated time / real time | The game date follows pause and acceleration. Real duration measures work or waiting; these are two different time scales. |
| Assembly / activation / publication | Producing files, installing them for the next launch and distributing them are three distinct operations. |