Quote Originally Posted by Ladon View Post
Again, still not addressing my point. The three examples of controls I gave cannot be restricted to NOCOMBAT extensions because there is legitimate use of them in combat. Also for WoW they use NOCOMBAT to specific actions that normally cannot be used in combat. This is simply in place to prevent someone from circumventing a normal restriction in the game via API call. They can't be used to be like "while in combat your can't read player HP, run a comparative then cast a heal spell."
I don't think you understand what the NOCOMBAT thing can be used to break your scenario very easily.

For your scenario to work, there are three requirements:

1. Performing a health check.
2. Creating a target.
3. Performing an action.

Adding the NOCOMBAT clause to any of the 3 will break this automation. But generally, finding a target is an API that does not exist in any game. When you can automate target creation is when you can automate everything else.