BUG: ikaruga chars in tag mode have a funny bug

[mrkarate505]

when i select any ikaruga kof char in tag mode they are dead and jumping out of the screen like frogs LMAO

[K4thos]

not a bug, Character has a conflict with state numbers used by ikemen go default tag system. As per wiki ikemen go reserves following states:

StateTagEnteringScreen = 5600 StateTagLeavingScreen = 5610 StateTagWaitingOutside = 5611 StateTagJumpingIn = 5620 StateTagLanding = 5621

[mrkarate505]

thanks

[mrkarate505]

I tried to solve it but couldn't solve it. the character transition during tag mode worked but more bugs appeared in the chars, for example all kyo made by ikaruga have moves that make p2 fly through the wall, "ex k' xi" makes p2 run behind the wall during a special move

[Kuroteba]

Did you change the P2StateNo or TargetState value of the technique that causes the bug?

[mrkarate505]

not yet, i just deleted the states "5600, 5610, 5611, 5620,5621" but i will test the ones you said now

[NeatUnsou]

After all, each state number is just a conflict, so rewriting the following file state numbers will work perfectly for almost all characters.

common.const

; tag.zss states
StateTagEnteringScreen = 5600
StateTagLeavingScreen = 5610
StateTagWaitingOutside = 5611
StateTagJumpingIn = 5620
StateTagLanding = 5621

tag.zss

[StateDef 5600;

[StateDef 5610;

[StateDef 5611;

[StateDef 5620;

[StateDef 5621;

For example

common.const

; tag.zss states
StateTagEnteringScreen = 985600
StateTagLeavingScreen = 985610
StateTagWaitingOutside = 985611
StateTagJumpingIn = 985620
StateTagLanding = 985621

tag.zss

[StateDef 985600;

[StateDef 985610;

[StateDef 985611;

[StateDef 985620;

[StateDef 985621;

The number 5600 in the tag system has no special meaning, so the user may rewrite this number. It would be better to change this default numbers.

[K4thos]

7f83118901f6427488bbd522c974f8af817cfb24 added const support for cns/zss StateDef numbers and modified ZSS files shipped with engine to take advantage of it, so in next build it will be possible to solve this compatibility problem just by pasting state numbers of your choice to character's [Constants] group (or modifing common.const to implement the change globally for all characters)

[NeatUnsou]

Added const support, users can now easily change the tag state number. Therefore, I feel that there is no longer a need to keep the default tag state number as it currently is. The number conflict problem can be solved by changing the state number in common.const, but forcing all users playing tag to make this change is not a good workaround. Can't close this issue on ikaruga chars without changing the common.const state number on github to another number that is less likely to conflict.

[potsmugen]

I understand the sentiment behind wanting to keep all system states between 5000 and 5999 though. And Elecbyte did ask people to not use those numbers for anything.