Add subroutines for bot programms about todo

[paulsonnentag]

In my opinion we should discard any events if the bot program has already received an event or is currently executing an event routine

[timgrossmann]

In my opinion we should discard any events if the bot program has already received an event or is currently executing an event routine

I think this would be the best approach, too...
Another idea is, that events get a priority which determines how important they are.
I'm thinking about a case where a marker for "resources" is dropped and after that one of "help me fight" is dropped.

[perguth]

I could imagine such a case (ignoring technical probs of the issue for now):

// code: go find ressources!
game.on('ressourceFound', e => {
  // code: mine and bring home!
})
game.on('enemyDiscovered', e => {
  // since we want to run away, we ignore `ressourceFound` events:
  game.removeListener('ressourceFound') 
  // since we're running away, we're now looking for allies:
  game.on('allyDiscovered', e => {
    // code: group!
  })
  // code: run!
})

(Along the lines of Node EventEmitters)

[H3rby7]

I was also thinking about this issue. My Idea would be to have the robot/unit "know" its current subroutine. When a new event occurs the programmer has access to that information and can decide himself in the event handling how he wants to continue. In your example @timgrossmann

Unit State

• current order: "get ressources"

Event (enemy detected)

• has information on the unit and the Unit state
• when handling this event can check for the current order of the unit

Inside Event: event.ENEMY_DETECTED

if (unit.getCurrentOrder() === action.GATHER_RESSOURCES) {
  unit.issueOrder(action.FLEE)
}

This way we pass the problem and soultion and power to the programmer. He could also not check for the event and always take the newest event, or check if an order is present and just continue. As he pleases.

[H3rby7]

Addressing the multiple Actions event I would suggest to have a list of events that happened in the entity as suggested here in the Object>Unit section. There is an example there.
Again this empowers the coder to chose which event to handle.