Code center > Darwinbots Program Source Code

Order of mutation

<< < (3/6) > >>

PurpleYouko:

--- Quote ---We should keep all versions together, it'll only create confusion and counter effort when we try to combine them again. The way the code is segmented it should be easy to change A without effecting B.
--- End quote ---
I will definitely second that!
You should see the trouble that Num and I have trying to keep our source code synchronized.
Basically every time I modify a single peice of code, I email to change to him.
We absolutely have to keep the code up to date on both sides or it soon becomes completely impossible to re-integrate it.

It certainly makes it easier for each of us to concentrate on a certain area of the program and try our best not to modify any code that is common to both our projects without letting each other know immediately.

It isn't easy  :(

Botsareus:
well I dont have the right modem and the time to keep emailing you guys all my changes, when I will change it I will change it all at once and send the code to my website.

Check this out:

Make aimshot shoot more then one place like in real sells , its kinda like multi-aim-shot every time .aimshoot is called on a different angle. ex:

20
.setaim
store
-1
.aimshoot
store
120
.setaim
store
-6
.aimshoot
store

this results in a robot that shoots in two directions at once.

***
I am still not done with pusherbots so if you guys want to add multi-aim-shoot yourselfs go ahead.
***

How will multi-aim-shoot not be overpowered?

ans:

* you cant aim less then 15 degrees difference so
 if you shoot at 10 degrees you cant shoot at 11 degrees at the same time.

* if you shoot more , you waste more energy. A robot shooting 24 different shots will die almost instantly.

Botsareus:
I seen real cells use multi-aim-shot its possible , no joke.

PurpleYouko:

--- Quote ---20
.setaim
store
-1
.aimshoot
store
120
.setaim
store
-6
.aimshoot
store
--- End quote ---

Even with the hypothetical sysvar, .aimshoot, your example will not and cannot work.
Remember that each sysvar represents a single memory location in the robot.
For your example to work, it would be necessary to save multiple values into the same memory location in a single cycle.
If these commands were in the genome then only the last instance of each one would be implemented.
.setaim would contain the value 120. (20 would be overwritten and lost)
.aimshoot would contain -6. (-1 would be overwritten and lost)
Only a single instance of each of these sysvars (memlocs) would ever be processed so the robot would still only shoot once

Botsareus:
I beat I can find a way arround that;

Navigation

[0] Message Index

[#] Next page

[*] Previous page