Detcting Winmugen or Mugen 1.0

[O Ilusionista]

This is a tuto made by SonSon3000, and I think that this would help many people.

This will help to detect if the char is beeing played on winmugen or mugen 1.0

On Winmugen, the players have this IDs

P1 = 32
P2 = 33
P3 = 34
P4 = 35

But on Mugen 1.0, they have different IDs

P1 = 56
P2 = 57
P3 = 58
P4 = 59

So, we can use this code to detect which mugen we are using:

[State -2, VarSet]
type = NULL
triggerall = TeamMode = Single
trigger1 = TeamSide = 1
trigger1 = ID = 32
trigger1 = var(0):= 11
trigger2 = TeamSide = 2
trigger2 = ID = 33
trigger2 = var(0):= 12
trigger3 = TeamSide = 1
trigger3 = ID = 56
trigger3 = var(0):= 21
trigger4 = TeamSide = 2
trigger4 = ID = 57
trigger4 = var(0):= 22

[State -2, VarSet]
type = NULL
triggerall = TeamMode = Simul
trigger1 = TeamSide = 1
trigger1 = ID = 32 || ID = 33
trigger1 = var(0):= 11
trigger2 = TeamSide = 2
trigger2 = ID = 34 || ID = 35
trigger2 = var(0):= 12
trigger3 = TeamSide = 1
trigger3 = ID = 56 || ID = 57
trigger3 = var(0):= 21
trigger4 = TeamSide = 2
trigger4 = ID = 58 || ID = 59
trigger4 = var(0):= 22

[State -2, Which Mugen?]
type = DisplayToClipboard
trigger1 = var(0) = 11 || var(0) = 12
text = "WinMugenHack"

[State -2, Qual mugen é qual]
type = DisplayToClipboard
trigger1 = var(0) = 21 || var(0) = 22
text = "Mugen 1.X"

CODE UPDATED
-----------------------------

I try - with no success - to identify the screen resolution, using a code that could be used both in Winmugen and Mugen 1.0.

I noticed that even if you use 1280x720 resolution and use a helper to make a DisplayToClipboard of FrontEdgeDist, the result is ALWAYS 320.

[ClubSyN-X-TReME]

O'illu, these ID's especially in winmugen are not always the same.
And I seen the 1.0 id's on winmugen also at times.

The only true way is to detect a 1.0 characters is through its def file "mugenversion" line
Post Merge: September 25, 2010, 12:06:17 PMyou said id 56 is a 1.0 character right?

well:




This is winmugen and you can see the ID is clearly 56.
So what you stated isn't always guaranteed.

[O Ilusionista]

So what you stated isn't always guaranteed.

This is a tuto made by SonSon3000...

About the ID 56, this is weird. How you get that? in which mode?

O'illu, these ID's especially in winmugen are not always the same.

I think that is missing a TeamMode trigger there, but you will get the right numbers using that.

[ClubSyN-X-TReME]

Winmugen team mode

And in my earlier post, it was arcade "single" mode

[O Ilusionista]

that is weird. I nevet got an ID 56.
Post Merge: September 25, 2010, 04:08:20 PMCODE UPDATED

[State -2, VarSet]
type = NULL
triggerall = TeamMode = Single
trigger1 = TeamSide = 1
trigger1 = ID = 32
trigger1 = var(0):= 11
trigger2 = TeamSide = 2
trigger2 = ID = 33
trigger2 = var(0):= 12
trigger3 = TeamSide = 1
trigger3 = ID = 56
trigger3 = var(0):= 21
trigger4 = TeamSide = 2
trigger4 = ID = 57
trigger4 = var(0):= 22

[State -2, VarSet]
type = NULL
triggerall = TeamMode = Simul
trigger1 = TeamSide = 1
trigger1 = ID = 32 || ID = 33
trigger1 = var(0):= 11
trigger2 = TeamSide = 2
trigger2 = ID = 34 || ID = 35
trigger2 = var(0):= 12
trigger3 = TeamSide = 1
trigger3 = ID = 56 || ID = 57
trigger3 = var(0):= 21
trigger4 = TeamSide = 2
trigger4 = ID = 58 || ID = 59
trigger4 = var(0):= 22

[State -2, Which Mugen?]
type = DisplayToClipboard
trigger1 = var(0) = 11 || var(0) = 12
text = "WinMugenHack"

[State -2, Qual mugen é qual]
type = DisplayToClipboard
trigger1 = var(0) = 21 || var(0) = 22
text = "Mugen 1.X"