I know not as a frame action, but I always use movieclips... just habit of mine.
What I was meaning is that on() is the function, but onEnterFrame is just a variable (well, according to flash) without a eventListener attached to it. If flash is automatically assigning the eventListener then that is in a newer version (insert rant on how I really hate how flash handles variables).
I often use 60 FPS because I often need that higher rate for the smoothness and an increase in calculations per second. As I control everything with action script (except for premade animations, which can be incrimented by AS too) simple uses of timers keep everything running smoothly. I know that Flash IS powerhungry and will grab 100% of the cpu rate at high refresh rates, but when that occurs I'll reduce the fps to 30-45. Simple managment of functions keeps the CPU from getting too overworked...
Quote: "....really I have no plans for changing the already perfectly working array level system..(sometimes I put random frames imbetween levels for times when I forget to implement something ebfore the first level so..."
Perfectally working isn't allways a perfect answer. Even what I am suggesting isn't a perfect answer... I just prefer it, it seemingly makes things much easier... but then again, it is your perogative.
Quote: "(this will also let me rearrange my levels quite easily, which I plan on doing)"
Using individual motionclips does this with extreme ease. Instead of having to keep track of frames, you only have to keep track of 12 movie clips, you can even just put each movie clip in a frame after it.
Quote: "what do you mean, shouldn't have a path for level 1? btw the path shown is the actual guide path I use(copied to another level so that you can actually see it though)"
My (insert rant here) is about USEING paths... but what I WANTED you to do is put it a level below the 'button'.
If you fear speaking for yourself, make use the words of others while discovering your own voice.
