Invincibility

[Chon Wang]

Make your char invincible.

; Use states -2 or -3 and a variable

; sets
[State -3]
type = VarSet
var(5) = 300 ; time (in gameticks) of invincibility
trigger1 = stateno = 1000 ; a condittion

; countdown
[state -3]
type = VarAdd
var(5) = -1
trigger1 = var(5)

; invincible
[state -3]
type = NotHitBy
value = SCA
trigger1 = var(5)

; resets
[State -3]
type = VarSet
var(5) = 0
trigger1 = var(5) < 0

[Valodim]

imho, every mugen creator should be able to think of that code himself

anyway...

[State -1, -2 or -3]
type = NotHitBy
trigger1 = !Var(X)
trigger1 = condition
trigger1 = !Var(X):=(timeinticks)
trigger2 = Var(X)
trigger2 = 1||Var(X):=(Var(X)-1)
value = SCA

pwned

By the way, your code doesn't at all look like code written for a tut...

[Chon Wang]

I like this code don´t matter how it´s written

[Valodim]

so it's not written by you...?

[Chon Wang]

Yes, it´s written by me. I might have not understand your reply, because of my bad English: "By the way, your code doesn't at all look like code written for a tut...".

[Valodim]

okay

[Matmut]

@Deku Nut: Don't forget the brackets

trigger1 = !(Var(X):=(timeinticks))

[Valodim]

are those needed? I don't know but guessed not...

[Matmut]

Yep. It gives a parsing error otherwise.

BTW, Valodim's code has more sense because invicibility time continues decreasing even if it is triggered one more time, unlike Chon Wang's.

[Valodim]

actually, his loops from -1 to 0 within one tick...

[sign=4]my code pwns[/sign]

[Winane]

Um, no, his code never results in var(5) holding the value -1 (nor anything less).  Which, by the way, makes his last controller rather useless.

[Messatsu]

Maybe it is a backup in case Mugen forgets how to work and decrements when var(5) has no value. :huh:  It would be more economical to place the first state controller in state 1000.

[Chon Wang]

Well, the last State isn´t useless because it can be anything that the creator would want to use, not necessarily a stateno trigger.

[Messatsu]

... in this example it is.

[Chon Wang]

... in this example it is.

It was obvious, but just like you can see in my first post i´ve put "a condition", not "the condition"  

[Valodim]

[sign=2]we need a mod for this board.[/sign]

[Messatsu]

me? :grin:

Chon Wang:

Which, by the way, makes his last controller rather useless.

A state controller is this:

Code Select Expand

[blah]
type = hiddentrigger ;)
trigger1 = 1

Not this

Code Select Expand

trigger1 = stateno = 1000 ; a condittion

This is what is refered to as useless

Code Select Expand

; resets
[State -3]
type = VarSet
var(5) = 0
trigger1 = var(5) < 0

As mentioned, var(5) (with the code presented) doesn't ever equal -1.

[Valodim]

me? :grin:

if the gmods did their job, we'd not need a mod here

[Chon Wang]

Well, i think i know what a state and a trigger are  

When var(x) < 0 you can´t trigger var(x)? I mean, trigger1 = var(x) returns to sfalse if var(x) <= 0 or only when var(x) = 0?

And in case of using a different triggerization? Like gametime = 95 and !var(5)? Would it be useless?

If not, I think a better solution should be:

; sets
[State -3]
type = VarSet
var(5) = 300 ; time (in gameticks) of invincibility
trigger1 = gametime = 95 ; a condittion
trigger1 = !var(5)

; countdown
[state -3]
type = VarAdd
var(5) = -1
trigger1 = var(5) > 0

; invincible
[state -3]
type = NotHitBy
value = SCA
trigger1 = var(5) > 0

Edit: changed a trigger.

[Valodim]

[State -1, -2 or -3]
type = NotHitBy
trigger1 = !Var(X)
trigger1 = condition
trigger1 = !Var(X):=(timeinticks)
trigger2 = Var(X)
trigger2 = 1||Var(X):=(Var(X)-1)
value = SCA