Code center > Suggestions

" All the mutations don't develop interesting beha

<< < (3/3)

Botsareus:
FOR A PERSON READING THE CODE IT IS HARD TO SEE STUFF LIKE: 5 store , it looks like a memory location storage; a noob wont even think that it is some kind of sysvar , forget about bothering to looking it up on the sysvars file...

Therefore its important that the actualy sysvars mutate.

5 store

must be desplayed as:

.aimsx store

so its easy on the user!

I like to keep sysvar mutation seporate from number mutation. storage to memory locations is also important.


OR JUST MAKE MUTATIONS FOR 'INSERT A NEW VALUE' WITCH YOU SAYED YOU FIXED BUT NEVER RELEASED THE VIRSION OF THE PROGRAM WERE ITS FIXED.

Numsgil:
We should probably set up some kind of number to sysvar conversion for mutations.  If you have a number followed by a store, check to see if that number is a sysvar.  If so, convert it to a sysvar.

shvarz:

--- Quote ---Total chance = 1 in 4,752,000,000
--- End quote ---


Now PY, don't say that - this sounds like one of anti-evolution people talking.  Of course, the chances that a gene like that would be created from scratch are very low.  Now calculate the chances in the following scenario:

1. It does not have to be 150 - can be any number from 100 to 200 (or even from 1 to 1000).
2. There are already "store" commands in the DNA, so that mutation simply has to appear right in front of the "store" command.  It does not have to generate that command at all.

Botsareus:
ok , thats a good solution Num.


 read "AAA Here is post"  for more ideas!!!, If you dont understand somthing in there:

*The Part that you dont understand: Quote it in your own reply inside that thread, and please explain how you dont understand it.

*I still think the 'mutation rates of mutation rates' when set to 1 are currently changing the 'other rates' too slow for the fact that: its the Fastest possible rate change.

Navigation

[0] Message Index

[*] Previous page