Lord Vectra

I just tried it in battle and it 100% works. All event methods work in-battle. If you change a character's graphic in-battle, give them levels/XP, or completely remove/add a party member, it will work. Can you tell me what you thought specifically wasn't going to work?

When you use it in battle, are you not getting the correct level? I'm pretty sure this works in-battle, but I'll check when I get time.

You have two choices: 1. On the third tab in the event commands, there's a "Change Save Access" command that you can use to disable it. 2. Or to get rid of the save button, go to the script editor, go under WINDOWS, go to Window_MenuCommand, line 40 where it says add_save_command and delete that

Without a script, the latter seems like the best option. I don't know any script that does what you want nor would I even know what it would be called if it did exist lol. What I will add, however, is you probably want this: https://himeworks.com/2013/05/untargetable-state/ You can give him the untargetable state where he can't be targeted at all. After that, the rest should be easy.

Can you rephrase your issue?

Welcome!

It has been fixed!

I think a more simpler way of explaining it, @Kayzee, is let's take these 3 properties of a spell: Damage, Duration, and Range. If a fire spell does 50dmg for 4T and hits enemies within 4 tiles, if it's broken, you have options to balance it. You can decrease the damage per turn to compensate for the big range, decrease the duration if 4T is too long (especially if you have other skills/spells that have extra effects if person is burning), reduce the range to make it more of a single-target overtime burst damage, decrease the damage but increase the duration so it takes longer to do the same damage, and the list goes on. Granted, this does make it more complicated, but I guess it depends on the player what is considered too complicated and what is considered a great addition. @Saireau may also be referring to "ghost stats." It's stats that is in the background that the player is unaware of. An example is the variation. When you use the skill, you don't know the highest dmg and lowest dmg it can deal, so you kind of guess by using it a lot (if you're paying attention to the dmg dealt). Variance is the "ghost stat" in this case where the player does not need to keep track of it. About LUK: I always replace LUK and turn it into any stat I want, then I null out it's effect in the default script. In XP, I learned how to just create my own custom stats (and XP doesn't have LUK), but in VXA, for example, one project I was working on had it as "distance" which did not also decide what would hit you or not (depending on distance from others) but also decided damage of your gun (ex: Shotguns did more damage the closer you were). On my latest VXA proj that's on standby, I don't have LUK even show up in the menu because I couldn't think of anything for it lol.

Welcome to Central!

Welcome to Central!

Welcome to Central!

Hello!

My only real issue with it is it dumped the old way of doing animations because the way they have it now it SUPER complicated to a much greater degree,

Make a parallel process common event that changes him back.

Welcome!