AI taking over

[prnzokoshiro]

I have a few chars, and have noticed a few chars in full games I can't change where, after a few rounds or so, the AI activates in the char I'm using and takes over playing for me.  I've studied the files and can't find a clue as to where the problem lies or what's causing it.  Can anyone help?

[Acey]

List one or some of the characters,
Which screen pack
What is the exact situation that the AI is activating.

[ExeLord]

That's Skynet... It started...
Jokes aside - what Acey said.

[prnzokoshiro]

cvs2_leo, cvs2_nool, cvsmature

I can't think of any others off the top...

it happens in any screenpack I put them in, both winmugen and 1.0

[Cyanide]

Which version of winmugen. The old AI activation, especially the XOR method from Winane are somewhat broken in 1.0. However 1.0 has AIlevel which is instant and easy so changing them for that is simple enough.

If it's winmugen, you have bad AI activation. If it's 1.0, the old methods are slightly broken and you want to update them to use AIlevel to turn on the variable instead of the old methods.

[prnzokoshiro]

so how do I fix the bad AI activation to work with winmugen (cuz that's where they fit in)?  am I going to have to update them to 1.0 with AILevel and what not? 

[Cyanide]

So you're using them in winmugen and they're breaking? Whoever made them has made a bad job of winane's XOR method. Wipe it, implement impossible commands.

I have never bothered learning how winane's method works because it's complex and too simple to mess up. There is a tutorial on it at guild, follow it backwards to delete everything.

[prnzokoshiro]

I don't know about AI much... should I put things like U+D+F+B, is that what you mean by impossible?

[Cyanide]

First get rid of the currently implemented method. This may be annoying as it makes use of 3 variables in a number of states including 2 of the negative states.

The impossible command method is well documented.

Alternatively, try the characters in 1.0 and see if they work
Change their mugenversion to 1.0 in the .def file
Figure out what variable the AI makes use of and insert the following 2 things in the cmd

[state -1]
type = varset
trigger1 = AIlevel > 0
v = 59
value = 1

[state -1]
type = varset
trigger1 = AIlevel = 0
v = 59
value = 0

Normally i would not include the second one, but this means if it ever activates under human control it's reset. This is also assuming these characters use var(59) for their AI. Change it if necessary. This method will not work in anything other than 1.0.