Quickstart
This page lists the steps on how to setup Rush.
Last updated
This page lists the steps on how to setup Rush.
Last updated
🚧 Rush is under heavy development. Expect bugs, crashes, breaking changes, and partial experiences so we can ship fast, break things, and iterate to bring you the best onchain game development experience. This page is Updated Daily.
Check for successful installation by running
If successfully installed it should print out the following
Using the Rush CLI, create a new Rush workspace to generate the Rush Manifest and initial Rush Gaming Blueprint.
Use the following command
For example
A successful Rush workspace creation will display the following
It will also create a new folder with the following folder structure
Where Rush.toml
is your Rush Manifest and world.toml
is your Rush Gaming Blueprint.
After creating your Rush workspace, modify the Rush.toml
and replace the fillers with actual values.
See References for recommended values.
Next, configure your Gaming Blueprint to define the data you are able to interact with in your Onchain World using the Rush SDKs.
For example the Gaming Blueprint above defines a 1 Entity player
, 1 Region base
, 1 Instance player
under the Region base
.
Now that you're done configuring your Rush Manifest and Rush Gaming Blueprint, it's time to deploy your Onchain World (migration) with the Rush CLI.
A successful deployment would yield a similarly looking output below.
To interact with your Onchain World, you need to add the rush_ecs_core
package and rush_ecs_sdk
package with the command below.
Import them into your Bevy game.
Instantiate the SDK and use it to interact with your Onchain World.
See Reference to see more available SDK functions.
Rush is currently at prerelease and only supports the .
Clone the repository to study a barebones scaffolding of a simple Player movement game.