Creating Game Prototypes with Phaser 3 - Simon

In this video, we will focus on creating a basic implementation of the game Simon using the Phaser 3 framework! For our game, we will be using the Phaser 3 Prototype Template as a starting point, and then we work on creating the basic layout for our Phaser 3 game. Once this is done, we focus on creating a re-usable Simon class that can be used with any JavaScript framework, and then we update our Phaser 3 game code to use the new class.
Video Chapters
0:00 - Intro
1:17 - Project template
2:10 - Project task list
4:01 - Download assets
4:29 - Update game config
4:47 - Load assets
6:40 - Create buttons
12:58 - Make button interactive
16:56 - Create Simon class
22:23 - Generate random sequence
25:42 - Handle player input
28:46 - Add game state
31:34 - Play sequence
35:34 - Update game logic
43:13 - Add audio
44:50 - Summary and Enhancement ideas
45:55 - Thanks and links to other content
You can download the project template directly from GitHub here: github.com/devshareacademy/ph...
The completed code for the Phaser 3 Simon game prototype can be found here: github.com/devshareacademy/ph...
Interested in more great content?
Check out my videos on Phaser 3 here on KZbin:
• Phaser 3
Check out my free courses here on KZbin:
Monster Tamer - Pokemon like RPG Tutorial with Phaser 3:
• Monster Tamer - Pokemo...
Introduction To GitHub Actions Course:
• Introduction To GitHub...
JavaScript Course:
• Learn JavaScript Course
Follow Me:
/ scott-westover-77393a97
github.com/scottwestover
Blog:
scottwestover.dev/

[@iberryboi]

You should apply for the content creator role at phaser studio!

[@noelpena4567]

Thank you for this walkthrough. I had a question, why do you create private variables with a "#" in front of them? Is that a convention you use personally?

[@swestover]

Thanks! Yeah, for private fields and methods, I typically try to use the built in javascript method of making the fields and methods as private (using the # as a prefix). However, using the "private" keyword in TypeScript would also work. By using the # method for making fields and methods private, it guarantees when the code is compiled by tsc and at runtime, it will make those values truly private, and not accessible. When using the "private" keyword, this is only considered at compile time, and these fields/members can still be accessed. There are a few other differences, but this is the main reason that I use this syntax.