Hey Guys, I'd say I'm still fairly new to the forums but I'm checking more and more often, and one thing I have noticed is that the Programming Help section isn't very active. So I thought I would add my 2 cents and share some of my AS programming experience.
I've been programming actionscript for about 3-4 years now and have even been through 2 ArmorGames challenges. I've been asked by a lot of people for some coding help over my time and, well, I see a lot of times that I code quite a bit differently then they do, and a lot of that is because they are: 1.Still new to Actionscript 2.Have learned only from online tutorials 3.Are used to coding with what works instead of what works best.
So, what I decided to do here is to share with you what I have learned over the years to be Good Programming Technique. So before I start this first one off take note: This is being coded is Actionscript 2.0 (I still have to fully embrace AS3 although I highly encourage learning it) Also, this is what I have personally learned from my experience, you may disagree, that is fine, actually if you think I'm wrong let me know so that we can all learn because there is no reason to code ONE way.
Ok so after that intro this is what I have to share with you.
Coding on the Main Timeline
The more complex your game gets, you're going to have more MovieClips, Layers, Frames, lines of code, etc. And with that, it will be harder to organize everything. Which is why it is always good technique to code on the main (or _root) timeline. Now some of you may not even know it, but you can actually control every aspect of your game by coding into the the first frame (not movieClip, frame) of your game. For example, on my latest game I had right around 2000 lines of code on the very first frame.
2000 lines on the same frame!?
Yes. You may be thinking right now, How? Well, there are 2 very very important coding methods I use when I program and they both make use of that frame. The first one, which I'm going to explain on this post is calling movieClip's (onEnterFrame) method from the main timeline instead of on the instance of the movieClip itself. I'm sure you are very used to coding with: onClipEvent(enterFrame) -What I'm telling you is that I don't do that.
You can do onClipEvent(enterFrame){ outside the movieClip?
Yes, yes you can. And here is how:
on the main timeline for a movieClip with the instance of myClip you would have something like:
myClip.onEnterFrame = function():Void{ Which would be the same doing a onClipEvent(enterFrame){ on the myClip movieClip, you just have to make sure you have the instance name (in Properties) set to 'myClip' and that it is on the main timeline.
-If it is not in the main timeline, lets say its in a movieClip called 'otherClip' you simply have to add a bit of code: otherClip.myClip.onEnterFrame = function():Void{
Umm ok, but I still don't see why you do this...
Fine fine, I understand this might be a little confusing at first, but in time I'm sure it will make sense, it might take a little trial and error. The reason I say it is good technique is that having all of your code on the main timeline makes it very easy to keep your code organized and easy to locate. If you have several movieClips/Frames/Layers in your game that you want to apply code to, it going to get confusing. Where did I put that clip? Where is the code that deals with the hitTest? What frame is it on? etc, when you code in one place you don't lose, forget, or repeat code. Its all in the same place so it is easy to work with, and if you ever code with with someone else it will make their lives a lot easier because they won't be looking all over for code they don't even know exists.
Alright, so just a few notes to end on: (gosh this post long, sorry)
It is always a good idea to code on the main timeline. You can save lots of lines of code and better organize your code by calling .onEnterFrame functions (functions are a very very big part of coding as well, if you don't know about them I'm sure I'll make a topic on it someday) Even if you code AS3 you can still practice this.
Let me know if something doesn't make sense, I'm sure it may be quite confusing.
What I usually tend to do is if it becomes too much code on the timeline, I put it in a seperate .as file. For me, this makes it easier since it keeps everything together, yet doesn't show the 'useless' timeline GUI - which I don't use when I'm coding anyway
And a few seperate classes ofcourse, such as for the player and the GUI of the flash.
Keep it simple , solving a problem with simple steps will be far better then a complex solution to a complex problem, what is known as elegant code. It is far easier to debug and get it working. Also the end result is better will run better on a wider variety of end use machines.
This is an AWESOME tutorial for anyone who wants to learn a good OOP approach to making flash games: http://gamedev.michaeljameswilliams.com/2008/09/17/avoider-game-tutorial-1/
Hey , im new , ive just started to make flash only like a maze,buttons,change mouse stuff like that. how long dose it take to make a game how do i remembers all the codes where do i get the codes from?
