When it comes to actual VB syntax, it's just been too long. I haven't really done any VB coding since October. This is a good resource, if you're a good searcher you should find an article on just about anything you could ask a question about. It'll be far more helpful than I ever could.
great. thanks.
will see what I can finger out ...
then when it comes to utilizing it within DB, will pick your/PY's brains. ;)
I'll put what I learn [if anything] ;) in some form on the wiki ...
as an aid to others who might wish to get into the VB and DB codes.
Your last post, about Invested energy. That was not my original intention. I was hoping to have the bot itself and its descenddants equally weighted. In the end I don't know that it matters.
I don't think it does, other than when it comes to scaling or assigning the weights
to other factors one may wish to consider so they are of the same magnitude.
so ... just trying to get a sense of what range of numbers might be returned.
obviously, if a bot has many decendants which are thriving ... it's score is going
to be high and it is a good candidate and one which we want to capture.
Feel free to take whatever I had and run with it. It's not like it's a critical part of the program, it allows a great deal of consequence free experimentation.
exactly. and making it as 'open' as possible for the user ...
is a good thing, ime.
one may wish to have the bot that is saved as 'fittest' to be one
that has not only survived and prospered, but one that has some
useful mutations. iow, it doesn't do a lot of good to auto-save the
fittest bot if it is going to turn out to have the exact same DNA with
no mutations as the 20 it has saved before, so giving the number of
mutations some weight in the selection process might be of some use.
and who knows what else the user might desire to look for?
greatest slime producers, most kills, etc. whatever.
so, finding a way to make it more versatile for the user is, imo
a good thing.
the more user friendly, the better.
within reason.
when possible. ;)