vgma2 said, November 13, 2016, 10:53:47 pm

If you're using Mugen1.0+, you can try using trigger# = AILevel = 0 for your ChangeState

the character is before mugen 1.0

the CPU and player controls are on diffrent variables

Spoiler, click to toggle visibilty

; ‹C—Í—­‚ß
[State -1]
type = ChangeState
value = 1900
triggerall = var(45) <  1
triggerall = statetype = S
triggerall = Power < 3000
triggerall = ctrl = 1
trigger1 = command = "hold_b" && command = "hold_y"
trigger2 = command = "hold_c"

[State -1,‹C—Í—­‚ß]
type = ChangeState
value = 1900
triggerall = var(45) > 0
triggerall = roundstate = 2
triggerall= !inguarddist && !enemy,numproj && p2movetype!=A
triggerall = power <= 3000
triggerall = p2bodydist X > (200-((p2movetype=H)||(p2statetype=L))*100)
triggerall = statetype != A
triggerall = ctrl ||(stateno=[20,22])
trigger1 = random < 250

AI sometimes ignore the code  (where can only when the p2 is down, far away and not attacking) and keep charging. and sometimes power up even when its player only move

probably going to try changing the AI input

Yeah, AILevel won't work in this case.
If you don't want the AI to use the move at all, maybe you can just Null the AI version of the sctrl.
Make sure the player version isn't changed.

Usually when you Null something out it's for testing. You'd just simply add Null; infront of changestate
So
[State -1,‹C—Í—­‚ß]
type = Null;ChangeState
value = 1900
triggerall = var(45) > 0
triggerall = roundstate = 2
triggerall= !inguarddist && !enemy,numproj && p2movetype!=A
triggerall = power <= 3000
triggerall = p2bodydist X > (200-((p2movetype=H)||(p2statetype=L))*100)
triggerall = statetype != A
triggerall = ctrl ||(stateno=[20,22])
trigger1 = random < 250

All of the triggers would still be read, but it makes testing a lot easier when you can just delete "null;" to get back to where you were.


Also, maybe try
 
triggerall = (roundstate = 2) && (var(45) != 0)  ;AI ON
and
triggerall = (roundstate = 2) && (var(45) = 0)  ;AI OFF
for activating AI changestates. Unless the values can be less than 0 to represent off.

I think this is how I'd set up your changestate.

Spoiler, click to toggle visibilty

[State -1, AI Charge]
type = ChangeState
value = 1900
triggerall = (roundstate = 2) && (var(45) != 0)  ;AI ON
triggerall= !inguarddist && !enemy,numproj      ;you may get debug flood if there's no enemy.
triggerall = power < 3000                                  ;we dont need it to charge at max 3000
triggerall = p2bodydist X > (200- ( (p2movetype=H)  ||  (p2statetype=L) )*100)
triggerall = statetype != A && p2movetype!=A
trigger1 = ctrl ;||(stateno=[20,22])                     ;walking should have ctrl
trigger1 = (random <= 250)                           

When I adjusted the values to match my Ibuki she barely charged. I changed the var and the state no and that's it.

Odb718 said, November 18, 2016, 08:26:05 pm

Usually when you Null something out it's for testing. You'd just simply add Null; infront of changestate
So
[State -1,‹C—Í—­‚ß]
type = Null;ChangeState
value = 1900
triggerall = var(45) > 0
triggerall = roundstate = 2
triggerall= !inguarddist && !enemy,numproj && p2movetype!=A
triggerall = power <= 3000
triggerall = p2bodydist X > (200-((p2movetype=H)||(p2statetype=L))*100)
triggerall = statetype != A
triggerall = ctrl ||(stateno=[20,22])
trigger1 = random < 250

All of the triggers would still be read, but it makes testing a lot easier when you can just delete "null;" to get back to where you were.


Also, maybe try
 
triggerall = (roundstate = 2) && (var(45) != 0)  ;AI ON
and
triggerall = (roundstate = 2) && (var(45) = 0)  ;AI OFF
for activating AI changestates. Unless the values can be less than 0 to represent off.

I think this is how I'd set up your changestate.

Spoiler, click to toggle visibilty

[State -1, AI Charge]
type = ChangeState
value = 1900
triggerall = (roundstate = 2) && (var(45) != 0)  ;AI ON
triggerall= !inguarddist && !enemy,numproj      ;you may get debug flood if there's no enemy.
triggerall = power < 3000                                  ;we dont need it to charge at max 3000
triggerall = p2bodydist X > (200- ( (p2movetype=H)  ||  (p2statetype=L) )*100)
triggerall = statetype != A && p2movetype!=A
trigger1 = ctrl ;||(stateno=[20,22])                     ;walking should have ctrl
trigger1 = (random <= 250)                           

When I adjusted the values to match my Ibuki she barely charged. I changed the var and the state no and that's it.

it still has the same probablys only work sometimes but on a certains  match it starts charged almost the whole round

it works 100 percent when I take off the player code

it works alot better now since a change  the AI varset trigger. (Even when the player trigger is that constant but it did power up for like 2-3 second on a diffrent match)
From var(45) <= 0, var(45) !=1  to var(45) = 0

I was using var trigger from AI that was already there ( it was not specfic)

Spoiler, click to toggle visibilty

[State -1]
type = varset
triggerall = var(45) = 0
trigger1 = command = "ai1"
trigger2 = command = "ai2"
trigger3 = command = "ai3"
trigger4 = command = "ai4"
trigger5 = command = "ai5"
trigger6 = command = "ai6"
trigger7 = command = "ai7"
trigger8 = command = "ai8"
trigger9 = command = "ai9"
trigger10 = command = "ai10"
trigger11 = command = "ai11"
trigger12 = command = "ai12"
trigger13 = command = "ai13"
trigger14 = command = "ai14"
trigger15 = command = "ai15"
trigger16 = command = "ai16"
trigger17= command = "ai17"
trigger18= command = "ai18"
trigger19= command = "ai19"
trigger20= command = "ai20"
trigger21 = command = "ai21"
trigger22= command = "ai22"
trigger23= command = "ai23"
trigger24= command = "ai24"
trigger25= command = "ai25"
trigger26 = command = "ai26"
trigger27= command = "ai27"
trigger28= command = "ai28"
trigger29= command = "ai29"
trigger30= command = "ai30"
v = 45
value = 1

Use DisplayToClipboard to see if var(45) is changing mid-fight. That's the only thing I can think of if nothing else is working.

The other AI code could be messing with it also.
But like vgma2 mentioned, gut the charge move out of the cmd and see if it sneaks into it somehow.


If it does it at different frequencies you just need to change the values until you get them where you want. If the character only power charges a lot vs certain characters, put a trigger in to monitor those matches? IDK how this would be possible, but if it's happening it's happening.
Usually AI plays "harder" the second round if it lost the first. Keep that in mind