ground.type = attack_type (string)
This is the kind of attack if P2 is on the ground. Choose from: - "High": for attacks that make P2's head snap backwards. - "Low": for attacks that hit P2 in the stomach. - "Trip": for low sweep attacks. If you use "Trip" type, the ground.velocity parameter should have a non-zero y-velocity, and the fall parameter should be set to 1. A tripped opponent does not bounce upon falling on the ground. - "None": for attacks that do nothing besides pause P1 and P2 for the duration in the pausetime parameter.

If P2 is hit from behind, "High" will be displayed as "Low" and vice-versa. P2's animation for "High" and "Low" types will be superseded if the AnimType parameter is "Back". Defaults to "High" if omitted.

Then afterwards in the state that has the hit that needs that state, I add the following controller:

Code:

    [State TState]
    type = TargetState
    triggerall = numtarget(<hit_ID>)
    trigger1 = movehit=1 && !movereversed
    trigger1 = !target(<hit_ID>),ishelper
    trigger1 = target(<hit_ID>),time=0 && target(<hit_ID>),movetype=H
    value = 470
    ID = <hit_ID>
    ignorehitpause = 1


Not sure if this will circumvent the common behaviors, but if they are hardcoded I'm sure they only specifically work for state 5070/5071, but it's worth a shot.

Quote

Then afterwards in the state that has the hit that needs that state, I add the following controller:

Code:

    [State TState]
    type = TargetState
    triggerall = numtarget(<hit_ID>)
    trigger1 = movehit=1 && !movereversed
    trigger1 = !target(<hit_ID>),ishelper
    trigger1 = target(<hit_ID>),time=0 && target(<hit_ID>),movetype=H
    value = 470
    ID = <hit_ID>
    ignorehitpause = 1


Not sure if this will circumvent the common behaviors, but if they are hardcoded I'm sure they only specifically work for state 5070/5071, but it's worth a shot.

You also need to add a
trigger1=target,stateno!=[120,155]
line in there, otherwise hitting a helper (which won't be your target thanks to hitoverride) and then making contact with the guarding player (who will be a target instead) will force the guarding player to the custom state. In other words it makes the attack unblockable when guarding near one of your hittable strikers if the attack is capable of hitting both. Also, the moveguarded trigger will not work for this, if I remember well, it doesn't work when movehit is already set.

The same can be said of a guarding opponent's partner who also gets hit, but doesnt block, because fuck simul

Best solution would be to have it drop a target and keep one, which isnt going to make a difference in single, but at least it solves the guarding problem in simul.