Code center > Suggestions

Viruses

<< < (3/3)

Botsareus:

--- Quote ---Conditions can't be passed with viruses for the simple reason that a single condition can control multiple genes. Thus an inserted viral gene could control a great number of genes after it, which is too powerful.
--- End quote ---

Then make conditions passed by viruses only control the viral dna.



--- Quote ---I appreciate the attempt at a logical post, but you still lost me.
--- End quote ---

Witch parts did you not understand?


--- Quote ---If a robot has a moded "*.thisgene .mkvirus" in each gene what is going to stop it to passing on its entire dna anyway?
--- End quote ---

^%^%%%^


--- Quote ---What If you want to pass an exsisiting gene from the robot without evolving it twice (once for the virus gene and once for the robot itself).
--- End quote ---

Lets look at this example:

'gene1
cond
start
-1 .shoot store
stop
'gene2
cond
start
-1 .shoot store
*.thisgene .mkvirus store
stop

Now without the *.thisgene restriction:


'gene1
cond
start
-1 .shoot store
stop
'gene2
cond
start
1 .mkvirus store
stop

Note that I did not have to write -1 .shoot store twice , makes it easyer to evolve.

Numsgil:

--- Quote ---Then make conditions passed by viruses only control the viral dna.
--- End quote ---

How?  I already suggested that conditions only control the gene after it and people didn't like it.


--- Quote ---
--- Quote ---I appreciate the attempt at a logical post, but you still lost me.
--- End quote ---

Witch parts did you not understand?

--- End quote ---

For your benefit:  here is what makes no sense, or seems non sequiter.

--- Quote ---More Arguments and counter arguments for using somthing better then *.thisgene .mkvirus, I even have a solution at hand.
--- End quote ---

More arguments implies there have been arguments prior.  The only arguments prior was when I considered that .mkvirus would only really accept *.thisgene as legitimate.

What I think you mean to say is that you have something better in mind than .mkvirus being so picky.


--- Quote ---What If you want to pass an exsisiting gene from the robot without evolving it twice
--- End quote ---

What do you mean evolving it twice?  Evolution as a verb is a mass verb.  One Evolution + One evolution = One Evolution.  Same with poison.  The idea of plural doesn't exist.

Maybe you mean without mutating it twice?  But then the only time in 2.37.4 that DNA mutates is during reproduction.  In 2.4, mutations will theoretically occur anytime DNA is being copied.  Is that what you were referring to?


--- Quote ---If a robot has a moded "*.thisgene .mkvirus" in each gene what is going to stop it to passing on its entire dna anyway?
--- End quote ---

Why did you add the adjective "moded" to that sentence?  "If a robot as "*.thisgene .mkvirus store"..." is a sentence I understand.  By adding that qualifier, you're changing the meaning of the sentence to something I don't understand.


--- Quote ---Solution:

If you want robots only to pass on one gene per life time then do so:

Make robots only allowed to have one instance of the .mkvirus command otherwise make too expensive (but not impossible) and make them remember what gene they passed the lest virus from , and if they try a different gene in one life time, then make it too expansive.
--- End quote ---

Poor, poor grammer.  Rewritten:

Solution:

If you want robots to only pass on one gene per generation then enforce that.

Only allow robots to have one instance of the .mkvirus command in their genome.  If they have more, make it prohibitively expensive.  Also, store what the last gene that was formed into a virus was.  If the bot attempts to form a different gene into a virus, charge the bot extra for that.

In response I'd say: "why do we care if a bot passes on it's entire genome or not?".  I certainly never voiced concern over this.  The way you worded it it was as if you were suggesting that this had been cited as a concern, and you were addressing it.  As it is, I think it's a new problem you just perceived.  If so, you should do your best to indicate that it's a new problem no one's thought of before.


--- Quote ---Lets look at this example:

'gene1
cond
start
-1 .shoot store
stop

'gene2
cond
start
-1 .shoot store
*.thisgene .mkvirus store
stop

Now without the *.thisgene restriction:


'gene1
cond
start
-1 .shoot store
stop

'gene2
cond
start
1 .mkvirus store
stop

Note that I did not have to write -1 .shoot store twice , makes it easyer to evolve.
--- End quote ---
.

Ah, but you see that is the cost of creating a virus.  That gene can't get executed for a while.  It's a tradeoff.  There are ways around it, as you just showed, but they still are somewhat difficult.

Botsareus:
I actualy forgot why I wrote "moded" there :S Ignore moded.



--- Quote ---Ah, but you see that is the cost of creating a virus.[you] That gene can't get executed for a while.[/you] It's a tradeoff. There are ways around it, as you just showed, but they still are somewhat difficult.
--- End quote ---

And what does that have to do with: making it easy for a robot to use its already mutated -1 .shoot store , instead of mutating it twice? I don't get it.

Doesn't the .mkvirus command copy everything in the gene you spesifiy as a virus. Or am I lost here?


Nice beefy patcher you got there with 2.4 , I am likeing it already...

Numsgil:

--- Quote ---And what does that have to do with: making it easy for a robot to use its already mutated -1 .shoot store , instead of mutating it twice? I don't get it.
--- End quote ---
Exactly that it isn't easy for a bot to do that.  If a bot wants to use a gene and copy that gene into a virus and distribute it, it's going to have to balance the benefit of executing that gene for itself vs. the benefit of having that gene in other bots.


--- Quote ---Nice beefy patcher you got there with 2.4 , I am likeing it already...
--- End quote ---

I'm not sure why it's so large to be honest.  The next 2.4 patch will be like the old ones, under a meg.

Navigation

[0] Message Index

[*] Previous page

Go to full version