Re: Pixel Bots
Your API is indeed interesting.
Its a bit more on track than my code. But like I said, I gave my code to
show/prove/test some of the techniques.
However, no offense, lets reconsider, what cards we have, what we want and
how to keep a thing like this maintainable.
First of all, lets keep it much more generic. There are four parts to a bot
(that I could come up with)
-sensing: collision detection, 'hearing' a shot. etc.
-orientation: position, strenght, energy. etc.
-actions: move forward, turn left, shoot. etc.
-communications between bots: sending messages etc.
All of these sides could be 'generalized'.
This means, that have routines to add/register new communication methods,
orientation properties, sensing functions, action procedures. Not to use in
a bot. But to use in a much more specific BOTMatch..
There should also be a sort of generalized 'area' routines. This means that
the actual routines gets the area in a 2D image sequence, it calls every
method/event etc. when applyable.
Within such a framework, you could have a more specific maze solver library,
area battle etc. written...
Like, you said, I dont want to step on anybody's toes, but lets work on the
modelling a little bit more.
Ralf
|
Not Categorized, Please Help
|
|
