Tie feature request

[Elite]

First off, am I right in thinking that .tienum can be changed inside cycles like this:

cond
start
1 .tienum store
314 .setang store
.tienum inc
628 .setang store
.tienum inc
942 .setang store
.tienum inc
1256 .setang store
stop

So tie 1 gets set to 314, tie 2 gets set to 628 etc.

*********

Secondly, I have a feature request for 2.4 ...

.sendgene

.sendgene can be set to a specified gene, like .mkvirus, which is copied through the tie to which .tienum is set. The bot at the recieving end gets the selected gene inserted into it's genome like a virus

cond
*.numties 0 >
start
*.tiepres .tienum store
*.thisgene .sendgene store
stop

^ That would be a 'tie virus' that spreads as bots tie together

This would make horizontal gene transfer possible to code (me and Endy were trying to do this with viruses a while back), and would make possible all manner of interesting new kinds of virus, and other phenomena.

It's simple, useful, and limitlessly open-ended

[Numsgil]

First off, am I right in thinking that .tienum can be changed inside cycles like this:

cond
start
1 .tienum store
314 .setang store
.tienum inc
628 .setang store
.tienum inc
942 .setang store
.tienum inc
1256 .setang store
stop

So tie 1 gets set to 314, tie 2 gets set to 628 etc.

This is the plan I had for the C++ source.  The VB code doesn't support this.  At present the system's been worked out for tie communication but not for physics yet.

[Endy]

Man, it's been awhile.

Anyhow you can't currently change the tienum in midcycle like that. You could use tieang1-3 to do that although it'd be difficult to figure out which tie is which.

[EricL]

Secondly, I have a feature request for 2.4 ...

.sendgene

I'll put this on my list.  Remind me in a week or two.

I also haven't forgotten about a mechanism for addressing multiple ties in a single cycle.   A while back  I proposed something that I think was well received, but I can't find the post.  That is on my list too.

[Elite]

*Reminder*

And I have another tie-orienated request:

A .trepro sysvar, another reproduction sysvar. Storing a number in this sysvar would cause the bot to reproduce 50:50, but rather than being connected by a birth tie the two bots would be connected by a permanent tie with a tie phase equal to the number stored in .trepro

[EricL]

These are all on my list.  I won't forget but I probably won't get to them until January.  When I do, I will solicit feedback from the forum on any design or implementation issues which arise.