Following the setup of all the UI elements for the pause menu in part one, we’re now going to create an animation for the transition between the unpaused and paused states of the game. As a reminder, here’s a preview of…

Okay, so part one technically had a different name, so I can’t really claim that this is part two. Sue me. I was originally going to talk about using param converters to save even more space, but I realized that the process is too trivial…

After my previous post on refactoring controllers, Khepin made a great point about using lifecycle callbacks on your entities to further reduce your code footprint. I’ll reproduce it here for those who don’t care to look it up:

So far in our efforts to create an animated pause menu, we have set up the required UI elements for the menu, and created the animation clip that will drive the transition between the paused and unpaused…

Now that we have a functioning animator controller, it’s time to accept player input so that we can actually pause the game and bring up the menu.

Use the through2 npm library to pipe your gulp stream through Browserify, and use the babelify Browserify transformer instead of gulp-babel. Check out the gist

Building with magic