- No agressive use of ties. That means no tieing to enemies or alge, no tie attacks, no tie defences. If you use .sharenrg and such then you need to have a condition that makes sure you're tied to one of your own.
- No memmory shots of any kind.
- No use of venom.
- No viruses.
- No sexrepro. (Although the lack of mem shots should prevent raping anyway)
- Very large field, possibly without toroidal borders and with some shapes in there (Could be cool if we had some coustom maps, maybe with designated spawn points, both for bots and the initial veggies)
- Low veggy cap.
- Medium fluid resistance.
- F1 costs, possibly a litle more expensive, like set a 1.5-2 multiplier or something like that. And maybe cut the code execution costs completely.
The only uses of ties that lead to trivial strategies are tie info attacks. All other uses of ties are either capped or time delayed, so we really don't need to limit those.
I agree with scrapping venom, info shots, and viruses.
Sexrepro doesn't matter one way or the other, so I'd go against adding an extra rule for it (just fo the sake of not having as many rules).
A very large field would be a good idea, but regarding the veggy cap. The thing that makes food too easy to find in the current league format is that veggies repop very many at a time and very often when they go below their threshold. Perhaps rather than lowering the veggy cap, we lower the number of veggies in a repop event to 1 and we increase the repop delay.
Definitely more fluid resistance. We want the maximum speed to be very hard to obtain.
We don't need to fool much with the costs, except for movement. Code execution costs are fine as they are, since any complexity we add that can't recoup the currently negligible execution costs is pointlessly burning processor time.
Okay, so:
- You can only tie with your own species.
- No memory shots of any kind.
- No use of venom.
- No viruses.
- Sexrepro allowed (like moon said, lack of mem shots should prevent problems.)
- Very large field. (what size exactly?)
- Walls (non-toroidal), since that tends to break up big orgs.
- Low veg repop threshold (let's say 30), Veg repop 1.
- Medium fluid resistance.
- F1 costs, with lower movement costs.
Question: why increase the repop delay? Just have no delay, keep the repop at 1, and keep a low veg repop threshold. That should keep the vegs constantly at a low number.
Also, I don't think we should have a custom, non-changing shapes map. That's just waiting to be exploited.
So, Moonfisher, what do you think? And what size field should we have?
Moonfisher-
Anyway, I'm sorry, you might have lost me with the NNBots...
I'm willing to say that if it does nothing to begin with and
all subsequent behaviors arise through matching a + stimulus with a random behavior and/or a - stimulus with another random behavior (cannot be pre-programmed behaviors, MUST be random) all
within the bot's lifetime (aka not epigenetic like the fruitfly), then it qualifies.
This bypasses the problems you saw, right?
Maybe we should change the name too, since we're not looking for specifically NNs anymore- GAs, HMMs, etc... Basically any pattern-recognizing bots should qualify too, right? Although I don't know why or how someone could implement a GA or HMM in a bot, but that's their choice...
So maybe the Learning League? No behavior league? Einsteinbot/Geniusbot league? (LOL)
Thanks!