problem with multiple transformations

[3rdstring]

Hello I'm making a mugen project and I'm having a problem the my char going through its fourth transformation instead when the move is performed it goes back to the ssj standing state can someone please help or at least have any idea what's wrong ty

[Cyanide]

Urgh, transformations. So much effort for such a minor effect.

Anyway, if you have coded stand correctly the animation should be increasing on the basis of what transformation you're on. I would need to see the code for state 0. If you haven't overridden state 0, that's where your issue lies and something needs to be fixed there.

[O Ilusionista]

Saddly, this is (one) of Mugen's Achilles heel. This will require some custom codes to work and works better in closed games.
Its about time to Mugen to accept it.

[3rdstring]

this is what i have

; Stand
[Statedef 0]
type = S
physics = S
sprpriority = 0

[State 0, 1]
type = ChangeAnim
triggerall = var(7) = 0 &&  var(18) <= 0
trigger1 = Anim != 0 && Anim != 5
trigger2 = Anim = 5 && AnimTime = 0 ;Turn anim over
value = 0


[State 0, 1]
type = ChangeAnim
triggerall = var(7) = 1
trigger1 = Anim != 10000 && Anim != 10005
trigger2 = Anim = 10005 && AnimTime = 0 ;Turn anim over
value = 10000

[State 0, 1]
type = ChangeAnim
triggerall = var(7) = 2
trigger1 = Anim != 20000 && Anim != 20005
trigger2 = Anim = 20005 && AnimTime = 0 ;Turn anim over
value = 20000

[State 0, 1]
type = ChangeAnim
triggerall = var(7) = 3
trigger1 = Anim != 30000 && Anim != 30005
trigger2 = Anim = 30005 && AnimTime = 0 ;Turn anim over
value = 30000

[State 0, 1]
type = ChangeAnim
triggerall = var(7) = 4
trigger1 = Anim != 40000 && Anim != 40005
trigger2 = Anim = 40005 && AnimTime = 40000 ;Turn anim over
value = 40000

[State 0, 2]
type = VelSet
trigger1 = Time = 0
y = 0

[State 0, 3] ;Stop moving if low velocity or 4 ticks pass
type = VelSet
trigger1 = abs(vel x) < 2
trigger2 = Time = 4
x = 0

[State 0, 4] ;Are you dead?
type = ChangeState
trigger1 = !alive
value = 5050

[State 0, 4] ;fly?
type = ChangeState
trigger1 = pos y != 0
value = 50
ctrl = 1

;---------------------------------------------------------------------------

[Cyanide]

So all those are exactly the same. There are a couple of further options

1 is whatever move you're doing is causing that variable to decrease for some reason. This could be an oversight or something in state -2. Basically that var MIGHT be getting altered by the problem state somehow, double check.

2 is that the animation isn't what you think it is. You have potentially re-used an animation number that you've used previously for a different set, or even the sprites aren't what you think they are. Load the document with notepad and use the find tool to double check you don't have duplicate animations. Also scroll through your whole SFF to make sure you haven't doubled the sprites up as well.

[3rdstring]

I'm still not seeing anything I'm sorry for being such a noob but I rather ask than edit over some other creators stuff and do my own. There not to many tutorials for transformations except for singles transformation. Is there any kind of way I can email my char to you because I still have a lot of spriting to do

[Cyanide]

If it's not gigantic it'll go to my hotmail OK.

[3rdstring]

No I think so far it's just 5mb still got a lot of move to put in the char being slowed down because of transformations well at least the 4th transformation what you email

[3rdstring]

I'll send it when I get off from work and thank you

[3rdstring]

Hey cyanide what is your hot mail address I'm off work the next 2 days let me know when your ready

[Cyanide]

It's at the bottom of my webpage.

[3rdstring]

Did you ever get the email cyanide and did you see what I did wrong in there

[Cyanide]

Welp, that was easy.

I have just had a look to see what's happening. In state 7002, you set the variable to 1 again. Change it to 4 and you're fine.

Also, for this sort of thing i STRONGLY recommend a more standard increase in your states

7000 = Super Saiyan
7003 = Super Saiyan 3
7005 = Super Saiyan 2
7002 = Super Saiyan 4

Bad plan, and actually not too surprising you stuffed up the varset because it's not at all obvious in a logical sense where you're up to. A couple of other tips. Always comment your statedefs. If each of these was labeled with
;Super Saiyan transformation 1
; Super Saiyan Transformation 2

i wouldn't have needed to do so much work (not that it was difficult work) and it's an excellent idea to comment important explods and/or variables so you can remember what they're for. You have for example, 2 explods in each of these states. Which is which without looking at the .air file to find out? Comment them. Highly useful, especially when you're starting out. You can get lazy later.

[3rdstring]

Lol thank you very much cyanide I have it working now and you were right I was being lazy  and thanks for the advice