Code center > Bug reports
Large fields bugs
Numsgil:
I think it was something along the lines of "bots have a hard time as it is hitting the broad side of a barn (metaphorically speaking with finding the right values for certain actions)."
Specifically things like shots requiring a value of -1, and it being even more difficult for bots to find the right value if they have billions of numbers to pick from.
Not sure I have those same concerns anymore now that I think about it.
What I would do, my first impulse, would be to restructure the sysvars, cut off half the robots' memory locations ie: 1..500 and make those locations longs.
PurpleYouko:
So you are worried that memory locations would have values that are too large?
Well the present program has a bunch of limits on it to fix them all to a max of 32000 anyway. I don't propose to change that really, particularly on the ones where commands are being accessed and controlled.
Actually, most of those have even smaller limits already applied to them. For instance, I don't think it is possible to evolve a line of DNA code that would put a value of greater than 32000 into anything. Those limits already exist so making the memory locations into longs wouldn't change anything.
Numsgil:
So just have the 32000 limit still in place but use longs as the underlying data type?
Seems sorta a waste. I mean, 32000 isn't a magic number. I had reservations at first, but I think pumping up the allowed values into longs would be really cool. What would a veggy with a million body points even look like :P
PurpleYouko:
We would save a heck of a lot of code if we could take out all the lines that ask whether a value is greater than 32000 and then apply a limit to it.
Might speed the program up a bit.
I should imagine that a 1,000,000 body veggie would mostly fill the screen. :lol:
PurpleYouko:
It might be more realistic to bump the limits up to 100,000 or something rather than to allow absolute free reign.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version