however you have changed things like the macro names for the ten numbers 0-9 which would require the same number of changes in an existing EG configuration using this plugin,
I know what you mean. But IMHO the current implementation of this plugin is wrong. You doesn't see in the EG plugin what you can see in MP MessagePlugin extension configuration.
For "old" user my update requires some changes in their existing configuration (maybe better name it 2.0 instead of 1.1, which allows BC break). But for new user this is much easier. They can see the same thing on both side if they start to configure.
Just remembering myself. What triggers Power1,Power2,PowerTV from EG in MP... and after some time I found out:
- Power1 does not exists in MP
- Power2 is "Power PC"
- PowerTV is "Power TV"
Well, and the numers 0-9 are just having a logical problem. E.g. number 0 doesn't trigger a numpad0 in MP, instead it triggers a num0 (same char message, but different keyup-/keydown message)
I've also modified this file and added some macros to my personal MP EG plugin and the Message Plugin for MP
An idea for the next update of the EG plugin:
The plugin is reading the MessagePlugin configuration and does not define own actions. Thus, if you rename/add an action in MP, you have the same in EG. With such an update, you have initially the same names in EG like you can see them in my version.