You're using targetstate or p2stateno to place them into a custom state right?

Posfreeze to lock them in place. Use selfstate to drop them back into state 5050 which is falling.

Are you saying you don't have a standing state, [Statedef 0]?
In your Mugen folder you should have a folder called data with a file called common1.cns. Just copy from that. It has all the basic states like standing, crouching, walking, etc.
The explod and sound are played through the use of an explod and playsnd controller. It's not that hard to figure out.

Standing state

Spoiler, click to toggle visibilty

Code:

;---------------------------------------------------------------------------
; Stand
[Statedef 0]
type = S
physics = S
sprpriority = 0

[State 0, 1]
type = ChangeAnim
trigger1 = Anim != 0 && Anim != 5
trigger2 = Anim = 5 && AnimTime = 0 ;Turn anim over
value = 0

[State 0, 2]
type = VelSet
trigger1 = Time = 0
y = 0

[State 0, 3] ;Stop moving if low velocity or 4 ticks pass
type = VelSet
trigger1 = abs(vel x) < 2
trigger2 = Time = 4
x = 0

[State 0, 4] ;Are you dead?
type = ChangeState
trigger1 = !alive
value = 5050

Iv ben asking how to add effects to fighting stance that is anim= 0. they said to add an explod to [state -3] that worked .But the problem with this is the explod effect is trippled!!so i need to make a stand statedef to place a regular explode to get 1 effect instead of many.How do i construct a full stand statedef in cns so i can add an explode to stand?

---

      Posted: December 19, 2012, 11:56:49 pm
i fixed it

xstarter said, December 18, 2012, 09:26:49 am

Rajaa said, December 18, 2012, 06:25:14 am

To prevent the anim from just freezing, tell the changeanim to not activate when your anim != [transformation anim].

Also, like I said, post your code.

thanks
i already no i have to limit the code,and you said to make the changeanim to not activate my != [transformation anim].
i just need to no the codes to put in and why so i can learn.here's the code in using in cns.

[Statedef 0]
type    = S   
physics = N   
anim = 0   
ctrl = 0

[State 0,1 Change Animation]
type = changeanim
trigger1 = anim != [0, 5]
trigger2 = !animtime && anim = [0, 5]
value = random % 2

now what do i need to add or subtract to make the char not freeze up?

xstarter said, December 15, 2012, 07:45:10 pm

And also why is it that when i move with this code once i cant move or attack afterwords,
it just drags me across the screen?

It sounds to me like you omitted some of the other controllers from mugen's default State 0 (the one found in common.cns), specifically the ones regarding control and velocity. Based on the code you have now, you have nothing to reset your velocity to 0, which explains the sliding after you attack.

If the statedef for state 0 that you're using isnt located in common1.cns, I suggest you copy and paste the entire code of state 0 from that file into your usual cns file, and then make the modifications that 20S suggested. This should solve the problems you're having.

To prevent the anim from just freezing, tell the changeanim to not activate when your anim != [transformation anim].

Also, like I said, post your code.

Because you probably are not limiting the changeanim's activation. Post your code when you ask questions like that.

Because you probably are not limiting the changeanim's activation. Post your code when you ask questions like that.

That won't work, the character will immediately reactivate that changeanim every time the animation changes to 1.

Do the following:

Code:

[state 0, Change Animation]
type = changeanim
trigger1 = anim != [0, 5]
trigger2 = !animtime && anim = [0, 5]
value = random % 2 /*random % # is always a value from 0 to the divisor minus 1. In this case, 0 through 1.*/

If you're going from Mugen 1.0 to WinMugen high-res, then you will need to down-code some triggers and conditions.

I actually did the same thing with my latest characters. I started working on them with Mugen 1.0. When they were almost finished, then I down converted them to winmugen limits.

For things like AI control, instead of using AILevel from Mugen 1.0, you'll need to set your own variables for WinMugen. Or just remove the AI triggers all together. But I just used an AI variable control buffer for my characters for winmugen.