[Angelol]

I think you never had the case of a target moves behind you (+delay) while casting the final mudra (Raiton) and your profile tries to use raiton which will be cancelled because of the moving mob, right?

This problem got nothing to do with combat status, OGCD spells, GCD spells, or non mudra spells.

It's just a mudra problem itself.

Everything is working perfectly. Except the part when your bot tries to cast Raiton / any other Ninjutsu and in the same time your target walks out of your PoV and interrupt your Raiton cast by doing so. (GCD activates, but Raiton doesnt cast.)

That is the whole point of the problem! You will have the animation (or half the animation), the bot will think that the ninjutsu was casted, but in game it actually failed and the system tells you "Target not in range" (Refer to the first paragraph of Post #252)

So with "Missing Mudra" setting, no other skill can be casted while you still have the mudra buff - that's good because you won't have to deal with the GCD skills.
But what if you don't set the first mudra in the chain to offGCD:True? The bot will loop back to the same ninjutsu again - exactly the case you described in #253.
So with the offGCD set to True, when the bot failed to cast the ninjutsu properly, no GCD skill will be casted, so it will not go into oGCD state, and the first mudra will not be casted again because it requires the oGCD state to start with. So the whole bot will just sit there doing nothing until the mudra buff runs out. This is good enough for us to cast the ninjutsu manually.

This worked perfectly while the bot is trying to cast Raiton on Minotaur (Fractal Continuum) that uses Disorienting Groan to the other side of the arena.

The Combat Status thingy is just there to solve the delay in changing target when mobs die- it have nothing to do with the aforementioned problem. If you don't do so, everytime you lose the target in the middle of a mudra chain, the subsequent mudra will not be casted until you choose a new target.

Setting first mudra to true = dps loss (even if its just 0.x% dps) since the bot waits for the next spell to be used, before casting mudra. (nope, its not casting mudra if mudras get rdy while being in a gcd)
Setting first mudra to false = the bot instantly uses mudra as soon as it gets ready without waiting for the next spell to be casted.

And for the loop thing, I found another solution, i think. (Missing Mudra Buff got nothing to do with the loop thing.)