Massed Hunter with poison and shell and slime (F2) (rayz) (02-04-2008)

[rayz]

This is my first entry- the "Massed Hunter with poison and shell and slime".  Not a very original name, but all I could come up with. This is still a work in progress as I test it against other bots and tweak it.  Fires ties to anchor itself to food and then fires away at it.  It is meant for a food-intensive environment, as it just plows through all food.  Anyway, the code is below.

[you]MOST RECENT VERSION:[/you]

Code: [Select]

cond
*.nrg 750 >
*.body 1000 <
start
100 .strbody store
stop

cond
*.nrg 500 <
*.body 1 >
start
100 .fdbody store
stop

cond
*.shell 100 <
*.nrg 750 >
start
100 .mkshell store
stop

cond
*.slime 100 <
*.nrg 750 >
start
100 .mkslime store
stop

cond
*.poison 100 <
*.nrg 750 >
start
100 .strpoison store
7 .ploc store
stop

cond
start
420 .eye1dir store
315 .eye2dir store
210 .eye3dir store
105 .eye4dir store
-105 .eye6dir store
-210 .eye7dir store
-315 .eye8dir store
-420 .eye9dir store
stop

cond
start
105 .eye1width store
105 .eye2width store
105 .eye3width store
105 .eye4width store
105 .eye5width store
105 .eye6width store
105 .eye7width store
105 .eye8width store
105 .eye9width store
stop

cond
start
-4 .focuseye store
stop

cond
*.eye1 0 >
*.refaimsx *.myaimsx !=
start
560 .aimsx store
0 .aimdx store
stop

cond
start
4 .focuseye store
stop

cond
*.eye9 0 >
*.refaimsx *.myaimsx !=
start
560 .aimdx store
0 .aimsx store
stop

cond
start
-3 .focuseye store
stop

cond
*.eye2 0 >
*.refaimsx *.myaimsx !=
start
420 .aimsx store
0 .aimdx store
stop

cond
start
3 .focuseye store
stop

cond
*.eye8 0 >
*.refaimsx *.myaimsx !=
start
420 .aimdx store
0 .aimsx store
stop

cond
start
-2 .focuseye store
stop
cond
*.eye3 0 >
*.refaimsx *.myaimsx !=
start
280 .aimsx store
0 .aimdx store
stop

cond
start
2 .focuseye store
stop

cond
*.eye7 0 >
*.refaimsx *.myaimsx !=
start
280 .aimdx store
0 .aimsx store
stop

cond
start
-1 .focuseye store
stop

cond
*.eye4 0 >
*.refaimsx *.myaimsx !=
start
140 .aimsx store
0 .aimdx store
stop

cond
start
1 .focuseye store
stop

cond
*.eye6 0 >
*.refaimsx *.myaimsx !=
start
140 .aimdx store
0 .aimsx store
stop

cond
start
0 .focuseye store
stop

cond
*.eye5 0 >
*.refaimsx *.myaimsx !=
*.numties 0 =
start
0 .aimsx store
0 .aimdx store
*.maxvel .up store
1 .tie store
0 .stifftie store
stop

cond
*.eye5 25 >
*.refaimsx *.myaimsx !=
*.refnrg 0 >
*.numties 0 =
start
-1 .shoot store
4 .shootval store
*.maxvel .up store
stop

cond
*.eye5 25 >
*.refaimsx *.myaimsx !=
*.refnrg 200 <
*.refbody 1 >
*.numties 0 =
start
-6 .shoot store
4 .shootval store
10 .up store
stop

cond
*.eye5 0 >
*.refaimsx *.myaimsx !=
*.numties 0 !=
start
0 .aimsx store
0 .aimdx store
10 .up store
1 .tie store
0 .stifftie store
stop

cond
*.eye5 25 >
*.refaimsx *.myaimsx !=
*.refnrg 0 >
*.numties 0 !=
start
-1 .shoot store
4 .shootval store
10 .up store
stop

cond
*.eye5 25 >
*.refaimsx *.myaimsx !=
*.refnrg 200 <
*.refbody 1 >
*.numties 0 !=
start
-6 .shoot store
4 .shootval store
10 .up store
stop

cond
*.eye5 0 >
*.refaimsx *.myaimsx =
start
1 .tie store
630 .aimsx store
0 .aimdx store
0 .stifftie store
stop

cond
*.eye1 0 =
*.eye2 0 =
*.eye3 0 =
*.eye4 0 =
*.eye5 0 =
*.eye6 0 =
*.eye7 0 =
*.eye8 0 =
*.eye9 0 =
*.numties 0 =
start
5 .up store
stop

cond
*.nrg 100 <
*.eye5 50 >
*.refaimsx *.myaimsx =
start
1 .shootval store
-2 .shoot store
stop

cond
*.waste 100 >
*.refaimsx *.myaimsx !=
start
-4 .shoot store
*.waste .shootval store
stop

cond
*.fixpos 0 !=
start
0 .fixpos store
stop

cond
*.nrg 1000 >
start
50 .repro store
stop
end
Oh, this may also be considered mult-bot, as it fires ties which usually become permanent and allow the movement of a group instead of only the individual.

[Moonfisher]

As far as I understan your actions are executed at the end of the code, so 1 .focuseye will not change your eye before you're all the way through the code. Same goes for all the refvars, they won't get updated from your changes till the next cycle. Basicaly saying your eye genes look like they won't work the way you intended...
Haven't had a chance to run it yet, will do so in the evening if I have time.

[Moonfisher]

Took another look during lunch break... I don't know of any sysvars named refaimsx or myaimsx, there is a link to a page with all the sysvars on the main Wiki page.
Also what you're trying to do with the eyes, you'll always have eye5 in focus with that code, you should take a look at Excalibur. It's eye genes are realy simple but also very good.
You can always expand their functionality gradualy to get a feel for it, Excalibur makes a spin when looking at it's own, instead you could either keep tooking at nearest enemy in one direction (Maybe have eye9 in focus if you're not fighting and only turn left towards nearest eye that isn't empty). Or you can let your bots send enemy coordinates through out values, this way if you're looking at a friendly theres a chance he'll point you towards nearest enemy... (Locust does something similar, although it doesn't use excaliburs eyes, but the behavior is similar and it would provide an example of the use of in/out values.)
Generaly Excalibur is a great example for a lot of things, realy clever setup, realy simple, flexible, nice tweek values. There is some redundant code though... I'm thinking maybe I should post a cleaned up version of Excalibur (Had to make on when I tryed to SS'ify it). Most noticable is that excalibur has a -1 shot gene, but it's never used. (The eyes should be clean though).

Hmmm I'm going to try that idea with the eyes myself, try to put 'em in the next LoveBot, both the in/out thing an the idea for the eyes, so instead of spinning a fixed angle per cycle I'd turn to the next visible thing in the eyes, maybe even mess with the eyedirs to cover an even broader angle. Could possible be able to cover 360 degrees in 3-4 cycles if nothing is spotted, and take the largest step possible whithout running a chance of missing something... I like the whole spin thing, been using it in all my new bots since I SS'ified Excalibur, I'm hoping this idea will make the spin even more effective.
Bit expensive to mess with the eyes all the time though, probably going to go for small gaps in between the eyes to be able to use the same setup all the time, and not just when looking for food.
Then maybe once totalmyspecies is getting high it could switch to eyes that look more like the ones on Gazer or Pacifist.... just with a narrow eye5.
Only problem is, I'm not sure if this will actualy be an advantage for a rape bot, all these ideas would probably be better on Locust or something... but I want to work on the Rape bot

[rayz]

Took another look during lunch break... I don't know of any sysvars named refaimsx or myaimsx, there is a link to a page with all the sysvars on the main Wiki page.
Also what you're trying to do with the eyes, you'll always have eye5 in focus with that code, you should take a look at Excalibur. It's eye genes are realy simple but also very good.
You can always expand their functionality gradualy to get a feel for it, Excalibur makes a spin when looking at it's own, instead you could either keep tooking at nearest enemy in one direction (Maybe have eye9 in focus if you're not fighting and only turn left towards nearest eye that isn't empty). Or you can let your bots send enemy coordinates through out values, this way if you're looking at a friendly theres a chance he'll point you towards nearest enemy... (Locust does something similar, although it doesn't use excaliburs eyes, but the behavior is similar and it would provide an example of the use of in/out values.)
Generaly Excalibur is a great example for a lot of things, realy clever setup, realy simple, flexible, nice tweek values. There is some redundant code though... I'm thinking maybe I should post a cleaned up version of Excalibur (Had to make on when I tryed to SS'ify it). Most noticable is that excalibur has a -1 shot gene, but it's never used. (The eyes should be clean though).

Hmmm I'm going to try that idea with the eyes myself, try to put 'em in the next LoveBot, both the in/out thing an the idea for the eyes, so instead of spinning a fixed angle per cycle I'd turn to the next visible thing in the eyes, maybe even mess with the eyedirs to cover an even broader angle. Could possible be able to cover 360 degrees in 3-4 cycles if nothing is spotted, and take the largest step possible whithout running a chance of missing something... I like the whole spin thing, been using it in all my new bots since I SS'ified Excalibur, I'm hoping this idea will make the spin even more effective.
Bit expensive to mess with the eyes all the time though, probably going to go for small gaps in between the eyes to be able to use the same setup all the time, and not just when looking for food.
Then maybe once totalmyspecies is getting high it could switch to eyes that look more like the ones on Gazer or Pacifist.... just with a narrow eye5.
Only problem is, I'm not sure if this will actualy be an advantage for a rape bot, all these ideas would probably be better on Locust or something... but I want to work on the Rape bot

I pulled refaimsx and myaimsx from the Darwinbots sysvars page, under "refvars" and "myvars".

Thanks for the eyes hint, I will check Excalibur soon.

P.S. "Rape bot" ?

[abyaly]

Actually, I think excalibur doesn't work too well in current versions. Best not to use it as an example.

[Numsgil]

That's odd, because in a sample league run I did with the current F1 bots, Excalibur won.  Maybe all old bots are crappy in present versions?

[Moonfisher]

I think Excalibur works well enough, it's holding up better than the other old bots, and it's nice and simple. If you expand the eyes to work beter while spinning I think it would form a good base for scanning for food. I'm planning on trying some sort of effective spin involving the stuff I mentioned anyays.
Otherwise there's plenty of other good bots to look at, a lot of the newer league bots in the starting gate have some cool eyes on them.
The point with looking at excalibur is how very simple genes can accomplish a lot, and the long eye range can help a bot start off a lot faster.
Excalibur would still hold a descent F1 spot if all the new bots where run, and should come in second right after Multiply4 in F2. I think.
Either way I like excalibur.

And a rape bot is basicaly a bot that forces sexual reproduction on other bots... new feature, not documented in the wiki (I tryed, but the changes won't submit, it just ends up giving me a blank page).

[Numsgil]

If you have the desire, try editing a page again and see if it still won't let you.  I'm trying to fix any wiki issues but I have a hard time isolating all the problems.

[abyaly]

Eh? In that case I suspect my settings have gotten terribly screwed up in some sinister, hidden way. I have excalibur barely surviving on its own. sim attached.


Also, callidus beats excalibur in f1 matches Oo

[Moonfisher]

Ok, just noticed, Excalibur completely falls appart in the newest drop...    
It still has nice eyes though.

[Numsgil]

I don't know Excalibur well enough to say, but it's possible if he doesn't work in the latest version it's a bug in the latest version.

[bacillus]

I found that while Excalibur is still a good bot, it's not one of the Great Ones anymore. I've already coded 3 that can easily beat it, and I know of many more that do so as well.

[Moonfisher]

Excalibur should work again in DB 2.43.1j, there was a bug with poison and venom.
And excalibur may no longer be a top bot, but it's a good simple bot from the old league that still works
And it's also an F2 bot, if it boosted shots it could probably stay in the high end of the F2 league for a while.
Either way I think it's a good example for people who want to get started with league bots.