New in 1.0 · Experimental builds
Start with a mechanism you can explain in one sentence: press a switch, open a door. Build that small circuit, test it in the editor, and add another condition only when the first action behaves as expected.
A safe first-project workflow
- Pick one visible outcome. For example: make one interactive element control one other element. Keep the first test in a corner of your base where it cannot disrupt your normal crafting area.
- Craft the required Sparkworks tools and props. The system is accessed through a new set of tools and interactive props; use the in-game recipe and placement descriptions for exact requirements.
- Inspect the graph before wiring more parts. Identify what acts as an input, what should respond as an output, and where the rule or connection is shown. Give each test element an obvious label or nearby sign.
- Test one connection at a time. Trigger the input, observe the output, and change only one connection or rule if it fails.
- Expand into a small puzzle or trap only after the simple interaction works. Keep a manual way through or a reset route while testing, especially if friends will visit.
Troubleshooting checklist
- Confirm each interactive prop is placed and can be interacted with in the intended way.
- Follow the graph visually from input to output; look for an unconnected endpoint or a rule that never becomes true.
- Test with the simplest possible setup before adding timers, multiple branches, or enemy encounters.
- Keep a backup copy of the adventure or build before a major wiring change.
- When publishing a shared adventure, explain controls and reset behavior so visitors know what to do.
Scope note: The official announcement confirms the graph editor and broad uses, but exact component behavior should be documented from in-game testing. We are deliberately not inventing a pinout or wiring recipe here.
Once a build is stable, Adventure Sharing can help players discover and visit community creations. The 1.0 changelog adds more tags, highlighted adventures, and expanded browsing controls. A polished Sparkworks guide should eventually include tested diagrams, a short demonstration clip, and a troubleshooting section for each specific build.
Sources: Official Sparkworks and Adventure Sharing changelog · Official logic system introduction