Contraptify

Run a redstone design with its own test (inputs and expectations) and return which expectations hold and which fail (with what the block was instead, and when), what visibly changed (lamps, pistons, doors, dispensers) and when, dispenser shots, and notes on what broke. Without a test it just runs the machine and reports what changed. Use it on every candidate before showing it. Do not use it to display a design to the user: use show.

List a design's parts with their explanations, how many blocks each covers, and any blocks without a part. Use it before show to make sure every block is explained. Do not use it to test whether the machine works: use simulate.

List the built-in example designs (clocks, counters, a piston door, a lock, a flying machine). Use it to find a known-good starting point. Do not use it to fetch a design's blocks: use get_example.

Takes no parameters.

Return one built-in example design with its blocks, part explanations and its own test, by id from list_examples. Large designs (the 0-9 counter has about 2,500 blocks, the 00-59 clock about 5,100) are long. Do not use it to show an example to the user: use show with example set.

Show a design to the user in an interactive 3D viewer in the chat: they can press its button or flip its lever, watch it run tick by tick, move around, and click any part to read what it does. Give either design, or example (an id from list_examples). Call it once per answer, at the end, after the last simulate passes: every call adds another viewer to the chat. Do not use it to test a design: use simulate.