How Do I Stop A Characters Pallet Selector From Starting?

Yo whose Blazblue Takanna is that please? 

By the way, I think most "MUGEN in-game palette selectors" are made of MUGEN Helpers and Explods and a bunch of MUGEN Variables......if you can locate these then you can just remove them safely.....so after you give me information of that particular Blazblue Takanna then I can take a look at its possible MUGEN Helpers and Explods which are responsible for its "MUGEN in-game palette selectors"....

The MFFA site that i got it from is down but hopefully this is the same Taokaka that i have. Here is the link:

http://mugenarchive.com/forums/downloads.php?do=file&id=5265

Hmmmm...I don't want to register another MUGEN forum........anyway, I just found another file download provided by the MUGEN author (SXVector) who mugenized this BBCSE Taokaka:

https://mega.nz/#!zEcUTS7J!YUDikHCUfblOuaCf-OhHwRJho1h9TG0GOjHBacKQqqE

As a result, I am using this mega.nz Taokaka version for your MUGEN need.

Alright, I found the MUGEN Helper responsible for Taokaka's "MUGEN in-game palette selector".
This is the MUGEN Helper state controller at the bottom in the "Taokaka_CSE.cmd" MUGEN file:

Code:

[State ]
type=helper
trigger1=!numhelper(256)
trigger1=roundno=1&&stateno=5900
id=256
stateno=256

Now try to change this lines of MUGEN code to this:

Code:

[State ]
type=helper
triggerall = AILevel = 0
trigger1=!numhelper(256)
trigger1=roundno=1&&stateno=5900
id=256
stateno=256

>> the "triggerall = AILevel = 0" is used to make sure the Taokaka's "in-game palette selector" MUGEN Helper can be used only when Taokaka is controlled by the human player in MUGEN1.0.

To make everything safe, you may also want to do something to the Taokaka's "in-game palette selector" MUGEN Helper itself:

Also this is the [Statedef 256] in the "Taokaka_CSE_-3.cns" MUGEN file:

Code:

[Statedef 256]
anim = 9999
ctrl = 0
[State ]
type=assertspecial
trigger1=ishelper(256)
flag=intro

[State ]
type=varset
triggerall=ishelper(256)
trigger1=!time  ;;  Map on Initiation to PalNo
var(21)=root,palno

Now try to add a DestroySelf MUGEN state controller in this Statedef 256:

Code:

[Statedef 256]
anim = 9999
ctrl = 0
[State ]
type=assertspecial
trigger1=ishelper(256)
flag=intro

[State 256, disable AI's MUGEN in-game palette selector]
type = DestroySelf
trigger1 = Root, AILevel != 0
ignorehitpause = 1

[State ]
type=varset
triggerall=ishelper(256)
trigger1=!time  ;;  Map on Initiation to PalNo
var(21)=root,palno

>> this DestroySelf is used to kill the Taokaka's "MUGEN in-game palette selector" when Taokaka is controlled by the MUGEN A.I. in MUGEN1.0.

If it still doesn't work for you, then please let me know more.

My mugen crashed and here is the error code:

Code:

Error detected.
AssertSpecial parameter flag missing.
Error parsing [State 190,2]
Error in [Statedef 190]
Error in Taokaka_CSE.cns
Error loading chars/Taokaka_CSE/Taokaka_CSE.def
Error loading p1

I-Skorp-I wrote:

My mugen crashed and here is the error code:

Code:

Error detected.
AssertSpecial parameter flag missing.
Error parsing [State 190,2]
Error in [Statedef 190]
Error in Taokaka_CSE.cns
Error loading chars/Taokaka_CSE/Taokaka_CSE.def
Error loading p1

Yo what did you do to the AssertSpecial MUGEN code in [Statedef 190] in the "Taokaka_CSE.cns" MUGEN file?
The mega.nz Taokaka version I downloaded and checked has the AssertSpecial like this in [Statedef 190]:

Code:

[State 190, 2] ;Assert this until you want "round 1, fight" to begin
type = AssertSpecial
trigger1 = 1
flag = Intro

I guess you wanted to disable it right?  But somehow you only took the flag = Intro out right? 
If you want to disable this AssertSpecial MUGEN state controller then you can just change it to:
type = Null;AssertSpecial
or just delete the whole block of these MUGEN code lines.
If you want to make the intro animation shorter then you have to edit the [Begin Action 190] and [Begin Action 191] in the "Taokaka_CSE.air" MUGEN file, either in your text editor or your Fighter Factory.
Or, just in the same [Statedef 190], you can change the ending ChangeState to stance from these lines of MUGEN code:

Code:

[State 190, 4] ;Change to stand state
type = ChangeState
trigger1 = AnimTime = 0
value = 0

to these lines of MUGEN code:

Code:

[State 190, 4] ;Change to stand state
type = ChangeState
;trigger1 = AnimTime = 0
trigger1 = Time >= ###
value = 0

>> the Time >= ### is the MUGEN state time passed in 1/60 seconds.

I-Skorp-I wrote:

Never mind bro i fixed her haha i accidentally deleted the flag. haha but thanks to your advice i fixed her so she works perfectly find now...I'm forever in your debt Borewood!  

Don't mention it   We can both learn some more MUGEN fun day by day!

By the way, SXVector's MUGEN stuff is usually so cool!   It is too bad his MUGEN web site mugencoder.com has gone........

I-Skorp-I wrote:

borewood2013 wrote:

I-Skorp-I wrote:

Never mind bro i fixed her haha i accidentally deleted the flag. haha but thanks to your advice i fixed her so she works perfectly find now...I'm forever in your debt Borewood!  

Don't mention it  We can both learn some more MUGEN fun day by day!

By the way, SXVector's MUGEN stuff is usually so cool!  It is too bad his MUGEN web site mugencoder.com has gone........

Yea that truly is sad news...btw i have one last question...why is it that after having my mugen play on it's own after a while or when i play it for awhile he suddenly closes without any errors? could it be that it ran out of memory?

Lucky SXVector's YouTube channel is still there: https://www.youtube.com/user/SxVector/videos

About your MUGEN1.0 "suddenly closes without any errors" thingy, it happens to me too, when I try to load up more than one (1) "heavy-duty MUGEN characters/stages".  This can be the system memory problem MUGEN1.0 has.  Some say MUGEN1.1 does not have this system memory problem........you can give it a try to see....

This MUGEN1.0 "suddenly closes without any errors" thingy, happens to some other MUGEN folks too, you can read about some at MFG here:
http://mugenguild.com/forum/topics/ssfiv-abel-and-oni-public-beta-released-borewood-update-2014-155223.msg1944019.html#msg1944019

I-Skorp-I wrote:

Oh ok and i have mugen 1.1. i don't have 1.0 lol

Well, even your MUGEN1.1 has such system memory problem!?

Ok, then what MUGEN screenpack/motif and which MUGEN characters and stages and lifebars...etc. were you using when that unknown MUGEN crash happened please?

And perhaps you can try to use a default MUGEN1.1 package to do a test with one thing at a time to see.....

I-Skorp-I wrote:

I have an mugen 1.0 screenpack i think it's called X mugen or something like that but it was crashing the same way when i had 1.0 so it can't be that...and it crashes regardless of the character and stage lifebars that i use.

So you mean you are using a MUGEN1.0 screenpack in your MUGEN1.1?

I have no idea because I don't use MUGEN1.1 except for testing MUGEN1.1 exclusive stuff.........if you say "regardless of the character and stage lifebars that i use" then it might be a screenpack problem.......you may want to try generic default MUGEN1.1 installation to try to see.......