Code center > Bug reports
50 .mrepro store isn't doing anything RESOLVED 2.43t
Trafalgar:
I tried manually setting .mrepro to 50 using the console, on a bot with 13k energy, and nothing happened. The next cycle, to make sure the bot wasn't unable to reproduce, I tried setting .repro to 50, and it reproduced properly.
Looking into this in the source, it looks like although mrepro does trigger reproduction, the routine which processes the reproduction reads from only .repro to get the percent-of-energy parameter. Since I'm only setting mrepro, it reads 0 from repro, which is probably why nothing appears to happen.
(I'm trying to have a bot set mrepro on another bot through a tie, so setting both mrepro and repro in one cycle isn't possible)
googlyeyesultra:
I've only used .mrepro once or twice, but I haven't had any problems with it. I think it should just mutate ten times as much, and use the value on the stack to determine how large the child should be.
How did you force commands in the console?
Trafalgar:
--- Quote from: googlyeyesultra ---I've only used .mrepro once or twice, but I haven't had any problems with it. I think it should just mutate ten times as much, and use the value on the stack to determine how large the child should be.
How did you force commands in the console?
--- End quote ---
There's a 'set' command for the console (if you type 'help', it tells you about it along with the other commands):
It says: set (.var|n) value : stores value in variable .var or location n
So I did set .mrepro 50.
(I tested it on the console only after noticing that my bots that were setting it through ties weren't actually causing reproduction in the tied bot. I have them setting repro instead now, which works, but doesn't have the 10x mutation rates which I wanted)
Welwordion:
Same problem for me .mrepro just does not activate altough I need it because I need to forbid mutations at normal reproductions for my evosim.
tested it in 2.43 as well as in 2.43s.
Numsgil:
This bug actually sounds familiar to me. I think it might have been something that I fixed when I ported to the C++ code, but it never got incorporated into the main Visual Basic program. I'm sure Eric's going to fix this promptly, but in the mean time, just do:
49 .mrepro store
1 .repro store
That'll trigger the mutation reproduction I think.
Navigation
[0] Message Index
[#] Next page
Go to full version