it would be quite useless to have such a glossary as those things can be coded in many different ways depending on the context, so you'll have to manually code them according to your game's structure.
Zoom in / Zoom out - check out MovieClip properties, _xscale and _yscale (e.g. mc._xscale = 200;)
Limit Ammo / Rounds cap - just make a variable to store the amount of bullets, and prevent it from shooting once it reaches 0 (assuming you are decreasing that variable for each shot), and just turn it back to its default value when reloaded
Failure if wrong target shot - seriously, this should be pretty easy. Just make it fail if you hit the wrong target, lolz, if it's a button, make it fail, if it's a movieclip, give it an instance name and use hitTest to check if what you've hit any of the wrong targets
For re-usability, you could have those codes inside Functions, and just reuse them whenever you want (only in the current FLA file, you would have to copy and paste them in new ones as well if you wanted to reuse them there), or for something even more advanced, you could create Classes for each of those functions, with a structure which is easy to implement in most cases, to easily re-use your code (but this is way to advanced for you, I think)
17 Years old boy, who loves the Computer Technology
BRING BACK THE OLD DESIGN!! OR AT LEAST FIX THE AS TAGS
Thanks for the code.
I think classes is way to advanced, but hopefully one day. I think I need to do a course even if it just gives you the bare bones and can go from there.
Reply With Quote
