My understanding of its working, are based on explanations I've seen posted and are not necessarily entirely accurate.
And I don't know anything on the programming end.



Inner Space is a program that runs.
IS Boxer is an interface for the configuration of Inner Space.
IS Boxer is free, while Inner Space is a subscription based program.

Inner Space runs as a layer between Windows and whatever it launches.

Some games require a window to be the active/focused window, in order to receive keyboard or mouse input.
Because Inner Space exists as a layer between the Game and Windows, the game can be made to believe it is the Active/Focused Window, in Windows even if it is not.
That is configured via a check box in IS Boxer.

Once Lax has added the game, you can select it as a Profile which checks the appropriate things for a given game; prior to that, you can add the relevant executable and check the boxes that you want to...
If the game has a Configuration File, for game settings, adding the game via the Profile will virtualize the configuration file for characters launched through IS.
Basically, rather than using the default Config.wtf file in Warcraft, it uses the virtualized file for each character, which allows lower settings on some and higher settings on others.
If you launch the game without IS, it uses the non-virtualized file.

IS/IS Boxer cannot read the game.
If I make a mapped key that will Round-Robin a keystroke between the ranged damage classes on a team.
Let's say there are five toons, one is the tank, one is the healer and three are ranged dps.
I can create, what is called (in IS Boxer) an Action Target Group, and put the three ranged dps in it.
I can then have it send a keystroke to game, with the target being the ranged dps ATG, and check a box to round-robin within the target group.
The software will send the appropriate keystroke (when I push the hot key) to Ranged DPS 1 (on press 1) to Ranged DPS 2 (on press 2) and to Ranged DPS 3 (on press 3)... afterwhich it resets to Step 1.
It has no way of knowing if the client was Crowd Controlled, locked out of that school of magic, on a Global Cooldown, or otherwise incapacitated or even dead.
The keystroke is sent, but the software cannot know whether the ability fired off or not, and if it did cannot tell if it hit or was resisted.