In Ikemen you can use the (I think) NoGuardDamage AssertSpecial flag. But I assume you're using Mugen. I've never done Faultless Defense, but I figure there are two ways to do it:

Easy but less accurate: You'd enter a certain state by doing the command and that state would use a HitOverride to block hits. I think you can disable damage if the second state is not movetype H.

Hard but more accurate: You'd override the guard states and code Faultless Defense side by side with regular defense. Damage would be undone by regaining a life amount equal to GetHitVar(Damage). You'd probably need to use a NoKO AssertSpecial flag and a LifeSet to 1 to avoid chip death.

Maybe with this info you can already understand how other chars did it.

Once this is working correctly, how do I limit its use to an onscreen Barrier Meter like in Blazblue?

JasonThePhoenix said, November 16, 2023, 01:19:38 AM

If the Barrier System I want my character to have is impossible in the mugen engine, that's fine. Just let me know and I'll scrap it. It seemed to work fine-ish when costing regular meter, Xrd's Faultless Defense isn't so bad.

In theory it should be doo-able but might be tedious. 

Quote

[State 1315, 3]
type = HitOverride
trigger1 = AnimTime = 0
attr = SCA,NA,SA,HA,NP,SP,HP,NT,ST,HT
slot = 0
stateno = -1
time = 1
forceair = 0
;ignorehitpause =
;persistent =

That won't work. You have no stateno for your character to go into during the hitoverride (-1 isn't an actual state) and the timing is too strict, it is literally just one tick, and also on the same tick that changes you back to statedef 0.  It should look something like this:

[State 1315, 3]
type = HitOverride
trigger1 = 1
attr = SCA,AA,AP;   All attacks and projectiles but not throws.
slot = 0
stateno = 9999 ;----A defined stateno that will put your character in that state.
time = 1
forceair = 0
ignorehitpause =1

You shouldn't hitoverride back into the same state. You need to create a whole new state for the character to go into so for e.g. create a statedef 9999 (or use whatever) and have your character go into that.

Your statedef 1315 should look something like this at a bare minimum:
[Statedef 1315]
type = S
ctrl = 0
anim = 1315
velset = 0,0
movetype = I
physics = S
sprpriority = 2

[State 1315, HitOverride]
type = HitOverride
trigger1 = 1
attr = SCA,AA,AP;   All attacks and projectiles but not throws.
slot = 0
stateno = 9999;----A defined stateno that will put your character in that state.
time = 1
forceair = 0
ignorehitpause =1

[State 0, ChangeState]
type = ChangeState
trigger1 = !animtime
value =0
ctrl = 1
;-------------------------
There's no reason to change into state 130. The override state (statedef 9999 in this e.g.) will negate any damage and as long as you code in push back, it will push the opponent back as well like how you want it. 
Do note that any hitsparks from the opponents hitdef will be displayed so this is really the main drawback.

JasonThePhoenix said, November 20, 2023, 04:32:40 AM

What code is the override state supposed to use?

It's just a state you want your character to go into if he's hit by the opponent.  For example, if you use state 40 (jump start):
[State 1315, HitOverride]
type = HitOverride
trigger1 = 1
attr = SCA,AA,AP;   All attacks and projectiles but not throws.
slot = 0
stateno = 40;----A defined stateno that will put your character in that state.
time = 1
forceair = 0
ignorehitpause =1

Then your character will jump the moment they are hit while in state 1315.

Quote

[State 1315, ChangeState]
type = ChangeState
triggerall = HitOver && !HitPauseTime && stateno != 110 && hitshakeover && movetype != H
trigger1 = !(command="holdback") && !(command="yz")
value =0
ctrl = 1

This changestate makes no sense for what you're doing and has no purpose being in it.

Quote

Animation 1315 is 2 frames long, how do you make it last until you're out of blockstun and you've stopped holding Back and Y+Z?

I think you've misunderstood some things.  Firstly, state 1315 is your barrier state that let's you transition into another state through hitoverride, meaning that it's not a guarding state.  It's a state meant for you to get-hit by the opponent.  Blockstun does not exist. 

If you want the barrier to hold while holding y+z and finish if you release it, then it's like many character's power up/charge moves. There's plenty of those characters around for you to look into how they code in the buttons.