Blitz2, Swdtech2, Morph2, etc...

A new code for swap the toggles command? too much annoying... sounds like revert would be almost for sure the first command to overwrite with the code of a new command

So... 5 different morphs -> 4 command codes replaced from 4 copies of morph code
+ 8 bytes to add on SRAM?

No. 4 bytes plus one extra bit for each if you want to have it in later game like the original morph. A byte contains 8 bits.

Just misread, i guess... if i didn't know that a byte contains a bit, it would have been very worrying!

Say i want to have it from the beginning... do i have to do the same, and use the event that unlocks morph at the beginning?

The easiest way to enable Morph by default is to simply skip the command that nulls it out in battle. At the rom address 0x25410, there are two bytes "F0 22". This is a branch instruction to null out Morph, but if you replace the bytes with "EA EA" then it will never happen.

Since you don't need to display names for SwdTech and Blitz, there should only be two major places where you would check which character is active and branch. The first is whatever byte controls how many skills the character knows; you'd need a second one for your second skill. The second is what skill is selected; you'd just start with a different offset for the different move set. Blitz has an additional hitch for the button combo, which would be a third place to branch if you wanted.

Here's another one: say i wanna mix leap and tools features(random example)...
I wanna be able to use tools command, but the command must be available only in the formations in which leap is allowed to the player... something like i'll be able to use tools only when i'm in Magitek lab.

My idea would be to partially overwrite the leap command feature so that the part in which is determined if the formation allows to use the command or not, is still there, but the rest of the code that would make leap the character is replaced from the code that makes you use the tool.

Any idea on how it could be implemented this new command?

The code governing whether or not a command is available is at C2/53C9. It's actually not part of the Leap code; the same code governs the availability of Magic, X-Magic, Morph, Dance, Leap, and Lore. (Lore is never actually checked, as Strago knows three Lores at startup, but the code is in the game to make it unavailable if no Lores are known.) You could theoretically co-opt the Lore check for whichever command (Tools, or whatever) you want to make available only at certain times, leaving Leap intact, or you could make use of the Leap check itself. Since the code that governs availability doesn't have anything to do with what the command does, it's a simple matter to alter the command you're dealing with -- just point the relevant code to your new command, instead.

I haven't dealt much with Leap/Rage yet, since I'm not using them in my hack, so while a quick glance shows that Leap's availability is governed by a bit in $11E4, I don't know much about how it's set; it looks like it's set in C0 from the formation data, maybe?

This is quite interesting... btw for the use that i intended to have with that command i believe it must have exactly the same restrictions applied to leap command, which looks like it's a unique restriction, compared to magic, X magic, lore, etc.
is it possible to duplicate that restriction?

Okaaay. Looking at this a little more thoroughly, it looks like you don't really need to deal with Leap at all. Basically, current map is stored in 16-bit $1F64. Just run a CMP against that for whatever map(s) you want the command to be run on. It's much less complicated than trying to use the Leap functionality, which is a combination of 'particular locations on world map' + 'particular monster formations'.

With maps you mean formations or backgrounds(or something else)?

Thinking to that better i don't even need of the original leap command... if i just do what i said before(replace part of the leap code), then i solved the problem...
Btw for my purposes it must have the formation restriction.