Parameters: Restrictions
Three prohibitions that apply to all bots: tying to another bot, reproducing alone and anchoring in place.
These three switches take away a DNA tool from all bots. They are useful for experiments (“what evolves if nobody can tie?”) and for tournament rules. All three are off by default in the app and in the F1 league, and can be turned on or off while the simulation is running.
They do not make the DNA fail: the bot keeps writing the command, and the command simply has no effect. A DNA that depends on it does not find out, unless it looks at the result (for example, .numties or .fixed).
Disable ties
Nobody can tie to another bot.
- Default
- no
- Usual range
- yes / no
- Variable
DisableTies- Key
opt:70- Live
- can be changed while the simulation runs
- Mode
- advanced only
Nobody can tie to another bot with .tie: the command is cleared without doing anything and costs nothing. Birth ties, the ones that join a parent to its child, still form as usual, but they last 100 cycles and never stiffen: without .tie there are no multicellular bots. See how a tie is created and the birth tie.
In one test, two bots that looked for each other and wrote to .tie ended up tied within a few cycles; with this option on they kept reading .numties as 0.
No asexual repro (non-repopulating)
Only repopulating vegetables clone.
- Default
- no
- Usual range
- yes / no
- Variable
DisableTypArepro- Key
opt:71- Live
- can be changed while the simulation runs
- Mode
- advanced only
Bots that are not vegetables cannot reproduce on their own: .repro and .mrepro do nothing. Vegetables keep cloning themselves, and sexual reproduction is still allowed for everyone (see sexual reproduction). With this option, an animal species only leaves children if it finds a mate.
In one test, a bot that asked for a child in its cycle 2 got one without the option and did not with it; marked as a vegetable, it got one anyway.
Nobody can fix position
Disables .fixpos for everyone. Bots already fixed stay fixed, and so do their offspring.
- Default
- no
- Usual range
- yes / no
- Variable
DisableFixing- Key
opt:72- Live
- can be changed while the simulation runs
- Mode
- advanced only
Nobody can anchor with .fixpos: the engine stops reading that address, and the bot stays loose even if it writes to it. In one test, a bot that wrote 1 to .fixpos at birth and then pushed ended up anchored without the option; with it, it moved and read .fixed as 0. See fixed bots.
What the engine stops doing is updating the state, and that goes both ways: a bot that was already anchored when the option is turned on stays anchored for as long as it remains on, whatever it does with .fixpos. Its children, which inherit the anchor, are born anchored too.