.:: Bots United ::. - View Single Post

@$3.1415rin · **Misc bot idea & stuff thread -** 30-11-2004

maybe this could be just some brainstorming thread. not about current code, just about idea's in the bot's design, current problems, wanted features etc. but maybe more from the bot developer side than from the user's side. usually the users come into play later on, when the design and stuff is already done and it's often more a question of tweakin' ...

ok, I start :

currently i'm using a system based on behaviours on the bot and squad level. ( see http://www.lampel.net/johannes/joebo...XPDoc-beta.pdf page 26, behaviours ) the problem is now to get some coherent behaviour on squad level, which isnt simply coded into the different behaviours, but which is more coordinated, which takes care of 2 squads doing the same thing. Currently there is e.g. a bomb planting behaviour on squad level which just get's activated when 60 seconds of a round is played, and then this squad heads to the bomb place if it has the bomb. This isnt what I want, this was just for testing different stuff.

I plan to implement some blackboard on team level. There will be behaviours and the squad which is most suitable ( that's determined just like with the behaviours on bot level ... evaluate is called, each behaviour which can do anything, puts a goal with a priority into some list, and in the end the goal with the highest priority wins ). this way I think that I can control the numbers of sniping squads, rescuing hostages, just securing the place, etc, squads. The only problem is at the moment a nice and elegant implementation, since the evaluation on team level has to be done for a single behavior for multible squads, which somehow collides with my current system of bots / squads 'owning' behaviors

This whole system would also save processing time, since not every squad would have to execute a lot of behaviours, just those which do the basic work and those which were appointed to this squad by the team / blackboard. the bomb plaing behavior e.g. has to be tested by every squad at the moment, which of course takes time.

To come back to planting bombs : somewhen it's suitable to plant the bomb. then the related behaviour would produce a high priority goal. if the goalfinder of the team/blackboard 'thinks' that this is ok, i.e. there is no other more important behaviours, the behaviour would be handed over to the squad to be executed. after some time, there gotta be a check if the team wants that behaviour back, or if it's still ok that it is executed by the squad.

ok, that's it ... for now

	(#1)
@$3.1415rin Council Member, Author of JoeBOT Status: Offline Posts: 1,381 Join Date: Nov 2003 Location: Germany	Misc bot idea & stuff thread - 30-11-2004 maybe this could be just some brainstorming thread. not about current code, just about idea's in the bot's design, current problems, wanted features etc. but maybe more from the bot developer side than from the user's side. usually the users come into play later on, when the design and stuff is already done and it's often more a question of tweakin' ... ok, I start : currently i'm using a system based on behaviours on the bot and squad level. ( see http://www.lampel.net/johannes/joebo...XPDoc-beta.pdf page 26, behaviours ) the problem is now to get some coherent behaviour on squad level, which isnt simply coded into the different behaviours, but which is more coordinated, which takes care of 2 squads doing the same thing. Currently there is e.g. a bomb planting behaviour on squad level which just get's activated when 60 seconds of a round is played, and then this squad heads to the bomb place if it has the bomb. This isnt what I want, this was just for testing different stuff. I plan to implement some blackboard on team level. There will be behaviours and the squad which is most suitable ( that's determined just like with the behaviours on bot level ... evaluate is called, each behaviour which can do anything, puts a goal with a priority into some list, and in the end the goal with the highest priority wins ). this way I think that I can control the numbers of sniping squads, rescuing hostages, just securing the place, etc, squads. The only problem is at the moment a nice and elegant implementation, since the evaluation on team level has to be done for a single behavior for multible squads, which somehow collides with my current system of bots / squads 'owning' behaviors This whole system would also save processing time, since not every squad would have to execute a lot of behaviours, just those which do the basic work and those which were appointed to this squad by the team / blackboard. the bomb plaing behavior e.g. has to be tested by every squad at the moment, which of course takes time. To come back to planting bombs : somewhen it's suitable to plant the bomb. then the related behaviour would produce a high priority goal. if the goalfinder of the team/blackboard 'thinks' that this is ok, i.e. there is no other more important behaviours, the behaviour would be handed over to the squad to be executed. after some time, there gotta be a check if the team wants that behaviour back, or if it's still ok that it is executed by the squad. ok, that's it ... for now Last edited by @$3.1415rin; 01-12-2004 at 00:30..