dojo-model

To define a Dojo model, annotate a Cairo struct with #[dojo::model], place key fields first, and derive Drop and Serde traits. This ensures the struct maps correctly to on-chain entity components and integrates with the world read/write API.

Dojo models require Drop and Serde trait derivations to function correctly. If your model contains nested types, those nested types must also implement the Introspect trait to ensure proper serialization and compatibility with Starknet storage.

Create a composite-key model by defining a Cairo struct with multiple key fields ordered correctly, such as player and location. Annotate it with #[dojo::model] and derive Drop and Serde to query resources by combined entity keys.

Yes, you can define a global singleton model for game settings by creating a Dojo model without entity key fields. This pattern stores global configuration state on Starknet while maintaining standard Drop and Serde derivations.

Dojo model state read/write failures often stem from missing key annotations, incorrect key ordering, or lacking required Drop and Serde derivations. Ensure all nested types implement Introspect for world API compatibility.