Making a Phaser 3 Tutorial Series?



I have some time to spear and thought about making video tutorials on how to make my phaser platformer game

I have already recorded 30min of coding and would like to know what you think.

Although I read and write a lot in English, I rarely speak. So I ask you native speaker, how does it sound? Should I practices a bit more before making a series or is it just fine? And what about the content? Do you like my style or is it a no go to code more or less unprepared?

Here is the playlist of the first video examples.

Hope you like it and can give me some feedbacks :slight_smile:


I watched the videos 10times and noticed that my voice sounds a bit boring and sleepy. Guess I have to work on this.

Also I should use a second screen which includes the code I want to write. Guess this will help making less boring.

Any thoughts?


I only sped through them, but as a native English speaker I think you
sound absolutely fine!

As someone who has just started working with Phaser3 only a month or so
ago, my advice would be to start from your starter project instead…

Most of the concepts you cover in the current 3 videos are the boilerplate
people will pickup as they get more familiar with Phaser, but I don’t
believe anyone (especially a newbie) should be coding that from scratch.

What I would have loved to see a month ago. is a review of the top starter
kits with pros and cons on why you would choose them. Then take the ‘best’
and show them how to get the environment setup. (node, vscode, vscode plugins)

Then start by showing how you would implement the elements of a typical
game following on from the proper structure set by the starter kit.

I went with phaser-plus as my starter/generator. But now that I am a
little more experienced I definitely would have preferred a typescript
based one for the better intellisense!

Related to this, a guide to finding what you are looking for in the
Phaser docs & source would be helpful for a newcomer too - I’ve
had to dive into the phaser source code on many occasions… this forum
is ok for the basics. but I haven’t ever had any of my questions answered.

Thinking back, my most painful experience learning phaser was getting
a grip on the coordinate and viewport system! Now it’s just second
nature, but to begin with it was hard to break out of the top/left/width/height
style systems I have used in the past.

Prior to starting this project I’d never used ES6, babel, webpack, gulp,
etc… IMHO all of these things (or equivalents) are absolutely essential for
developing anything more advanced than a simple demo - and when included in
the starter kit you don’t need to understand how they work right away. So
starting with a quick overview of what the kit provides and why, then jump
straight into how to structure the typical game elements with the kit - is what a
newcomer would really benefit from.

Then as you answer all of the resulting “how do I do this” questions,
it would really fill in the documentation for your starter kit. A large
part of the reason I chose phaser-plus was because of the excellent
instructions and a youtube video walking through the demo.

But I’ll definitely be trying your typescript starter kit on my next project
so thank you for that! :slight_smile:


Thanks :slight_smile:

The plan was actually to start the first 3 videos with creating a very simple setup (maybe with a even simpler index.html file) to understand better how Phaser works. Then I will start using a simplified version of my TypeScript template.

Since, I do only use linux for years, I did not know how to use node on windows and mac. When creating the production ready movies, I will explain how to set up the environment on all 3 operating systems. For example, on windows git-bash should be installed and the terminal of vscode should automatically use bash instead of powershell.


You’re welcome :smiley:

Thanks for all your feedback. I am very certain now that I can and will make a great tutorial :grin:


On a second thought, maybe it would be better to start with the simplified version (where the npm packages are locked to a specific version) of the template directly :thinking:


(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)


You read this in a book that you wrote yourself? Correct me if I’m wrong, but your post look to me like a total SPAM!