I don’t know what that means
edit: Okay, I see what that means and will investigate that.

But i expect that the input from the makey makey (basically a generic gamepad with the letters W A S D F and G, a space bar, a 4 way d-pad, and a right click) won’t work? Or, at least, the D-Pad won’t work. right click already works and the letters and space bar can probably work as text input

Takk for all your help (takk? is that right?!) Britzl! I really appreciate it.

At the moment I am going to investigate the possibility of adapting my hardware. I know it’s possible to hack the makey makey ( this just in case anyone has read this far without knowing what it is ) so I could probably change the D pad to assign it to some other key presses.

If that doesn’t work, I am going to try and run the game in HTML5 on Chrome on Android OS to see if key inputs are passed correctly that way.

If anyone has any idea how a native extension might be built for this task (letting defold correctly interpret key presses from a keyboard connected to an android device via USB-OTG) I would be interested in hearing about it!

If none of the above work I am going to set fire to all of my personal possessions and go and live in the woods.

the text trigger method did work and I was able to get the keypad working with the android app to some extent…

…but not to the extent that is necessary for my game. text triggers don’t have action.released, action.pressed, or action.repeated. And those are vital for me, because each “cable” in my “bomb” is a completed circuit attached to the makey makey. The computer interprets this as a key being held down. Just like in those old Bond films, you have to disconnect the cables in the correct order (=the computer must receive the action.released in the correct order) in order to avoid the explosion sound effect that signals your doom. I am going to continue experimenting, this time focusing getting a HTML bundle and playing it in the chrome browser on the android device.

Just to update this thread as well so there are no doubts: Apps built in defold now correctly interpret key presses from USB OTG devices, at least in the alpha build that Britzl has sent to me. I expect these changes will be included in the main build soon. So i’m joyfully marking this as solved.