Code center > Suggestions

More realistic mutations

<< < (2/9) > >>

PurpleYouko:
It can be fixed but it involves a lot of very specific conditions.
In order to stop the program from returning stupid numbers in things that can only use numbers in specific ranges, you first have to identify what memory location stuff is being put into and then apply limits to the input value.

Lots and LOTs and [span style=\'font-size:14pt;line-height:100%\']LOTS[/span] of code.

 :unsure:  PY  :unsure:

Endy:
Oh well. :unsure:

Maybe we can just think of it as junk dna, which could eventually develope into something more useable.

Endy ;)

PurpleYouko:
One thing we could easily change is to reduce the random number that will be put into the DNA on mutation.
I can't really think of any DNA command that can take a number higher than 1256. (correct me if you can think of one) So why are numbers as high as 32000 being put there?

This random number can be limited to a range of -1256 to +1256 which will give more chance of usable mutations.

 :D  PY  :D

Botsareus:
HOW ABOUT OUR HIP RANDOM NUMBER IS EQUAL TO: = Choose(Int(Rnd * 3) + 1, Int(Rnd * 10), Int(Rnd * 255), Int(Rnd * 20000)) * IIf(Int(Rnd * 2) = 0, -1, 1)

'One/Three low values
'One/Three mid values
'One/Three huge values
'One/Two Negative or Posetive

'Good Game Huge numbers problem

Numsgil:
Boyancy goes up to +/-2000.  (setboy)

I definately think it should be an option in the mutations panel.  Some masochists might decide that 32000 is a great number for mutations!


Bots, can you break down your statement into several smaller ones?  No need to optimize it yet  :rolleyes:

Navigation

[0] Message Index

[#] Next page

[*] Previous page