MUD config
Certain CLI commands, such as mud tablegen
and mud worldgen
require the MUD configuration file.
This file needs to be named mud.config.ts
and be in the same folder as your foundry.toml
file.
The config is used to define:
- The tables in your project in the
tables
object of your configuration. - The namespace that systems and tables will be deployed in.
- The
System
s in your project. By default, the deployer will find all Solidity matching*System.sol
(so any file ending inSystem.sol
, in any folder) and deploy them as publicSystem
. If you want greater control over your systems (to change their public access or their name), you can use thesystems
object in the config. - The modules that will be installed in the
World
.
The is an example of a World
config:
import { defineWorld } from "@latticexyz/world";
export default defineWorld({
excludeSystems: ["System3", "System2"],
worldContractName: "CustomWorld",
namespace: "mud",
systems: {
IncrementSystem: {
name: "increment",
openAccess: true,
},
},
tables: {
Counter: {
schema: {
value: "uint32",
},
key: [],
},
Tasks: {
schema: {
id: "bytes32",
createdAt: "uint256",
completedAt: "uint256",
description: "string",
},
key: ["id"],
},
},
deploysDirectory: "./mud-deploys",
});
Global configuration keys
The global configuration keys are all optional.
-
namespace
: astring
: which namespace to deploy the resources defined in the config into. The default value is the ROOT namespace. -
tables
: a record of tables. The keys in the record are table names. The value is a record of table properties (opens in a new tab).-
schema
(record): The keys of this record are the field names in the data, which includes both the key fields and the value fields. By convention, these keys start with a lowercase letter. The values are strings that contain the data types of the fields. Note that this is the sole required field, all the others are optional. -
key
(list): A list of theschema
fields that are the key for that table. If you want a singleton table, use an empty list (as inCounter
table above). -
type
(eithertable
oroffchainTable
): The table type. The default istable
, which is a table stored onchain. If you specifyoffchainTable
, the table's data is only available offchain through events.
-
-
systems
: a record of system definitions. The keys in the record are file names without the.sol
extension. For example, if your system is namedTestSystem.sol
, useTestSystem
as the key.The value is a record of system configuration properties:
-
registerFunctionSelectors
(optional, defaulttrue
): abool
. Whether we want to automatically register thepublic
functions of theSystem
as function selectors -
openAccess
(optional, defaulttrue
): abool
. If set tofalse
, only the systems in the same namespace and the addresses or systems listed in theaccessList
array have access. -
accessList
(required if openAccess isfalse
): an array ofstring
. Each address in the array will be granted access to this system, allowing them to call it.
-
-
excludeSystems
: an array ofstring
: which systems to not deploy, even if their name ends with “System”. -
modules
an array of module definitions: each module definition has aname
,root
(optional), andargs
key.-
name
: Name of the module to install. The same module can be installed multiple times. This should be the name of the contract file without.sol
(eg: if the file is namedDopeModule.sol
, the name of the module isDopeModule
) -
root
: whether to create aroot
module or not.root
modules have access to all tables and are not bound to namespace restrictions. -
args
: a list of arguments to be sent to theinstall
function of the module. In this array, you can use the functionresolveTableId
. This function will turn a table name from your config into its low-level ID in the World. It is useful to pass references of a table to a module.
-
-
codegen
: a record of code generation options.worldInterfaceName
astring
: The name of the interface for theWorld
. The default value isIWorld
.worldgenDirectory
astring
: The directory for system and world interfaces. The default value isworld
.
-
deploy
: a record of deployment options.-
postDeployScript
astring
: Script to execute after the deployment is complete. This script must be placed in the forge scripts directory (seefoundry.toml
) and have a.s.sol
extension. The default isPostDeploy
. -
deploysDirectory
astring
: Which folder to put the deployment artifacts into after deployment. The default is./deploys
. -
worldsFile
astring
: JSON file for the chain toWorld
deploy address mapping. The default is./worlds.json
.
-