The Mugen Fighters Guild

Help => M.U.G.E.N Development Help => Topic started by: Disconcorde on September 21, 2019, 01:28:28 am

Title: NotHitBy vs HitBy, which is better?
Post by: Disconcorde on September 21, 2019, 01:28:28 am
I did a bit of messing with kfm in regards to hitby and nothitby but to me it seems like that they basically have the same function.

I mean, what's the difference between these, can anyone tell me?:

Code:
[State -2, NotHitBy]
type = NotHitBy
trigger1 = 1
value = SCA,AA,NA,SA,HA,AP,NP,SP,HP,NT,ST,HT
ignorehitpause = 1

and

Code:
[State -2, HitBy]
type = HitBy
trigger1 = 1
value =  , AT
ignorehitpause = 1

After all, that NotHitBy has every attr except AT, whilst the HitBy has only AT. So, if what documentation says about how these operate is true, then shouldn't this achieve the exact same result? Why would someone choose to use one or the other in circumstance if they do the same thing? I'm just curious.
Title: Re: NotHitBy vs HitBy, which is better?
Post by: Cyanide on September 21, 2019, 08:03:57 am
The hitby you have will only be hit by throws. Because the doco is a bit fucky the nothitby will just be immune to everything
Title: Re: NotHitBy vs HitBy, which is better?
Post by: Yuko on September 21, 2019, 08:19:27 am
Also correct me if I'm wrong but NotHitBy using value = SCA already makes it immune to everything, right? I mean you don't need to put every single condition there...
Title: Re: NotHitBy vs HitBy, which is better?
Post by: Nep Heart on September 21, 2019, 08:23:31 am
 Yeah, even Elecbyte implies that if you want invuln against a very specific attribute, omit SCA and put something like ,AP instead of SCA,AP for proj immunity for example.
Title: Re: NotHitBy vs HitBy, which is better?
Post by: Disconcorde on September 21, 2019, 03:04:03 pm
@DeathScythe
I guess it does, but I've seen other chars put every condition there when creating OHKO resistances/counters, which is why I asked. I'm trying to make a character more OHKO resistant.

@Cyanide @Nep Heart

I see. But you get where I was going. I didn't know that SCA would mean complete invulnerability, but A nothitby with everything minus AT and SCA, would be the exact same thing as the hitby with only AT, and would result in the exact same abilities for the char.

Yet, HitBy is used less, and when I do see it, it's in better characters that usually come with OHKO resistances, and I just sort of assumed there's a connection... a reason as to why they might use one instead of the other.




I've currently been coming up short though, I guess I'm not at the coding level to make OHKO resistances, but I don't want to give up either. I've been trying to study some of the other chars that I have who have OHKO resistances themselves, though because I don't know what to search for, I haven't really found anything.
Title: Re: NotHitBy vs HitBy, which is better?
Post by: Archimonde on September 22, 2019, 04:20:18 pm
MUGEN code execute from high to low and asenceding order (from -3 --> -2 --> -1 --> main statedef)
Title: Re: NotHitBy vs HitBy, which is better?
Post by: Yuko on September 22, 2019, 04:39:03 pm
I guess it is the same thing and is more of preference. Example would be a dodge that you want to be invulnerable to everything except throws, in this case I'd use HitBy with value = AT. Now if I'm coding a move where the character is invulnerable to only projectiles, I'll go with NotHitBy with value = AP.
Title: Re: NotHitBy vs HitBy, which is better?
Post by: Cyanide on September 22, 2019, 10:22:20 pm
It gets harder if you just want to be immune to standing attacks. Not projectiles or throws. You need to start combining them. Nothitby S,NA. Hitby = CA,SA,HA,AP,AT

Yuck.