You can use the stance change feature

The main thing you need to work on is switching prefabs to the transformed version

The stances already let you change the "walk speed" and you can also change the attack damage of the moves.

The main problem is the shift of prefab when you activate the stance switch . And also put a timer to auto change back when it runs out

Also particle affect can already be added to basic walk and idle animations no coding needed

You could potentially change the move editor to make a move that is time sensitive can't you.

It's seems like that would be easier with less coding than the way your going about currently.

Hi mate,
I'm trying to wrap my head around the approach you are taking with this functionality. Do you want a completely different character model for the transformation, or do you want just a few different body parts visible (ie. glowing golden hair, a tail, etc.)?

The error you are getting COULD be caused by accidentally setting the "prefab object" by dragging and dropping the instance of the object from the Heirarchy, instead of the Prefab object which would be in your Project tab. It's a pretty easy mistake to make when you're so focused on 100 things at once. If this isn't the problem, then try to track down any code you may have added or changed and start commenting things out until the game runs properly again.

How did it go? Were you able to get it up and running?
I usually have 3 or 4 backups of my project so I can go back a few hours or a few days if there's problems. If your project keeps having that problem, you might want to create a new UFE project just to get a clean copy of any classes you might have accidentally broken. Replace one file at a time if commenting out changed code doesn't work. Try also taking out any new properties you may have added to classes (for example, new prefabs for transformation forms), cleaning, building and loading the game, and see if it boots up.

Hey thank you so much!  You were right about assigning a prefab from the heirarchy rather than a prefab in the assets folder.

So I cleared that first error, and now I get this response.  The game spits these errors now.  The weird animation thing is just to use as a test

So im happy the game can run at the start.  My goal currently is just to have the consol print out that Ive triggered a move that triggers a stance change as a power up like in the image below

so these are the lines each error points to

this is what prints out to the console from MoveSetScript.CS from line 315 and i get another error on Line 316

Thank you so much for your help.  Yea I made sure to have at least 2 other back ups of previous versions before I make huge changes.  I try to put all of my free time into this since I work full time at a hospital right now.  Im currently tracing through these errors and trying to knock one out at a time.

Ok so im thinking I should move away from stance changes like i originally thought because MoveSetScript calls the function FillMoves which tries to destroy the MecanimControl component.

I tried commenting these out for now but it breaks the game completely.

  You say visibility, and I remember you mentioned to add a percent modifier, a bool in MoveSetScript and a duration for the transformation.  I havent changed physics or control script yet because im a little confused on how to modify values in those scripts during a transformation.

Could you guide me a little bit more? Ive been poking at different resolutions to these errors, but it seems to always boil down to using a stance change as a bad choice.

I hope this works.

I was thinking this myself, and it seems like it would work if you have the two meshes as long as both are deformed with same armature (i.e. One set of bones). But this would require the imported model itself have both meshes built in. That's a whole lot of "back to the drawing board".  If I had such a model it would be easy to animate the change

No worries. For Animelee's transformation speed modification, we use a float such as transformationSpeed;

By default, this value is always 1f, especially in non-transformed state. We do this because it substantially reduces the amount of modifications we need to make to the existing equations.

I'm not a different machine that doesn't have our source code so I don't have our project on hand. What you'll want to do is just insert your "transformationSpeed" float value into the PhysicsScript functions that affect movement speed. You'll want to modify both the move forward, move backward, and jumping distance. Simply multiply those values by your "transformationSpeed".

We use a targetTransformationSpeed and expose that in the character editor. When the character transforms, we set transformationSpeed = targetTransformationSpeed;

That way, you can set the targetTransformationSpeed to anything you like in the editor. If you set that value to 1.25f, the character will be 25% faster. If you set it to 2f, that character will be twice as fast as fast.

That's how Freiza does it, that's how Goku does it, so that's how we do it.

For mesh model changes in the character, that is how I would advise doing it. You can toggle the meshRenderer for each character state (normal, transformed), by building a functionality into the moves. Naturally, the easiest way to manage that is to have both meshRenderers rigged to the same joint, but it seems like you know what you're doing there.

We added a bool value to moves, (specifically in the particle effect section), so that the controlScript function of creating a particle effect can trigger the transformation. This isn't necessary and there are much neater ways to do it, but for Animelee, it saved us a lot of time to attach the transformation this part of the script, since all transformations occur the exact same way and are always attached to a "special effect". Also, this part of controlScript is very reliable, easy to understand, easy to edit, and never fails due to unexpected overlaps of actions and states.

That is so helpful to know thank you.  My semester is about to end so Ill be full time on this until it works for the next month.