.tieloc
What to do through the chosen tie: a number from 1 to 1000 writes .tieval to that cell of the other bot; -1, -3, -4 and -6 pass or take energy, venom, waste or body.
Facts
- Address
- 452
- Name
.tieloc- Kind
- Command: the bot writes it and the engine reads it and usually consumes it
- Group
- Ties
- Written by
- Your DNA.
- Read by
- The engine. With 1 to 1000, in the forces and collisions phase it writes
.tievalto that cell of the tied bot (requires.tienumto be other than 0). With-1,-3,-4or-6, it transfers in the movement phase. - Cleared
- The engine, together with
.tieval, when it carries out the command. A write with no tie on that port stays written; so does a transfer, if you have no ties or no tie is chosen. - Range
- −32000 to 32000; 1 to 1000 and
-1,-3,-4and-6work - Mutations
- picked as a store target
It is always used together with .tieval and acts on the tie you picked with .tienum. It has two modes:
Positive (1 to 1000): write to the other bot. The engine puts .tieval in that cell of the tied bot's memory. It can be free memory, to pass it data, or one of its own commands, such as .up or .shoot. It happens in the same cycle, after everyone's DNA has run, so the other bot reads it on its next turn. In this mode .tienum has to be other than 0: .tiepres isn't enough.
Negative: transfer. With a positive .tieval you give; with a negative one you take. Here the .tiepres tie does count when .tienum is 0:
.tieloc | What happens | Cap per cycle |
|---|---|---|
-1 | Energy. The receiver keeps 70% as energy, almost 3% as body and 1% as waste | give 1000, take 3000 |
-3 | Venom. When giving, it paralyzes the other bot with your .vloc and .venval (whether or not it is of your species); when taking, you keep its venom | 100 |
-4 | Waste (.waste) | 1000 |
-6 | Body. The receiver keeps almost all of it as body | give 100, take 300 |
Taking energy or body from a bot of another species that has enough poison (.poison) poisons you instead of feeding you.
When the order is carried out, the engine clears .tieloc and .tieval. But they are not always cleared: a write (positive) that doesn't find a tie with that tie port stays written, and so does a transfer if you have no ties or if .tienum and .tiepres are 0. Careful, because that old order runs later, as soon as a tie picks it up.
' feed on the bot tied through tie 7
start
7 .tienum store
-1 .tieloc store
-100 .tieval store
stopWith this, the other bot loses 100 energy and you gain 70, plus a little body.