Trailmakers-LogicBlocksGuide VS GlovePIE

you can check out my logic guide, it's the most up to date and in depth guide there is

it's explained in my logic blocks guide

For how logic blocks work, i recommend reading my logic blocks guide as it's the most in depth, updated and accurate guide there is

Not exactly. You also need to add a seat to the detached object and make sure it's the last edited side of the detached block. As for how logic gates work you don't need to understand them, just put the keybinds on OR gates connected to the blocks those keybinds control. If you want to understand how logic works however, you can check out my guide which is the most accurate, in depth and up to date that exists

A sequential latch is not what OP used, but i have a guide which explains how to create one. It's more complex than what OP used, but it's useful in more situations and allows you to make a single input button have n possible values rather than just 2

A NOT gate inverts the state of the input, meaning that it will give an output if it has no input and it won't give an output if it has an input. For more information you can check out my logic blocks guide

flip-flops are useless in this game because toggle is a built-in function on logic gates and works better than a flip flop circuit. Also, this is a better guide about logic blocks as it's the most up to date and in depth guide that exists

you can check out my guide about logic blocks for how they work, but basically they allow you to automate things on your creation and add new functionality

for how logic gates work, you can check out my guide. For how to keep a thruster on after being detached, the easiest way is with a toggled OR gate with the detach keybind connected to the thruster

I tried to use that program years ago, wasn't really satisfied. I believe there's a program that will let you use the keyboard as a... keyboard, I guess. https://github.com/Ravbug/GlovePIE

In theory you could use GlovePIE to map one of the keyboards to buttons in a virtual joystick.

I use GlovePIE to get around most of those. It's annoying that I have to set that up in the first place, but it works well.

The more boring way is install GlovePIE (see https://github.com/Ravbug/GlovePIE for an preservation archive site as the original site has fallen into disrepair) & use an IR sensor bar (like the original Wii sensor bar, which is just a set of 2 IR transmitters that the Wii used as a fixed reference point) to use it as an HID, like a mouse.

https://github.com/Ravbug/GlovePIE i use a software called glovepie to interpret MIDI inputs as keyboard presses. with this software you can use any MIDI device to emulate keyboards, mice, controllers, or whatever you want. here is my script that i created to use my piano as input for Lunatic Rave 2 and similar rhythm games as an example. There is also a built in GUI based key mapper which is helpful to set up MIDI devices (just press a button on the device and then the button you want to emulate).

Nice. The language looks really nice! I started out with GlovePIE (site went down about 1-2 years ago) (image). It was more a hotkey scripting/assigning language, allowing multiple types of syntax (bash or c like). I used it to map my Wii Remote to the keyboard and initially played some games using the classic controller mapped to mouse and keyboard.

You could try using Freepie or Glovepie this is how I bind my wii controllers to PC games.

Check out GlovePie.

You can use GlovePie on windows to have it output MIDI. I have been using it for years now. If you want the script I run for it feel free to DM me.

Just cleaning it to connect it to my PC using Glovepie: https://github.com/Ravbug/GlovePIE/releases/