Skip to content
A Truffle box for a barebones Oasis Game
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
contracts
core
migrations
scripts
src
test
.babelrc
.gitignore
README.md
package.json
secrets.json
server.js
truffle-box.json
truffle-config.js
webpack.config.js

README.md

Making Games with Oasis

This example project demonstrates how to build a turn-based game, Tic-Tac-Toe, on the Oasis devnet. Our Gaming SDK (inspired by boardgame.io lets you define a core set of game rules in Rust that can be run locally for in-browser testing, then deployed the Oasis testnet for live games, all without needing to touch WebAssembly or web3 (though under-the-hood we use both).

Here are the interesting bits of this Truffle box:

  1. core/game is where your game logic is defined. This core module is imported into a browser-compatible WebAssembly module in core/client, and an Oasis-compatible smart contract in contracts/server.
  2. contracts/server is where your smart contract is defined. It imports your core game logic and creates a game server contract that manages game instances running on the Oasis testnet.
  3. src is where your frontend code is defined. You should only need to edit src/components/board.js and src/components/board.css to create new games.
  4. scripts contains helper scripts to get you started. These are described in more detail below.

Installation

This Truffle Box is designed to run from within your Contract Kit container. If you haven't already, pull the oasislabs/contract-kit image from Docker Hub.

  1. Launch your Contract Kit container:
    • docker run -v "$PWD":/project -it oasislabs/contract-kit:latest /bin/bash

The remaining steps are meant to be run in a shell inside your new oasislabs/contract-kit container.

  1. Install wasm-bindgen: cargo install wasm-bindgen-cli --vers 0.2.37 (this can take some time).
  2. Create a directory for your new project: mkdir (project name) && cd (project name)
  3. Unbox this repo: truffle unbox oasislabs/game-box
  4. (optionally) Start a local Parity instance for debugging: ./scripts/start-parity.sh
    • (Note: This will launch Parity with very loose network settings -- feel free to restrict those to localhost if you don't want to test with other machines on your local network)

Specifying credentials

If you want to deploy on Oasis, make sure your mnemonic is defined in secrets.json. This file is not tracked by your repo, but it's imported by Truffle during migration and frontend compilation. The default Contract Kit mnemonic is already there, ready to use.

Creating your game

Once this example has been unboxed, you're ready to start building your game. This section is a crash-course for getting started quickly; for a thorough overview the architecture of the game framework, check out of Gaming SDK documentation.

TL;DR: In most cases, the only files you'll need to edit are core/game/src/lib.rs (with your move and flow functions) and src/components/board.js (with your game UI) -- everything else should be done for you!

API

Our APIs let you describe broad types of turn-based games with little more than a state description, and a handful of flow functions. A complete game definition for our example game (Tic-Tac-Toe) can be found in core/game/src/lib. Games are comprised of the following pieces:

  1. State: Your game state can be any JSON-serializable data structure, and is defined as a Rust struct.
  2. Moves: Your moves are defined in a Rust trait, wrapped by our #[moves] macro. A move is a function that takes in a state and an action, and produces a new state.
  3. Flow: Flow methods describe how your game progresses over time. You can define hooks end_game_if, which take your game state as an input, and tell the game engine if the game is finished. See below for a list of the available flow methods.

Moves

Move methods are entirely user-defined, and you can have as many as you like. For Tic-Tac-Toe, there is only one possible move, and so our Moves trait looks like:

#[moves]
trait Moves {
  fn click_cell(cell: &mut UserState<State>, player_id: u16 args: &Option<Value>) -> Result<...> {
    ...
  }
}

The game framework takes these move definitions and automatically creates corresponding Javascript methods that you can call from within your client-side JS code as follows:

class Board extends React.Component {
  ...
  onClick = id => {
    if (this.isActive(id)) {
      this.props.moves.click_cell(id)
    }
  };
  ...
}

Since Rust is statically-typed, and move methods are user-defined, we cannot know in advance how many arguments you'll need to pass from JS into your move methods. For this reason, all move methods take an optional, untyped, JSON array of arguments as input (args: &Option<Value>). It's up to you to complete the deserialization step inside your own code, so you can assign a user-defined type to these inputs, i.e:

fn click_cell(state: &mut UserState<State>, player_id: u16 args: &Option<Value>)
            -> Result<(), Box<Error>> {
    if let Some(value) = args {
        let id = value.as_array()
            .and_then(|arr| arr.get(0))
            .and_then(|cell| cell.as_u64())
            .and_then(|cell| Some(cell as usize))
            .ok_or(Box::new(Errors::InvalidCell))?;
   ...
}

Once your inputs are parsed, you can then mutate the state you're given with whatever changes are necessary. In Tic-Tac-Toe, we update a cell with the player ID of the active player. Here's how all the above steps come together to make a complete move method.

fn click_cell(state: &mut UserState<State>, player_id: u16, args: &Option<Value>)
            -> Result<(), Box<Error>> {
    if let Some(value) = args {
        let id = value.as_array()
            .and_then(|arr| arr.get(0))
            .and_then(|cell| cell.as_u64())
            .and_then(|cell| Some(cell as usize))
            .ok_or(Box::new(Errors::InvalidCell))?;
        match state.g.cells[id] {
            -1 => {
                state.g.cells[id] = state.ctx.current_player as i32;
                Ok(())
            },
            _ => Err(Box::new(Errors::InvalidCell))
        }
    } else {
        return Err(Box::new(Errors::InvalidCell))
    }
}

Flow

Flow methods are more constained than move methods. The game engine exposes a handful of hooks that you can implement inside your Flow trait to control how a game evolves over time. As an example, in Tic-Tac-Toe, there are only three components to the game flow:

  1. The initial state should be an empty grid.
  • Note: initial_state gives you a seed, which you can use to construct a pseudo-random number generator. You'll only care about this if you're interested in making a game that uses randomness.
  1. Turns should alternate.
  2. When a victory condition is met, the game should end.

We express those components in the following Flow trait:

#[flow]
trait Flow {
    fn initial_state(&self, seed: Option<u128>) -> State {
        State {
            cells: [-1; 9]
        }
    }

    fn end_turn_if(&self, _: &UserState<State>) -> bool {
        // End the turn after every move.
        true
    }

    fn end_game_if(&self, state: &UserState<State>) -> Option<(Option<Score>, Value)> {
        // If there's a three-in-a-row, then a player has won.
        if let Some(pos) = is_victory(state.g.cells) {
            let winner = state.ctx.current_player;
            return Some((Some(Score::Win(winner)), json!({
                "winner": winner,
                "winning_cells": pos
            })));
        }
        
        // If all the cells are filled, then it's a draw.
        if state.g.cells.into_iter().all(|c| *c != -1) {
            return Some((Some(Score::Draw), json!({
                "draw": true
            })));
        }
        None
    }
}

The end_game_if method has a trickier interface, since it's responsible for assigning a value to the final game state (which are be useful for bots, more docs forthcoming). Additionally, the final game state is entirely user-defined, and thus must also be stored as a Value (an arbitrary JSON object).

Here's a complete list of available flow methods. For complete signatures, take a look here:

  1. initial_state - Generates the first game state, before any moves have been made.
  2. end_turn_if (default true) - Given a game state, returns true if the active player should transition to the next player in the turn_order
  3. end_game_if - Given a game state, has the game completed? If so, return a gameover value.
  4. on_turn_begin - Gives you the option to update the state at the beginning of every turn.
  5. on_turn_end - Gives you the option to update the state at the end of every turn.
  6. on_move - Gives you the option to update the state after every move.
  7. can_make_move - Is the given player allowed to make a move? This is useful for games where many players can make moves at the same time (i.e. draw phases of card games).
  8. allowed_moves - List the move types (i.e. "click_cell") that the given player is allowed to make. This does not enumerate all possible moves.
  9. optimistic_update - Should a given game event be executed client-side and on-chain concurrently? In perfect-information games, this can give latency benefits.
  10. get_current_players - For games that require more sophisitcated turn orders (beyond Round Robin, which is the default), you can use this method to return a Vec of players that are allowed to make moves in the current turn. For an example of a game that uses this, check out our Poker demo.

You're free to implement as few or as many of these as you like. In the future, we'll be adding more opinionated flow methods to make it easier to make more complicated games (we currently only have a small subset of those available in boardgame.io, for example).

Building + Migrating

Building is separated into three stages, each with a corresponding build script. From the repo root:

  1. Build Rust dependencies: ./scripts/build-crates.sh
  2. Migrate contracts onto a testnet: truffle migrate --network oasis
  3. Build frontend components: truffle exec ./scripts/build-frontend.js --network (your network) --confidential true

It's important that (3) always be performed after (2), and with truffle exec, because it depends on the address of your deployed contract, which Truffle automatically determines.

Once everything is built and migrated, you're ready to play!

Playing

This box currently contains the following game modes:

  1. Singleplayer: Two boards are rendered on the same screen, and a single user makes moves for both. This is useful for debugging your core game logic.
  2. Two Player (On-Chain): Production time! This game mode allows for multiple players, or bots, to compete using a game contract running on Oasis.

Singleplayer

To debug your game in singleplayer mode, first complete the installation steps above, then perform the following steps:

  1. npm start (you can do this in another shell, outside of Contract Kit)
  2. Navigate to localhost:8080/singleplayer in your browser (or whichever port you've chosen to use)

This mode launches a local game server on port 8080 (note: this is an HTTP server, not an Ekiden gateway -- there is no blockchain involved in this game mode).

Multiplayer

To play a complete end-to-end, on-chain game with friends, there are a few more steps. We're working on a browser-based game creator that will make it super easy to launch games and share game links with your friends. In the meantime, this box comes bundled with a game creator CLI tool that you can use for testing:

  1. To create a new game on the Oasis devnet: truffle exec ./scripts/create.js --num-players (number of players)
    • This script will generate a series of "magic" links, one for each player.
  2. npm start (you can do this in another shell, outside of Contract Kit)
  3. Open up the magic links in your browser. Each player must currently use a different Oasis account, which means you should open these links in separate private windows (since the accounts are stored in your browser's localStorage).

If your players are using different computers, make sure that both the web server and the testnet are accessible to all parties -- this might require updating the networking configuration in the config section of truffle-config.js.

If you're using the Oasis testnet, you will not need to update any networking configuration.

You can’t perform that action at this time.