google-code-export / badquest

Automatically exported from code.google.com/p/badquest
0 stars 0 forks source link

A.I. Demo #67

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
To get a basis for game A.I., put together the "Key-per" scenario. Hopefully 
enough will be learned from getting it functioning to have a grasp of 
requirements for enemy A.I. The specification is as follows:

The Key-per of Closed Doors
-Wants to see all doors in his room closed and locked
-Actions include:
  -Patrolling the room in search of an open door (achieved through a predefined waypoint list)
  -Recognizing all doors within a certain vision arc
  -Moving to an open door
  -Closing a door
  -Locking a door

The Key-per of Open Doors
-Wants to see all doors in the room unlocked and opened
-Actions include:
  -Patrolling the room in search of a closed door
  -Recognizing all doors within a certain vision arc
  -Moving to a closed door
  -Unlocking a locked door
  -Opening a door

Since the two entities share several actions, it would be ideal if some could 
be recycled between the two. A goal for this issue is to find some modularity 
when writing behaviors.

Original issue reported on code.google.com by mikeg3...@gmail.com on 9 May 2013 at 1:44

GoogleCodeExporter commented 9 years ago
Hey, not bad! There are some issues with MoveTo that need to be worked out, as 
well as some additional transitions that may need to be added. For example, 
OpenDoors wants to move to the center of the room but cannot because all of the 
doors leading there have been closed. Because of this, there is no valid path, 
even though he could easily make one.

Original comment by mikeg3...@gmail.com on 6 Jun 2013 at 11:49

Attachments: