Trailmakers-LogicBlocksGuide VS python-guide

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

1. RealPython/Python-guide - This repository offers a comprehensive guide to Python, covering a variety of topics such as installation, setup, and more advanced concepts like machine learning and web development. https://github.com/realpython/python-guide

Explore here.

I'm not saying run off and merge a major update into React; You can start much smaller than that. I started by writing small documentation fixes (1, 2, 3), and eventually added new functionality to libraries that I've used in some side projects (1).

Congratulations!! Along with another comment made here, I have this starred on my GitHub for when I do get around learning Python: https://github.com/realpython/python-guide