I'll place a scenario first. You have an animation that loops while a track is playing. You create a custom pause button that tells the animation to freeze on it's current frame and resume again when unpaused. Easy enough with a bit of knowhow.

A problem arises, though, when you use physical buttons on your keyboard to control software, as do I. Obviously, pausing from your keyboard bypasses your custom button and the animation will keep playing since it's a raw signal.

So, the idea is a keyword that detects incoming control signals and converts them into a software click. For example, adding "externalpause" to a button object will detect an incoming hardware pause and execute via the button instead of directly controlling Xion.

That's a really roundabout way of doing it. Much better solution would be to simply hook animations to actions rather than button presses, so that the actual paused state of the player triggers animations, rather than the press of the pause button itself.