Guides

Anymaker Logic Without the First-Vehicle Spiral

Cables carry signals. Microcontrollers make decisions. Debug before you write a novel.

Last updated:

Anymaker Microcontrollers

Anymaker lists microcontroller programming with a drag-and-drop editor or text editing. Developers have said logic should be easier than Stormworks, with debug, step, and inspect so you can watch values instead of guessing. The failure mode is simple: people open the logic tool on a chassis with no fuel path, then decide the game is cruel. Cables are not microcontrollers. Keep this page closed until a seat, wheels, and a starter circuit exist.

The embedded electrical-circuit video is a pre-launch look at the boring layer those controllers sit on. It is not a cookbook of unofficial chips. Early Access on 18 September 2026 is still upcoming. Treat every graph you see in alpha or the June demo as a method, not as a part number this wiki will invent.

Logic versus cables versus fluids

The cable tool runs electrical paths: power, ignition, lamps, fans, radio, a switch that means on. The fluid tool runs liquids: fuel, cooling, and whatever marine jobs boats and helicopters add at launch. The logic tool is for decisions: if this value, then that output. If you only need “key on means pump on,” try a cable and a switch first. Engines and wiring is that first page on purpose.

A microcontroller earns its slot when the decision has more than one input or a sequence. Honest examples without invented APIs: a light that stays off until a pressure value exists; a starter that drops out after a value says running; a gate on a base that waits for a button. Autoland and a custom ECU do not belong on vehicle one.

Property, inspect, and debug are how you prove a decision happened. If a value never changes when you toggle the real-world switch, the bug is usually the cable, the component, or the binding — see controls — not your future text script.

Drag-and-drop, text, debug, step, inspect

Drag-and-drop is the friendly graph: nodes, links, something you can show a co-op partner on voice chat. Text is there for people who want to type. You do not need both on the first gate. Pick one, make a tiny program, then use debug and step. Step is the gift. It is how logic becomes easier than a black box you only restart.

Inspect values the way you inspect a hinge. Name what you think a number should do, then watch it. If the number is dead, do not add three more nodes. If the number twitches and the motor does not, you left the microcontroller and returned to belts. Career nights do not pause because you opened a graph.

Sandbox at launch is the classroom: all parts, infinite supply, noclip, daylight, no enemies. Build a plank, a lamp, and a controller you can step without a wolf, then put the same graph on a truck that already starts.

Keep the first vehicles simple

A first buggy wants throttle, brakes, lights, maybe a horn you will regret. Those can often stay on cables. A first truck might want a fan that tracks temperature if the weather system is already cooking the bay. That is a small graph. A first career raider van does not want a custom ammo counter overlay you designed instead of looting food. Inventory is limited; attention is too.

Duplicate a working controller the way you duplicate a wheel bay. One understood starter program is worth more than four mystery boxes. When Steam Workshop arrives at Early Access, take downloaded graphs apart and inspect values. The build checklist should list “logic last.” The parts tier list should not rank fictional chips.

Co-op, radio, and who is allowed to edit the graph

Online co-op includes building. That includes logic if you let it. Agree who owns the microcontroller the way you agree who owns the only running truck. Voice chat and radio can walk a partner through a step session. They can also talk over a military patrol. Co-op is the manners page. Survival still applies while the hood is open: someone watches the road.

Do not debug a gate during a lightning storm on a steel roof. Weather is a listed system. Park, close the door you actually hinged, then step the program. If you need noclip to reach a controller you buried, the placement is wrong. In-world building means you are the technician. Leave an access panel.

What logic will not replace

A microcontroller will not float a hull. Buoyancy is a launch simulation, not a graph. A microcontroller will not replace the career bunker spike. Finishing that location in the demo opened higher-tier loot more widely; it did not require a custom script. A microcontroller will not feed you. Hunger is a loot problem.

Geometa still plans about a year of Early Access with more tools and parts. Track that on the roadmap instead of assuming every Stormworks habit has a clone. Anymaker is not Stormworks 2. The editor lives in the world, and the first win is still a vehicle that starts.

When the tiny graph works, stop. Drive. Eat. Come back later with a second decision. Everything flashy in a trailer belongs on Preview until you can inspect it after 18 September 2026.

FAQ

Frequently Asked Questions

Quick answers about Anymaker building, survival, and Early Access.

Do I need a microcontroller to start my first Anymaker engine?

Usually no. Get fuel, cooling, belts, and cables working first on engines and wiring. Add logic when a switch is not enough.

Is Anymaker logic the same as Stormworks?

No. Geometa wants it easier, with drag-and-drop or text plus debug, step, and inspect. Building is also in-world, not a separate CAD editor. Keep first graphs tiny.

What is the difference between the cable tool and the logic tool?

Cables carry electrical signals and power. Logic decides. If a value never moves, inspect the cable and the component with the property tool before you write more nodes. Controls lists both tools.

Should I learn microcontrollers in sandbox?

Yes. Launch sandbox is daylight, infinite parts, no enemies, and noclip for access. Put a working graph on a plank, then on a truck. Career can wait.

Can Workshop creations teach me logic?

They can, if you take them apart and step values. Do not drop a downloaded helicopter into career and assume the graph is safe. Use the build checklist and inspect everything.