Post by: O Ilusionista on September 25, 2010, 11:24:54 AM
This will help to detect if the char is beeing played on winmugen or mugen 1.0
On Winmugen, the players have this IDs
Quote
P1 = 32
P2 = 33
P3 = 34
P4 = 35
But on Mugen 1.0, they have different IDs
Quote
P1 = 56
P2 = 57
P3 = 58
P4 = 59
So, we can use this code to detect which mugen we are using:
Quote
[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.
Post by: ClubSyN-X-TReME on September 25, 2010, 11:58:43 AM
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 PM
you said id 56 is a 1.0 character right?
well:
(http://clubsyn-x-treme.net/-X-HQ-/uploads/images/Cs-X--1285430655-U1.png)
(http://clubsyn-x-treme.net/-X-HQ-/uploads/images/Cs-X--1285430709-U1.png)
This is winmugen and you can see the ID is clearly 56.
So what you stated isn't always guaranteed.
Post by: O Ilusionista on September 25, 2010, 12:17:54 PM
Quote
So what you stated isn't always guaranteed.
Quote
This is a tuto made by SonSon3000...
About the ID 56, this is weird. How you get that? in which mode?
Quote
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.
Post by: ClubSyN-X-TReME on September 25, 2010, 12:32:39 PM
(http://clubsyn-x-treme.net/-X-HQ-/uploads/images/Cs-X--1285432306-U1.png)
Winmugen team mode
And in my earlier post, it was arcade "single" mode
Post by: O Ilusionista on September 25, 2010, 12:54:04 PM
Post Merge: September 25, 2010, 04:08:20 PM
CODE UPDATED
Quote
[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"