Wednesday, July 29, 2009
MJW Avoider Game ep8ch1
...That'd be episode 8, challenge 1
So now that he's shown us the magic of adding sound, he wants us to figure out how to create a Mute button on our own... sheesh. :) This was the easiest challenge, so far. But, so that I can solidify this in my own head, and in case you need help, here goes my thought process:
The first step I wanted to complete, had nothing (directly) to do with sound. I wanted Flash to recognize another button was being pressed. Instead of being original, I picked "m" as my mute button... Feel free to pick L, meaning "Let the music stop", or ß (ALT+0223) for "This music was picked for the beta. If you don't like it you can turn it off."
Going back and referencing my old code, I made these additions:
All of them are in the AvoiderGame.as file.
Create a publicly accessible variable (outside contructor)...
Initialize it in the contructor...
Inside the onKeyPress function
Michael let you figure out the onKeyRelease function, and a student is not above his teacher, so I'll let you figure that out too.... :P
Then in the onTick function, I used a trace() command as a placeholder
Don't forget to "Disable Keyboard Shortcuts"
...and then watch your Output window. When you press m, it should fill up with "You're pressing M!!!" over and over...
Ok, so it's working, I have a stream of useless output to prove it. Now I want it to actually do something useful! I created some new global variables:
musicPosition is an integer. It's going to be equal to where the music was muted, so that when it's unmuted it'll play from the same spot. I guess that makes it a pause button... so, sue me.
musicIsMuted is straight forward. It's a true/false value of whether the music is muted.
...and then I initialized them, one in the constructor (musicIsMuted), and one in the onTick function
Ok, ok.... I did a little more then initialize it. I put together the basic if...else structure I was going to use. If the m key is being pressed, then if the music is already muted, do nothing right now, else check the position (in milliseconds) it was muted at, and put that into our variable, as a whole number (that's what Math.floor() does, if you don't remember)
Now, let's flesh it out some. If the music wasn't muted already, what do we want to do? We want to stop the background music from playing, and we want to change our variable (musicIsMuted) which tells us if the music is playing to true.
If the player already muted the music, and now wants it to play again (cause they miss those jazzy synth beats!) then we would want it to play from where it stopped (we can do that by passing the play() function an argument), and change the musicIsMuted variable back to false.
Now save everything and test your game... Easy, huh?
Oh, wait, you say it keeps rapidly turning off and on? Crud! Well, we can fix that using some tidbits from Michael's sh'm'up tutorial.
Create another global variable:
Initialize it in the constructor:
and change your function to:
If you haven't read that tutorial already, and can't piece together what I did, head over and check it out. No use in me re-inventing the wheel.
Avoider Game Shmup
That should do it. Now you can hear the 'thump, thump, thump' of the enemys coming on screen without that pesky synth-music playing in the background!