DYNBATTLECHOICES

You mean make it so that a basic attack doesn't deal damage and doesn't create a damage number popup? I don't believe so, no. The solution I've found for my own project is to make "Fight" yet another skill, and entirely remove the default Fight battle command. Of course, that means you need to handle the animations for basic attacks with scripting, and you don't have the option of using the actor-based weapon animations. It's doable, but it involves hacky tricks involving conditions which I don't have time to describe right now. X)

That's part of it, but really I was referring to having a "doing a technique" status condition which I slap onto an actor. This condition causes all actors to become fully invisible while it's on them. Then I show a battle animation on the target enemy which includes the actor swinging a weapon or whatever, and immediately after it's done (which involves another hacky trick of using a "Wait 0-tenths of a second" command instead of the battle animation command's built-in wait-for-animation-to-complete option) I remove the status condition from the actor. The effect from the player's perspective is that the actor blinks over to the enemy and strikes them, then blinks back. It doesn't look quite as nice as RM2K3's built-in weapon attack animation system, which can show the actor running over to the enemy and back, but it's sufficient for my purposes.

The big problem with this sort of method is that you have to keep track of which animation you want to show and call it in script. Before I created DynParams, my project's combat code had huuuuuuge long pages that listed conditional checks for every possible battle animation that might be needed in a given situation. Now it's far more manageable because DynParams can just overwrite the battle animation number in a single battle animation command. You still need code to decide what that battle animation number is, though.