dojo-model

To define Starknet game state with Dojo, you generate Cairo structs annotated with the #[dojo::model] attribute, configuring specific fields with #[key] for unique entity identification and deriving necessary traits like Drop and Serde for on-chain compatibility.

The ECS pattern for Starknet game models separates game state into distinct components. You define models as data structures, using key fields to identify unique entities, which the Dojo engine then manages within its global ECS framework.

You create player-owned models by defining Cairo structs with multiple #[key] fields to establish composite keys. This allows the Dojo engine to map specific state components, like inventory items, uniquely to individual player entities.

No, you do not need to manually implement Serde and Drop traits. Generating Dojo models automatically includes the necessary trait derivations to ensure your game state structures are fully compatible with the Starknet on-chain environment.

To structure global singleton state in a Dojo game, generate a Cairo model without entity-specific key fields. This approach ensures the Dojo engine maintains a single global instance for game-wide configurations or shared state variables.

Yes, you can use it to generate various state structures, including standard game entities, player-owned models, and composite components. It handles the required ECS configurations and key definitions for any Starknet game data structure.