Author Topic: 2.4 sooo close  (Read 7274 times)

Offline Botsareus

  • Society makes it all backwards - there is a good reason for that
  • Bot God
  • *****
  • Posts: 4483
    • View Profile
2.4 sooo close
« Reply #15 on: September 27, 2005, 03:19:27 PM »
we can use a bytype opperator:  "3 4 < bytype 2 >" works like stop expression... o well...



Quote
I do think that bots not being able to remember things like "I used this number to form a tie, so I need to remember to use this number in tieloc" is soemthing of an issue. [you]Oh well, let's see if they can evolve anyway[/you].

I gess you added labels right?
« Last Edit: September 27, 2005, 03:25:10 PM by Botsareus »

Offline Endy

  • Bot Overlord
  • ****
  • Posts: 852
    • View Profile
2.4 sooo close
« Reply #16 on: September 27, 2005, 05:36:06 PM »
I think Nums is talking about the current coding complexity problem. For a simple operation like TF'ing a bot needs to have a number stored in .tieval, -1 in .tieloc and the number of the tie stored in .tienum. All of which is extremly hard for evolution to accomplish independently.

I was thinking of something similar to how the new tielens/tieangs might be useful. I was thinking that possibly storing a percent value (representing the resource type) to be transfered might be used instead of the negative numbers. The amounts transfered could be limited by bot strength, similar to what we do with shots; or increased with something similar to how shootval currently works.

Offline Numsgil

  • Administrator
  • Bot God
  • *****
  • Posts: 7742
    • View Profile
2.4 sooo close
« Reply #17 on: September 27, 2005, 05:36:19 PM »
Mutations possible:

1.  Single bp is changed into another bp.
2.  A run of bp are moved into a different location in the genome
3.  A run of bp are entirely deleted
4.  A series of random commands are inserted in at a random point
5.  A series of bp are reversed.
6.  Mutation rates are changed

That's it.  No fancy anythings going on.