I recently wanted to event something with a lot of different triggers on different bricks. Specifically a piano. It is kinda hard to use the mouse to click the different tangents, so I wondered if it was possible to remake it somehow. I came up with this idea:
On a trigger, let's say "onActivate", the player freezes and the key configuration locks. A message appears on the screen saying: "You are now in keyboard mode. Press Q (reconfigurable through RTB or something) to snap out of keyboard mode."
Then, you could use an event called "onKeyPressed -> [(scrolldown menu with all available keys except the one needed to snap out of keyboard mode (Q))]" to remap all keys on your keyboard to do certain things through events. Let me give you an example of how this would work, in this case with the piano:
0. onActivate -> self -> StartKeyboardMode [1
1. onKeyPressed -> ["A"] -> self -> playsound [C4]
2. onKeyPressed -> ["S"] -> self -> playsound [CS4]
3. onKeyPressed -> ["D"] -> self -> playsound [D4]
4. onKeyPressed -> ["F"] -> self -> playsound [DS4]
5. onKeyPressed -> ["G"] -> self -> playsound [E4]
6. onKeyPressed -> ["H"] -> self -> playsound [F4]
etc.
While KeyboardMode is activated, the keys cause some event to happen, instead of what they would normally do (ie. ASD wouldn't cause the player to move). This might require some new, static playertype.
Why would BL need such events? Like shown above, this could be used to create event based instruments. It would also become handy for making event based arcade games or advanced password-protected builds.
I don't know if this is possible, but I think it can be done somehow with new playertypes. Do you think this is a good idea? Did you even understand what I asked for? :P
