Book Image

Game Development with Rust and WebAssembly

By : Eric Smith
Book Image

Game Development with Rust and WebAssembly

By: Eric Smith

Overview of this book

The Rust programming language has held the most-loved technology ranking on Stack Overflow for 6 years running, while JavaScript has been the most-used programming language for 9 years straight as it runs on every web browser. Now, thanks to WebAssembly (or Wasm), you can use the language you love on the platform that's everywhere. This book is an easy-to-follow reference to help you develop your own games, teaching you all about game development and how to create an endless runner from scratch. You'll begin by drawing simple graphics in the browser window, and then learn how to move the main character across the screen. You'll also create a game loop, a renderer, and more, all written entirely in Rust. After getting simple shapes onto the screen, you'll scale the challenge by adding sprites, sounds, and user input. As you advance, you'll discover how to implement a procedurally generated world. Finally, you'll learn how to keep your Rust code clean and organized so you can continue to implement new features and deploy your app on the web. By the end of this Rust programming book, you'll build a 2D game in Rust, deploy it to the web, and be confident enough to start building your own games.
Table of Contents (16 chapters)
1
Part 1: Getting Started with Rust, WebAssembly, and Game Development
4
Part 2: Writing Your Endless Runner
11
Part 3: Testing and Advanced Tricks

Start a new Game

If you remember our originally planned behavior, and I don't blame you if you don't, we wanted to draw a new game button on the screen when RHB crashed and fell over. Then, when it's clicked, we want to start a new game. For that to happen, we'll need to do the following:

  1. Check whether RedHatBoyStateMachine is KnockedOut, and if so, transition from Walking to GameOver.
  2. On that transition, draw the new game button.
  3. Add an onclick handler so that when the button is clicked, we transition back to Ready with a new Walk instance.
  4. On the transition to Ready, hide the button and restart the game.

All the code we wrote before was to make that change easier. Let's see whether we were right about that:

  1. Transition from Walking to GameOver.

To transition from Walking to GameOver, we need to return the GameOver state from the WalkTheDogState<Walking> update method, but when should we do that? We'll need...