[State 3303, 1]
type = Offset
trigger1 = Time = [0,100]
y = Const(size.mid.pos.y)

[State 3301, 1] ;P2 is more tall than wide
type = AngleDraw
triggerall = (Const(size.mid.pos.y)*-2.0) > ((Const(size.ground.back) + Const(size.ground.front)))
trigger1 = anim = 0
trigger2 = anim = 20
trigger3 = anim = 3306
Scale = (18.0/(Const(size.mid.pos.y)*-2.0)),(18.0/(Const(size.mid.pos.y)*-2.0))

[State 3301, 2]
type = AngleDraw ;P2 is more wide than tall
triggerall = (Const(size.mid.pos.y)*-2.0) < ((Const(size.ground.back) + Const(size.ground.front)))
trigger1 = anim = 0
trigger2 = anim = 20
trigger3 = anim = 3306
Scale = 18.0/(Const(size.ground.back) + Const(size.ground.front)),18.0/(Const(size.ground.back) + Const(size.ground.front))

Ah okay. Good! Really, it's just a matter of offsetting the extra distance by calculating how much the sprite is off. You would just trigger that on the frame/state/whatever that you need it to. The sctrl would probably be Offset. I've had issues with PosFreeze in the past, but I think it was just my situation. See how it works for you though

Your logic should work here. One thing you have to understand about mugen is that if no floating point (float) numbers are within an equation, the result will be an integer. I can't remember if you need both the numerator and denominator as floats, but it doesn't hurt to make both:

Code:

Scale = (20.0/Const(size.height)*1.0),(20.0/Const(size.height)*1.0)

However, there is one way that you can have the player in your custom state read a "variable" of yours. It works like this:
In the HitDef, you take one of the unused (in your particular case) parameters and set it to whatever you want. For example:

Code:

fall.envshake.time = 0 ; To disable the fall.envshake entirely.
fall.envshake.freq = (20.0/enemynear(0),Const(size.height)*1.0)

Then in your custom state, you would access the "variable" using GetHitVar:

Code:

scale = GetHitVar(fall.envshake.freq)

I believe that what you're looking for is within the common required sprites.

When the attack hits the opponent, make the screen flash white

Nobody will notice the sudden jump in anims

[State 3301, 1]
type = AngleDraw
triggerall = Const(size.height) > ((Const(size.ground.back) + Const(size.ground.front)))
trigger1 = anim = 0
trigger2 = anim = 20
Scale = (20/Const(size.height)),(20/Const(size.height))

[State 3301, 1]
type = AngleDraw
triggerall = Const(size.height) < ((Const(size.ground.back) + Const(size.ground.front)))
trigger1 = anim = 0
trigger2 = anim = 20
Scale = (20/(Const(size.ground.back) + Const(size.ground.front))),(20/(Const(size.ground.back) + Const(size.ground.front)))

Sheng Long said, November 17, 2014, 11:05:37 pm

Also, can someone tell me why, when doing single mode, this code displays "has no 0-th partner"

They should be basically the same, except to check if there is a partner, or no partner. I wanted the first code, but it's giving me that 0th partner error.

I just saw this now, but the reason is quite simple. Let's compare the two:

Code:

triggerall = NumPartner <= 0 || NumPartner > 0 && ID < Partner, ID

In this example, you have everything on one line. First, numpartner<=0 will be evaluated. This will be true in single player modes. Next, the other side of the OR operand is evaluated. numpartner and partner are evaluated one after the other. However, if you have no partners, "partner" redirection will result in the error you're seeing. Why is this? It's because you aren't stopping the evaluation after it's found that you have no partners via numpartner.

Code:

triggerall = NumPartner > 0
triggerall = ID < Partner, ID

In this example, you have numpartner being checked first. Then, if the first line is true, the next line will be evaluated. This is safe and won't cause the error.

Do you see the difference? As a closing note, I would like to add that you can surly fix the single line of code to work for you. Observe:

Code:

triggerall = cond(numpartner, partner,ID<ID, 0)

What does this do? I'm sure you've seen ifelse and have used it before. If not, it basically evaluates the first parameter and returns either the second or third expression's evaluation depending on the result of the first expression.

Code:

ifelse(1, 5, 10) ; will return 5
ifelse(0, 5, 10) ; will return 10

The drawback with this is that both "5" and "10" are evaluated by mugen. "cond" does exactly the same thing except that it doesn't evaluate both "5" and "10" for the sake of this example. Instead, it will ONLY evaluate the expression that will be returned. Going back to my example before of cond, you see numparter. This will be false in single player mode. Then, the next parameter is your partner expression, and the one after is simply 0. The result will be 0, because numpartner was false. If simul mode, numpartner will be true and then the "partner" expression will evaluated instead.

I apologize for the long-winded explanation, but I really wanted to show you how it works.

Stupid program.

Another way that comes to mind that could added on top of what you have already is by detecting the stateno and prevstateno of your enemy. For example:

Code:

trigger1 = (enemynear(0),stateno=[10,12]) || (enemynear(0),prevstateno=[10,12]) ; If they're crouching or were crouching in the last state.

Most characters don't really have crouching chains, so usually, you'd see 11->400->11 for a simple crouching attack.

One idea would be to make a type of vertical pushblock helper. It'd take up some resources I think..
But make a blank animation with just a flat blue bar. (FF3) Make a helper and use it as it's anim.
You could set it to move down until it made contact with P2. Then you'd use it's position and find the general "top" of P2.
One thing would be like Ryu's crouching uppercut. The top of the fist would become the top of the character, so P1 still might have the problems you're describing.

If a creator of a character mislabels moves, I dont know how you should be responsible to code around it.
you could always do something like

[State -2, adjustvar]
type=varset
triggerall=numenemy
trigger1=enemy,name="cvsvega"&&(enemy,authorname="Warusaki3"||enemy,authorname="Gargoyle")

and list people with problems.

You can also use Enemy,Const(size.head.pos.y)

It will return the position of the head, based on the character's CNS. It will not return the current Pos Y of the character's head, so it will be the same if the enemy is jumping or crouching

However, you can play with this value by offsetting it with the character's axis. If the axis is higher than the head.pos.y, then the character is jumping

Open the door, get on the floor! Everybody walk the dinosaur!