Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Resets are the most common. These will generate a series of instructions such that the arm will return to its original position. The best way to describe how it does this is pretty easy:
[If it is grabbing an atom, drop it]
[If it is a piston and it has a different length to its original position, extend/retract to that length]
[If its rotational position is different from its original position, rotate back to that]
[If it is on a track and not in its original position, slide until it is]
Repeats are a bit more tricky, but pretty easy to understand. It'll copy and paste every instruction before it. The start point is dictated by the first non-repeat instruction after a repeat (if it exists), and the end point by the last non-repeat instruction before it. Most of the time, it means the start of the instruction tape and every instruction before any repeats.
Just think of this as a shortcut instruction. If you need a particular part of the machine to do the exact same process twice in one machine period, then feel free to use it. Just think of it as 'If I programmed this manually, everything I write will be the exact same as something I've already put down'.
The first time that an arm performs a particular instruction, whatever instructions the other arms were executing at that point, they'll be executing exactly the same instructions when that instruction is repeated on subsequent cycles.
Note that this doesn't guarantee that cycles are identical; if an arm ends its cycle in a different position to that at the start of a cycle, then the following cycle will have different results even though the same instructions are executed. But it makes it much easier to construct solutions which loop.
What also was happening was when one of the arms was grabbing stuff too early, I just shifted the instructions one step forward and nothing changed at all, the exact same thing kept happening. It must have something to do with the padding but like I said... I don't get it.
while also achieving the lowest Cycles score.
I wonder if there is a challenge that actually requires it, or if they are what I think they are - just shortcuts.