In ChipWits, Cycles represent the amount of time or processing power it takes for your ChipWit to execute a command. Each chip (or command) in your program consumes a specific number of cycles when executed.
Specifications #
- Cost of Actions: Every chip has a cycle cost. For example, skating forward might take 1 cycle, while more complex operations like sensing the environment or using memory might take more.
- Cycle Limit: Each mission or task often has a maximum cycle limit. Your ChipWit must complete its task within this limit, so using fewer cycles makes your program more efficient.
- Efficiency: The fewer cycles your program uses, the faster your ChipWit will complete its actions. Designing efficient programs is key to success in harder missions.
Example of Use #
If a Skate Forward chip costs 1 cycle and a Turn Left chip costs 2 cycles, executing both in a sequence will take 3 Cycles in total.
That amount (3) is then subtracted from the total Cycles that your ChipWit has to complete the Mission’s objective.
When your ChipWit’s Cycles run out (“Cycles Left” in the top right corner of the screen reads 0) your ChipWit will cease to function and gameplay will end.
Why Cycles Matter #
Managing cycles is crucial for optimizing your ChipWit’s performance. Programs that use too many cycles may run out of time before completing their task, so you need to balance complexity with efficiency.
Cycles vs. Energy #
Cycles and Energy are two very different things.
Cycles are the total number of actions/moves your ChipWit can make though the entire Mission, while Energy is like a battery that is depleted over time by operating your ChipWit, but can be replenished by consuming Good things.
You cannot regain Cycles once they are used, though you can press the Restart button to start the mission over.
