We covered a lot of ground yesterday. In Bumper Bash, we learned about the collision handler, which lets us know which two sprites just collided with each other. This is a huge addition to our coding toolbox!
Now if we’re writing a game we can let the SpriteKit framework do the work of figuring out when two objects have collided.
Now, my high score wasn’t amazing for this one. Have you managed to beat it?
We’ll look at a few ways to cheat the system today — we’re coders, after all, we can write our own rules!
We’ll also explore the
applyForce method on our sprites and see what that does.
We also moved on to Gem Hunter yesterday. This playground page combines all the inputs we’ve learned about: touch, light, sound, and collisions. We’re going to write a game that will use a few different ways of manipulating our player to get as many gems as possible.
My high score for this game, our first pass, also wasn’t brilliant, so please tell me you were able to beat me!
We’ll spend a little time rigging up some easy win scenarios today. Then we’ll think about what might make the game even more playable.
What behavior will our player have in reaction to light updates? Will we add some labels to see values from our events in real-time?
Come code with us today at 1pm, Irish time!