Lattice Workshop - Step 2.1

Let's add some textures! We want to be able to create new entities with new textures later without touching the code, so let's store the texture urls on chain.

To store the texture URls, we'll add a Texture component. We could naively assign this component to all entities with texture and use the respective component values to render the texture. But this solution would lead to a lot of duplicated strings stored on chain. A better option is to store each texture only once by adding it to a "texture entity". We'll then refer to the ID of this texture entity in the Appearance component and only have to store one uint256 per entity.

The contracts/functions to add components of types UintComponent and StringComponent are already provided to us by the Starterkit code. All we need to do is initialize them in the contracts, client and lattice.config.ts to add them to the deployment.

First add the components to the contracts, then run yarn build in the contracts folder to rebuild the ABI and generate Typescript types using Typechain. Next, add the components to the client and add a new mapping to sync the contract state with the client state.

You can confirm the mapping was successful if you receive the event logs in the developer console of your local game instance after restarting your node. In the next step we'll add client systems to render the textures.