YesNoOk
avatar

Matchover = 1 not working (Read 1082 times)

Started by BoyBoyz, December 20, 2011, 10:42:31 pm
Email this topic
View printable version
Share this topic:
« previous next »
Page 1 of 11   Go Down

BoyBoyz

Matchover = 1 not working
#1  December 20, 2011, 10:42:31 pm
  • ***
Hi pros, any idea how to make a matchover (after losing 2 rounds) voice work in mugen 1.0? matchover = 1 && !Alive doesn't work... : (

Cyanide

Re: Matchover = 1 not working
#2  December 20, 2011, 10:50:26 pm
  • ******
  • Legendary XIII
  • I am the eye of the storm to come!
    • New Zealand
    • network.mugenguild.com/cyanide/
IIRC when you're dead things stop actually processing for you. You're dead. You can trigger that sound in the first tick of the state you go through before you're dead. So, 5050 if matchover and !alive and time = 0 should be OK.


In M.U.G.E.N there is no magic button

They say a little knowledge is a dangerous thing, but it's not one half so bad as a lot of ignorance.

BoyBoyz

Re: Matchover = 1 not working
#3  December 20, 2011, 11:12:52 pm
  • ***
Oh sorry I think I should clarify... I have two sounds for losing. I want to have one sound for losing the first round, and another to play on losing the second round, which is matchover = 1. It's not working for me by using matchover = 1, the first sound still plays no matter what. Any idea how to fix this?

Cyanide

Re: Matchover = 1 not working
#4  December 20, 2011, 11:48:58 pm
  • ******
  • Legendary XIII
  • I am the eye of the storm to come!
    • New Zealand
    • network.mugenguild.com/cyanide/
What are your triggers for the first sound?

Also, i think i'm completely forgetting something that's kinda important here. Someone else will catch it, or i will check when i get home.


In M.U.G.E.N there is no magic button

They say a little knowledge is a dangerous thing, but it's not one half so bad as a lot of ignorance.

BoyBoyz

Re: Matchover = 1 not working
#5  December 21, 2011, 12:47:46 am
  • ***
I have this for the !Alive state

[State -3, Lose]
type = PlaySnd
triggerall = !Alive && matchover = 0
trigger1 = time = 1
value = 12,0

I need another voice to trigger when I lose the second round. Time = 1 works fine btw, so that's not a problem.

[State -3, Lose]
type = PlaySnd
triggerall = !Alive && matchover = 1
trigger1 = time = 1
value = 13,0

This second trigger where matchover = 1 does not work. The first sound still plays when I lose the second round.

BoyBoyz

Re: Matchover = 1 not working [solved]
#6  December 21, 2011, 06:59:28 am
  • ***
solved with roundno = 2. yay!

NickCox01

Re: Matchover = 1 not working
#7  December 23, 2012, 05:06:24 am
    • USA
    • nicholus6@aol.com
I am having the same problem, but of a different situation, i am trying to make a character use a certain state when they win the final round. My character has a total of four win poses. State 181 is thumb's up, State 182 is Surfin' Bird, State 183 is The Final Fantasy II Victory (SNES), and finally State 184 is The Final Round Win + Walk Off Screen. State 184 is the one i am trying to use for the character whenever he wins the final round, but even though i have State 184 set to display only for the final round, either States 181, 182, or 183 display instead of the State i set for it. What could be the problem here? Am i missing certain codes? Because if i am, i need to know A.S.A.P. so i can fix it up.

Cyanide

Re: Matchover = 1 not working
#8  December 23, 2012, 08:57:55 am
  • ******
  • Legendary XIII
  • I am the eye of the storm to come!
    • New Zealand
    • network.mugenguild.com/cyanide/
You're not having a similar problem to him at all, and bumping his thread is PROBABLY not the best way to get an answer.

Still, the solution is pretty simple.

Trigger your changestate for 184 above all the other changestates for your alternative state. Or restrict your triggers.

If you do something like this

changestate
trigger1 = time = 0
value

changestate
trigger1 = time = 0 && life < 500
value

The higher one will ALWAYS trigger over the lower one because mugen reads the state from top to bottom. That's probably what you're experiencing. Further questions, please re-explain the problem, post your code (probably statedef 180) and create a new topic because this one is not the same as your issue.


In M.U.G.E.N there is no magic button

They say a little knowledge is a dangerous thing, but it's not one half so bad as a lot of ignorance.
Page 1 of 11   Go Up
« previous next »