- First Logic Gate project
- Workshop rooms and protected pedestrian doors
- Testing two inputs before building an airlock

Basic Logic Door - Open from Either Side
A small bearing door controlled from both sides, used to learn input states, one mechanical output, and an obvious reset.
- The door must resist direct raid impact
- A vehicle needs to pass through
- The moving panel cannot clear players on both sides
Workshop baseline
Use these dimensions and targets for the first working version. They are a practical starting layout, not a fixed in-game preset; adjust them only after the baseline passes its tests.
Plan the craftable parts →- 01Opening
- 3 × 5 blocks
- 02Door motion
- 1 Bearing / 90° swing
- 03Inputs
- 2 Buttons
- 04Logic
- 1 OR Logic Gate
- 05Motion control
- 1 Controller
- 06Reset
- Return to closed
Part manifest
The quantities below describe one baseline build. Optional parts are marked so you can prove the working system before spending on lighting, storage, or automation.
Direct crafting cost
This total multiplies each listed part by its preferred Craftbot or Mechanic Station recipe. Processed materials and block recipes are shown as direct inputs instead of being expanded into every earlier production step.
- Craftable part types
- 6/6
- Station time
- 50s
- Input types
- 5






Construction sequence
Do not place the next system until the checkpoint under the current stage is true. That keeps steering, motion, power, and storage failures separate.
Build the hinge first
Prove the door leaf can move without logic.
- Mount one Bearing on the protected side of the opening.
- Build a light 3 × 5 leaf.
- Use a temporary Switch to test the full swing.
Set open and closed angles
Give the Controller two predictable positions.
- Connect the Controller to the Bearing.
- Set a closed position against a physical stop.
- Set an open position near 90° without over-rotation.
Combine two inputs
Let either Button request the same door action.
- Place one Button on each side outside the sweep.
- Set the Logic Gate to OR.
- Connect both Buttons to the gate, then the gate to the Controller.
Test all four input states
Confirm the behavior is defined rather than accidental.
- Test neither input.
- Test the outside Button only.
- Test the inside Button only.
- Test both Buttons together.
Workshop tools
Each tool below has a specific job in this build. Finish that job, then move to the next stage instead of wiring and tuning everything at once.
Connection map
Read each row from input to output. Name or color the physical controls to match this map before closing the bodywork.
Test bench
Run these checks with the normal load fitted. If one fails, make the listed physical change and repeat that same test before changing another variable.
Every Button combination matches the plan
Trace inputs before changing the Controller
Door stops against a safe physical limit
Reduce angle and move the Button out of the sweep
Door state is understandable after returning to the world
Add a visible maintenance reset
Scenario variants
Change the proven baseline for the route or job you actually have. Every upgrade adds a tradeoff, so repeat the test bench afterward.
Use direct Button behavior without toggle memory
Simple and safe, requires holding or repeated use
Replace one Button with a Sensor
Hands-free, vulnerable to unwanted triggers
Replace Bearing with a Piston
Smaller sweep, needs straight travel clearance









