Forums → Programming Forum → Game in the works

Skimming through the code it looks like when you keypress, you addChild then as the clip is finished you removeChild.

IMO this will cause a lot of errors. Instead you can create a movieClip and have all the sequences of movieClips in frames and label the frames to reference the sequence. I would also make the keypress in a separate class using switch, which will be dedicated to booleans in the main document class, and from there check if the key is pressed.

I have made a few sample's of what I am describing. My most current example HERE on setting up flash. Also a sample of game play HERE

I suggest to skim through it and pick out what you want. I can put together a "simple" sample of the movieClip sequences I briefly suggested If you want.

well I went ahead and made it. I kinda slapped it together so don't expect it to be perfect. I also put everything in the actions panel, but you should be able to easily pick out what you want.

LINK

Hey, thanks for getting back to me. I have been trying to convert my work into action panels and I haven't really used them before. I looked over the work you did with the LINK and I wanted to ask how does the compiler know what the defined property for hero is? I didn't notice one when I looked through it.

I highly suggest continuing working with the classes as that is what I prefer most.

As you load the file you can see the "hero" on the screen. Take a look at the timeline and you will see the layer containing the hero. It might be a locked layer just click on the lock to allow changes on the layer then you can freely select the hero. At that point while the hero is selected click on properties and you will see that hero is the Instance name. (if you don't see the properties panel press Ctrl+F3)

Normally in classes you just do this

var hero:heroMC = new heroMC();
addChild(hero);

The instance name is hero while the AS linkage is heroMC but on the timeline you need to declare the instance name by typing into that box and there is no addChild as it already exists on the screen.

EDIT: double-click on the heroMC to open an internal timeline showing the sequences.

I may have misunderstood your question. Flash automatically generates the definition on export. With the clip on screen you can convert to symbol. Then the properties box will ask if you want to export for action script, if selected the base class definition is right below it. If you decide you want to create your own "hero" class then you will need to "extend movieClip".

I finally figured it out and thanks again for the help. Do you know how to make it when I press a button it automatically changes to the other animation? I seem to have a minor lag between animations with button presses. I have it set to 24 frames per second and I am using exactly that amount so I wasn't sure if that was it.

hmm.. well post what you have and I can look it over.

This is what I have so far for my animations:

import flash.events.Event;

hero.gotoAndStop("running"


var upPressed:Boolean = false;
var downPressed:Boolean = false;

var gravity:Boolean = true;
var jumpTrue:Boolean = false;
var groundFix:Boolean = false;
var jumpHeight:Number = 0;

hero.addEventListener(Event.ENTER_FRAME, heroMove);
stage.addEventListener(KeyboardEvent.KEY_DOWN, keyPressed);
stage.addEventListener(KeyboardEvent.KEY_UP, keyUnPressed);

function heroMove(event:Event) {
if (upPressed) {
if (jumpTrue) {
if (groundFix) {
jumpHeight = hero.y - 75;
groundFix = false;
hero.y -= 15;
} else {
hero.y -= 15;
if(hero.y

[lesser than equal sign] jumpHeight) {
jumpTrue = false;
}
}
}
}
if (gravity) {
hero.y += 5;
}
}

function keyPressed(event:KeyboardEvent):void {
switch (event.keyCode) {
case Keyboard.UP: {
if (upPressed) {
hero.gotoAndStop("jumping"
}
upPressed = true;
break;
}
case Keyboard.DOWN: {
if (downPressed) {
hero.gotoAndStop("sliding"
} else {
hero.gotoAndStop("running"
}
downPressed = true;
break;
}
}
}

function keyUnPressed(event:KeyboardEvent):void {
switch (event.keyCode) {
case Keyboard.UP: {
if (downPressed) {
upPressed = false;
jumpTrue = false;
stop();
hero.gotoAndStop("jumping"
} else {
upPressed = false;
jumpTrue = false;
hero.gotoAndStop("running"
}
break;
}
case Keyboard.DOWN: {
if (upPressed) {
downPressed = false;
hero.gotoAndStop("sliding"
} else {
downPressed = false;
hero.gotoAndStop("running"
}
break;
}
}
}

Not sure why that didn't want to post.

Well looking at the code is limited when the question is directed at the animation. I am speculating that you might need to look at the frames in the clip that has the delay. First make a copy of it then you can try removing the first frame. If it is exactly the same as clip before it. Then it makes sense that it will show the same frame (and appear to have slight lag) then continue through the timeline. If you notice that it is making a difference then you can play around with the animation and find the exact frame to start from.

Okay, I'll mess around with the frames and see what's going on with them. Thanks for the help again.

Would the cause of the problem be if I am using the same picture on multiple frames?

It could very well be it. When you hero.gotoAndStop("jumping" and there is a slight lag but only at the beginning then it might not be a lag at all, and it is the start of the sequence. Remove the frames (after you make a copy) that are at the beginning until it is smooth.

Is there a command or something to completely stop the previous animation? While the other animation is running?

It is to my understanding when you switch frames the MovieClip on the previous frame ends and when you switch back it starts over. Anywho... The hero movie clip is on the stage. So the stage is the parent and hero is the child (unless you addChild on some other layer or it is not already present on stage). The hero (if you double click on the clip) also contains children; running, jumping, and sliding. You can select these children and give them instance names. If the jumping clip was declared as jumpingMC then you could use hero.jumpingMC.stop(); or hero.jumpingMC.gotoAndStop(1);. If you create a hero class you would eliminate the hero bit all together and it would look like this jumpingMC.gotoAndStop(1); If you decide to take this route you might also need to use hero.jumpingMC.play();