[State 190, State]
type = ChangeState
triggerall = Var(5) <= 0
triggerall = RoundNo <= 1
triggerall = NumPartner != 1 || NumPartner > 0 && ID < Partner, ID
trigger1 = Name = "sf2ww"
trigger1 = EnemyNear, Name = "sf2ww"
trigger2 = AuthorName = "Capcom-SF2"
trigger2 = EnemyNear, AuthorName = "Capcom-SF2"
trigger3 = P2Name = "sf2ww"
trigger3 = Name = "sf2ww"
trigger4 = Name = "sf2ww"
trigger4 = EnemyNear, AuthorName = "Capcom-SF2"
trigger5 = AuthorName = "Capcom-SF2"
trigger5 = EnemyNear, Name = "sf2ww"
value = 11000

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

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.

Алексей said, November 20, 2014, 02:44:55 pm

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.

Алексей, every response you make in this subforum is pure gold.