Here’s a typical Engine setup in a definition:

• Double clicking on the go toggle will make the engine work continuously, growing the assemblage at nI (100 in this case) parts placed at each iteration until it overshoots the total Objects number tN or it cannot grow anymore (due to environmental or rule-based constraints).

  <aside> 💡 In all example files where a “go” toggle is present, the same toggle is also wired to an auto-stop component (courtesy of froGH) that will set automatically the toggle back to false once the stop condition is reached.

  </aside>

• Double clicking on the step button will execute only one iteration, growing the assemblage of the number of parts (100 in this case) given as input in nI.

• rS (reset Settings) will reset environmental and Heuristics conditions without removing the already assembled parts

• R (Reset) will revert to the initial setup of the system, losing every progress eventually made in the current simulation

Just give those toggles and buttons a try for yourself in one of the example files. It’s easier to understand watching them in action!