Tutoriales y Programas

Combo Punches

This tutorial is going to deal with 2 seperate kinds of combo punch. 1 where you have to make contact, either blocked or hitting and another where you just press a button over and over. This is not continuing from Naruto but you will be able to follow along with him or anyone else.

What you'll need,

Fighter Factory.
A character with at least 2 basic moves.

Part I
Contact Combo'ing

Open up your character in Fighter Factory (FF) and go to the command section.

I hope you can remember the states you used, we're going to trigger off those. In this example i'm going to combo between Light Punch (state 200) and Medium Punch (state 210)

Go to the bottom of the command file where you have your basics coded.

;light punch
[state -1]
type = changestate
triggerall = command = "a"
triggerall = command != "holddown"
trigger1 = ctrl
trigger1 = statetype = S
value = 200

And

;medium punch
[state -1]
type = changestate
triggerall = command = "b"
triggerall = command != "holddown"
trigger1 = ctrl
trigger1 = statetype = S
value = 210

Now in order for a combo to occur Mugen needs to check if the hit has made contact. For this we use the MoveContact trigger. It returns true if a move either hits or is blocked. If you just want to check on hits OR blocks rather than hits AND blocks, you would use MoveHit or MoveGuarded.

In addition we need to check that the character is in the correct state. For this we use the StateNo trigger (state number see?)

If you followed my last punch tutorial you'll know what triggerall does. In this instance you'll actually see why we use it.

Create 2 lines under Medium Punch.

Trigger2 = MoveContact
Trigger2 = StateNo = 200

That means the character must be in state 200 and must have made contact with the hit. You will also note there is no "Command" line here and that both of them are labeled Trigger2 rather than Trigger1. This is because you're issuing a different method of activating the move. Think of it like, If I have control OR If I am in state 200 and make contact. Triggerall will allow both of these to function when you press "b", See it Triggers All. Clever what?

You can then do the same in reverse for Light Punch.

Trigger2 = MoveContact
Trigger2 = StateNo = 210

You can even make them trigger off themselves,
For State 200

Trigger2 = MoveContact
Trigger2 = Stateno = 200

If you want them to trigger off themselves OR the other state

Trigger2 = MoveContact
Trigger2 = Stateno = 200
Trigger3 = MoveContact
Trigger3 = Stateno = 210

Use Trigger3 as well, Triggerall will set it off fine.

Tweaking with other triggers can provide more control with how the move can combo. Things like Trigger2 = Time > 20 means you could only activate it when time doing the move was greater than 20 ticks (1/3rd of a second)

So by this point you ought to have something that looks like this

;light punch
[state -1]
type = changestate
triggerall = command = "a"
triggerall = command != "holddown"
trigger1 = ctrl
trigger1 = statetype = S
trigger2 = stateno = 210
trigger2 = movecontact
value = 200

Or this

;light punch
[state -1]
type = changestate
triggerall = command = "a"
triggerall = command != "holddown"
trigger1 = ctrl
trigger1 = statetype = S
trigger2 = stateno = 200
trigger2 = movecontact
value = 200

Or this

;light punch
[state -1]
type = changestate
triggerall = command = "a"
triggerall = command != "holddown"
trigger1 = ctrl
trigger1 = statetype = S
trigger2 = stateno = 200
trigger2 = movecontact
trigger3 = stateno = 210
trigger3 = movecontact.
value = 200

As you add more you may find the command looking rather drawn out. That's when you need to look up Code Optimisation. Used right it can make triggers activate more smoothly and clean your code up to an understandable level.

Part II
Button Mash Comboing

This is much looser than Contact Combos. You just hit a button over and over to activate the next move in the series. Actually hitting the opponent isn't a neccessity.

Even though we're just pummeling buttons we still want the previous move to run through the whole thing or you can just make the character flail around and never even get to the point where his HitDef will activate. For this we'll use the AnimElemTime trigger.

Using State 200 and State 210 again.

State 200 has 3 frames, State 210 has 4 frames.
Remember Frames are also called Animation Elements (AnimElem)

For State 200 to combo off State 210
Trigger2 = StateNo = 210
Trigger2 = AnimElemTime(4) > 0

As in Contact Combo'ing we're checking the state number with the StateNo trigger. AnimElemTime is new though so it'll need explaining.

The AnimElem trigger checks which frame you are on but it's not very flexible and can't be used well for this purpose. AnimElemTime checks how long you've been in a particular Animation Element (frame) In AnimElemTime(4) > 0 Mugen checks only if you're on Animelem 4 and at least 1 tick has gone by when you push "a"

If you wanted State 200 to activate off "b" instead of "a" just set it up so state 200 triggers off Triggerall = Command = "b" with those 2 triggers as Trigger1 instead of 2. In addition you'd have to remove the Ctrl line as when you're in a move you don't have control so the triggers would return false.

So you should have something that looks like this

;light punch
[state -1]
type = changestate
triggerall = command = "a"
triggerall = command != "holddown"
trigger1 = ctrl
trigger1 = statetype = S
trigger2 = stateno = 210
trigger2 = animelemtime(4) > 0
value = 200

Or this

;light punch
[state -1]
type = changestate
triggerall = command = "b"
triggerall = command != "holddown"
trigger1 = Stateno = 210
trigger1 = animelemtime(4) > 0
trigger1 = statetype = S
value = 200

Thats basically all there is to it. Add triggers or extra ChangeStates as neccessary.