It’s time to cover asteroid generation. I bet you never thought playing with rock would be fun… well, you were wrong! Before we code, let’s visualize and put into words what we want to achieve: we want a class that will draw an asteroid (stroke of genius right here) it should be drawn randomly within
I believe it’s high time we attempted to build a game with the engine we have so far; wouldn’t you agree? We’ll be making Asteroids, which first made its debut in November 1979; released by Atari Inc. There are so many ways we could implement the game: we could use sprite sheets, as we do
We’re going to continue with DisplayObject which extends Scene. You can review the schema in part 1 of this series but we’re going to make some changes to how things are named. Its job is very simple; it will group objects that need to be rendered in a children array and it will expose methods
The last article was a bit long so we’re going to move forward in smaller increments. Let’s start with a discussion on how movement works in games. The 18th century Swiss mathematician, physicist, astronomer, logician and engineer (quite a resume) Leonhard Euler devised a way for us to predict where an object’s going to be
Time to get started on the core components of the game engine. We should be able to render something on the Canvas before the end of this article! Note: please be aware that I’ll add links to specific pieces of code in the GIT repository history tree. This will make it easier for you to
Maybe I should ask if you’ve ever thought about how games work, perhaps even about building a game from scratch? If not, turn away now; I see lots of math in your future! In my childhood I was fascinated by Mario and other games like it. They were very simplistic and yet extremely fun to
