http://gameai.com/wiki/api.php?action=feedcontributions&user=Dave+Mark&feedformat=atom 2013-05-21T18:40:54Z User contributions MediaWiki 1.18.0 http://gameai.com/wiki/index.php?title=Medal_of_Honor:_Underground 2011-08-15T14:40:59Z

<p>Dave Mark: /* Believable Behaivors */ spelling</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> <br /> <br /> {{GameInfoBox<br /> |gametitle=Medal of Honor: Underground<br /> |imagefile=Medal_of_Honor_-_Underground_Coverart.png<br /> |developer=Dreamworks Interactive<br /> |publisher=Electronic Arts<br /> |year=2000<br /> |platforms=PSX<br /> |genres=FPS<br /> |era=Tactical Reasoning<br /> }}<br /> <br /> ''[http://en.wikipedia.org/wiki/Medal_of_Honor:_Underground Medal of Honor: Underground]'' is a videogame that is the prequel to the World War II hit ''Medal of Honor''. In ''Underground'', the player takes the role of Manon Batiste (Based on Helene Deschamps Adams), a French woman who appeared in the first game as an adviser.<br /> <br /> ==Description of AI Behavior==<br /> The AI in the original MoH game had been fairly rich. The enemies would use cover, attack in groups, and even throw back grenades the player tossed. In Underground, we wanted to further enrich that set of behaviors, as well as add some unique flavor to the game. Because of the incremental nature of this game, the AI had a huge amount of triggers that the AI would respond to. The inclusion of Disguise Mode (where the main character would dress as a journalist, and infiltrate areas in a non-combative way) meant there was also a large number of non combat behaviors that needed to be built for the AI characters as well.<br /> <br /> <br /> ===Notable Behaviors===<br /> One of the things that the original game didn't have was any vehicles, from either side of the joystick. You were always on foot, and were always fighting against other soldiers on foot. The first thing I worked on for this game was AI controlled tanks, which added a lot of WWII flavor to the game. Also added the motorcycle level, which was a major departure in gameplay from the norm (it was more of an on rails shooter than the open world FPS game) and so it worked very well. Also, since the original game already had a nice complement of weapons, we were able to add some of the more esoteric weapons into the game (as well as having the AI characters use them). The AI had to be given behaviors to use and deal with all these new gameplay elements. The game also had a ton more story specific behaviors because the backstory was actually a much larger part of this game than in the first Medal of Honor.<br /> Finally, the game had a full &quot;companion&quot; that was fully AI controlled and would either follow you through the level and help, or in some cases go off on his own and meet you in later parts of the level. This was a very large undertaking, since we didn't want this companion to be a sore spot if he acted stupid or didn't help in appreciable ways.<br /> <br /> <br /> <br /> ==Architectures==<br /> <br /> ===Scripted trigger based State Machine===<br /> {{AuthorStamp|name=Brian Schwab|url=http://www.linkedin.com/pub/brian-schwab/0/687/507}}The entire game was created using small event driven scripts. These scripts could turn on/off various event triggers, set variables, play sounds, assign AI animations, or fire other events. Any individual event script was quite simple. The magic behind this game was the sheer amount of event scripts that comprised the AI. There were hundreds of reactive scripts that could be available during open gameplay, and hundreds more that were more serial in nature for story elements. For the most part, behavior collisions were handled with a very simple number based priority system, as well as randomly choosing when multiple behaviors of the same priority were available. Again, the architecture wasn't the key here. It was the sheer amount of AI content involved.<br /> <br /> ==Post-Mortem==<br /> <br /> <br /> ===What Worked===<br /> <br /> ====Believable Behaviors====<br /> {{AuthorStamp|name=Brian Schwab|url=http://www.linkedin.com/pub/brian-schwab/0/687/507}}<br /> Because of the richness of the total behavior set, the game really felt immersive and alive. The enemies had an enormous amount of potential behaviors at any given time, and as such didn't seem repetitive or overly scripted, instead there were many small atomic actions blending together into a much more organic sort of AI.<br /> <br /> ====Many different types of interactions====<br /> {{AuthorStamp|name=Brian Schwab|url=http://www.linkedin.com/pub/brian-schwab/0/687/507}}<br /> The first Medal of Honor game was all combat, just in different locales. In Underground, we wanted to enrich the experience by giving the player other things to do. Some missions you were heavily involved with your AI companion. Other missions, you were disguised as a journalist and taking pictures of guards. There was a much larger bank of types of interactivity with Underground then there was before.<br /> <br /> ===What Didn't Work===<br /> <br /> ====Typical State Machine Issues====<br /> {{AuthorStamp|name=Brian Schwab|url=http://www.linkedin.com/pub/brian-schwab/0/687/507}}<br /> Classic state machine problems. Eventually, you get lots of reactions to a particular event, which means decision collisions. The trick is to just allow them, and randomly choose amongst the collisions. Making a ton of &quot;equivalent&quot; reactions that would be chosen between made the game seem much less deterministic and rich. Making very specific behaviors does nothing but make new categories of behavior that you then have a limited number of reactions to. This game required a lot more story moments than the first MoH, so there were a lot more specific event reactions. These definitely didn't feel as rich as the rest of the game, but this really only affected replay value, as opposed to how fun it was to play.<br /> <br /> ====Obfuscation====<br /> {{AuthorStamp|name=Brian Schwab|url=http://www.linkedin.com/pub/brian-schwab/0/687/507}}<br /> Because the behaviors were described as a series of small scripts, the overall picture of behavior connectivity was largely in the author's head. There was no tool for visualizing this connected web of behaviors, and as such following the thread of potential AI activity could be tedious or even difficult to follow. Many greps died to bring you this information.<br /> <br /> ==Reception by Public==<br /> {{AuthorStamp|name=Brian Schwab|url=http://www.linkedin.com/pub/brian-schwab/0/687/507}}<br /> Pretty successful overall. Game was reviewed well, and seen as a worthy sequel. There were still issues, but they were more because this was later in the life cycle of the PS1, and as such the next generation of game systems had started to come out (Sega Dreamcast, PS2 had just come out). So the lower graphic fidelity, much lower polygon counts, and some of the classic fixed point collision issues were not seen in the same light as they would have been just a year earlier.</div>

Dave Mark http://gameai.com/wiki/index.php?title=Medal_of_Honor:_Underground 2011-08-08T19:30:12Z

<p>Dave Mark: Cleaned up author stamps</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> <br /> <br /> {{GameInfoBox<br /> |gametitle=Medal of Honor: Underground<br /> |imagefile=Medal_of_Honor_-_Underground_Coverart.png<br /> |developer=Dreamworks Interactive<br /> |publisher=Electronic Arts<br /> |year=2000<br /> |platforms=PSX<br /> |genres=FPS<br /> |era=Tactical Reasoning<br /> }}<br /> <br /> ''[http://en.wikipedia.org/wiki/Medal_of_Honor:_Underground Medal of Honor: Underground]'' is a videogame that is the prequel to the World War II hit ''Medal of Honor''. In ''Underground'', the player takes the role of Manon Batiste (Based on Helene Deschamps Adams), a French woman who appeared in the first game as an adviser.<br /> <br /> ==Description of AI Behavior==<br /> The AI in the original MoH game had been fairly rich. The enemies would use cover, attack in groups, and even throw back grenades the player tossed. In Underground, we wanted to further enrich that set of behaviors, as well as add some unique flavor to the game. Because of the incremental nature of this game, the AI had a huge amount of triggers that the AI would respond to. The inclusion of Disguise Mode (where the main character would dress as a journalist, and infiltrate areas in a non-combative way) meant there was also a large number of non combat behaviors that needed to be built for the AI characters as well.<br /> <br /> <br /> ===Notable Behaviors===<br /> One of the things that the original game didn't have was any vehicles, from either side of the joystick. You were always on foot, and were always fighting against other soldiers on foot. The first thing I worked on for this game was AI controlled tanks, which added a lot of WWII flavor to the game. Also added the motorcycle level, which was a major departure in gameplay from the norm (it was more of an on rails shooter than the open world FPS game) and so it worked very well. Also, since the original game already had a nice complement of weapons, we were able to add some of the more esoteric weapons into the game (as well as having the AI characters use them). The AI had to be given behaviors to use and deal with all these new gameplay elements. The game also had a ton more story specific behaviors because the backstory was actually a much larger part of this game than in the first Medal of Honor.<br /> Finally, the game had a full &quot;companion&quot; that was fully AI controlled and would either follow you through the level and help, or in some cases go off on his own and meet you in later parts of the level. This was a very large undertaking, since we didn't want this companion to be a sore spot if he acted stupid or didn't help in appreciable ways.<br /> <br /> <br /> <br /> ==Architectures==<br /> <br /> ===Scripted trigger based State Machine===<br /> {{AuthorStamp|name=Brian Schwab|url=http://www.linkedin.com/pub/brian-schwab/0/687/507}}The entire game was created using small event driven scripts. These scripts could turn on/off various event triggers, set variables, play sounds, assign AI animations, or fire other events. Any individual event script was quite simple. The magic behind this game was the sheer amount of event scripts that comprised the AI. There were hundreds of reactive scripts that could be available during open gameplay, and hundreds more that were more serial in nature for story elements. For the most part, behavior collisions were handled with a very simple number based priority system, as well as randomly choosing when multiple behaviors of the same priority were available. Again, the architecture wasn't the key here. It was the sheer amount of AI content involved.<br /> <br /> ==Post-Mortem==<br /> <br /> <br /> ===What Worked===<br /> <br /> ====Believable Behaivors====<br /> {{AuthorStamp|name=Brian Schwab|url=http://www.linkedin.com/pub/brian-schwab/0/687/507}}<br /> Because of the richness of the total behavior set, the game really felt immersive and alive. The enemies had an enormous amount of potential behaviors at any given time, and as such didn't seem repetitive or overly scripted, instead there were many small atomic actions blending together into a much more organic sort of AI.<br /> <br /> ====Many different types of interactions====<br /> {{AuthorStamp|name=Brian Schwab|url=http://www.linkedin.com/pub/brian-schwab/0/687/507}}<br /> The first Medal of Honor game was all combat, just in different locales. In Underground, we wanted to enrich the experience by giving the player other things to do. Some missions you were heavily involved with your AI companion. Other missions, you were disguised as a journalist and taking pictures of guards. There was a much larger bank of types of interactivity with Underground then there was before.<br /> <br /> ===What Didn't Work===<br /> <br /> ====Typical State Machine Issues====<br /> {{AuthorStamp|name=Brian Schwab|url=http://www.linkedin.com/pub/brian-schwab/0/687/507}}<br /> Classic state machine problems. Eventually, you get lots of reactions to a particular event, which means decision collisions. The trick is to just allow them, and randomly choose amongst the collisions. Making a ton of &quot;equivalent&quot; reactions that would be chosen between made the game seem much less deterministic and rich. Making very specific behaviors does nothing but make new categories of behavior that you then have a limited number of reactions to. This game required a lot more story moments than the first MoH, so there were a lot more specific event reactions. These definitely didn't feel as rich as the rest of the game, but this really only affected replay value, as opposed to how fun it was to play.<br /> <br /> ====Obfuscation====<br /> {{AuthorStamp|name=Brian Schwab|url=http://www.linkedin.com/pub/brian-schwab/0/687/507}}<br /> Because the behaviors were described as a series of small scripts, the overall picture of behavior connectivity was largely in the author's head. There was no tool for visualizing this connected web of behaviors, and as such following the thread of potential AI activity could be tedious or even difficult to follow. Many greps died to bring you this information.<br /> <br /> ==Reception by Public==<br /> {{AuthorStamp|name=Brian Schwab|url=http://www.linkedin.com/pub/brian-schwab/0/687/507}}<br /> Pretty successful overall. Game was reviewed well, and seen as a worthy sequel. There were still issues, but they were more because this was later in the life cycle of the PS1, and as such the next generation of game systems had started to come out (Sega Dreamcast, PS2 had just come out). So the lower graphic fidelity, much lower polygon counts, and some of the classic fixed point collision issues were not seen in the same light as they would have been just a year earlier.</div>

Dave Mark http://gameai.com/wiki/index.php?title=Halo_3 2011-08-07T03:50:55Z

<p>Dave Mark: /* Declarative Logic */</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> <br /> <br /> {{GameInfoBox<br /> |gametitle=Halo 3<br /> |imagefile=Halo3Box.jpg<br /> |developer=Bungie<br /> |publisher=Microsoft Game Studios<br /> |year=2007<br /> |platforms=X360<br /> |genres=FPS<br /> |era=Tactical Reasoning<br /> }}<br /> <br /> Halo 3 is a first-person shooter game taking the player on a series of missions that engage in combat against various forms of alien life.<br /> <br /> ==Description of AI Behavior==<br /> The enemy agents in Halo 3 exhibited typical shooter game behaviors including moving, shooting, using cover, etc. Additionally, they acted in small tactical groups inside the scope of a battle and the battle as a whole exhibited large-scale coordination of all the units so that large team-based goals were accomplished.<br /> <br /> <br /> ===Notable Behaviors===<br /> The large-scale battle management was a hallmark of the Halo 3 AI. By approaching the entire encounter as a ''system'' that can be managed, the perceived result of battles was that all the enemies were working together toward a common goal such as coordinating the defense of a key target. <br /> <br /> <br /> ==Architectures==<br /> <br /> ===Declarative Logic===<br /> {{AuthorStamp|name=Damián Isla|url=http://www.naimadgames.com}}<br /> [[Halo 2]] used hand-designed [[Imperative Logic|imperative logic]] for the behaviors of the agents. That is, designers specified hard rules that the agents followed. The problem with this was that the complexity didn't scale to the levels desired for the design of Halo 3. Instead, Halo 3 utilized [[Declarative Logic|declarative logic]]. <br /> <br /> The underlying approach to this is similar to what is used in games such as [[The Sims]] where objects have &quot;affordances&quot; that can be measured and rated.<br /> <br /> ===Encounter Zones===<br /> {{AuthorStamp|name=Damián Isla|url=http://www.naimadgames.com}}<br /> The battle management system in Halo 3 utilizes designer-placed ''zones'' where the activity takes place. This approach is likened to the &quot;choreography&quot; of the encounter. <br /> <br /> The encounter zones are, in effect, a strategic layer only. Once in the zone, the behavior of each agent is autonomous and, therefore, defined by the agent itself (subject to parameters of the zone).<br /> <br /> [[File:Halo3_zones.png|thumb|alt=Designer-placed zones in Halo 3|Designer-placed zones in Halo 3|250 px]]<br /> As criteria of the zones are met, they change so that the location of the &quot;choreographed&quot; activity changes. For example, a zone could be set up that once the enemy loses a certain number of units, they would fall back to a 2nd zone. If they lose more units, they could be set to fall back again. The result is that it appears that the player is pushing the enemy back to successive strategic locations.<br /> <br /> In addition to the territory for each zone, the designer can specify the rules that are in effect for the zone. This includes:<br /> :* The aggressiveness of the unit<br /> :* The rules of engagement<br /> :* Whether the enemies will follow the player<br /> <br /> ===Task Trees===<br /> {{AuthorStamp|name=Damián Isla|url=http://www.naimadgames.com}}<br /> Instead of specifying details of &quot;who should do what and when&quot;, the designers were able to simply enumerate the tasks that needed doing as part of the mission (usually attached to the encounter zones above) and the system would figure who should do them. Tasks are given relative priorities. For example, a &quot;plain language&quot; version of this would read:<br /> &lt;blockquote&gt;“The most important thing is to guard the door, but if you can, also guard the hallway”&lt;/blockquote&gt;<br /> This could simply be accomplished by setting the values of guarding the door to a numerical priority higher than that of the guarding the hallway. Note that the priorities here are not for the individual actors but for the encounter ''as a whole''. <br /> <br /> Tasks can also have sub-tasks. This would read:<br /> &lt;blockquote&gt;“Guarding the hallway means guarding the front, the middle and the rear of the hallway.”&lt;/blockquote&gt;<br /> [[File:Halo3_task_tree.png|thumb|alt=A tree of tasks|A tree of tasks|250 px]]<br /> While the structure of tasks and sub-tasks may look similar to the structure of a [[behavior tree]], there is a significant difference. While a behavior tree is generally trying to parse out the ''single action'' to take at a given time, the task tree is attempting to intelligently distribute enemies across all of the possible tasks.<br /> <br /> The tasks are self-describing given:<br /> :* a priority, <br /> :* a script fragments specified by the designer to determine when the task is activated, <br /> :* a capacity for the task that is used for assigning the resources.<br /> <br /> The approach for distributing the tasks is to &quot;pour the squads into the top of the tree&quot; and allow them to filter down to the most important tasks that need to be filled ''right now''. As tasks are enabled and disabled, squads can be reassigned throughout the tree. For example, if a higher priority task is enabled, squads will be &quot;pulled up&quot; from lower priority tasks until the higher priority task is filled.<br /> <br /> ===Squad Distribution===<br /> {{AuthorStamp|name=Damián Isla|url=http://www.naimadgames.com}}<br /> The distribution of squads across the task tree follows the following procedure:<br /> <br /> :* Consider a sub-tree fragment<br /> :* Determine which tasks are active (using the script fragments)<br /> :** Any squads assigned to a deactivated task are reassigned up to the parent<br /> :* Divide tasks into groups of equal priority<br /> :* Consider the group with the top priority<br /> :* Collect squads from:<br /> :** The parent<br /> :** Tasks with ''lower'' priority than the current group<br /> :* Distribute squads across tasks in the priority group<br /> :** Recurse down the tree so that tasks that are ''parent'' tasks can distribute their squads accordingly<br /> :* Move to the next lower priority group and repeat until there are no more tasks at that level<br /> <br /> The mapping of squads to tasks needs to respect two factors:<br /> :* Respect the capacity constraint of the task<br /> :* Minimize the cost function for the task<br /> <br /> The capacity restraints are slightly more complicated than simply (''proposed &lt; maximum'') because agents are being assigned by ''squad'' rather than individually. Squads may be different sizes at any given time based on initial size and losses within the squad. This approach is solved using a classic [http://en.wikipedia.org/wiki/Bin_packing_problem bin packing] approach but with tolerances for sub-optimal results. One reason for this is that the focus is on the cost function rather than the optimal arrangement of squads.<br /> <br /> [[File:Halo3 minimizing cost function.png|thumb|alt=Coordinating movement|Coordinating movement|100 px]]<br /> The cost function helps to determine which distribution of squads to tasks is the most preferable. It takes into account the following preferences:<br /> :* Minimize travel distance per squad<br /> :* Act in a coordinated fashion with other squads<br /> :* Balance the task tree<br /> :* Get near to the player<br /> <br /> While iterating through all the possible squad-to-task mappings was potentially expensive (''O(n&lt;sup&gt;2&lt;/sup&gt;m)''), it was manageable due to the small numbers of squads and tasks. Regardless, they made a point to cache the costs of actions since that was the most expensive portion of the process. Additionally, the entire tree was time-sliced. Considering that there were numerous trees processing for different types of enemies, they would restrict that only certain trees were being processed at certain times.<br /> <br /> Filters were added to restrict types of agents were available to be assigned to a task. These included the type of characters, status of characters (in or out of vehicles), etc. This was done by returning an infinite value from the cost function so that the agent would not be considered for that task.<br /> <br /> ===Behavior Trees===<br /> {{NeedsInput}}<br /> Individual agent actions are performed by [[behavior trees]] as they were in [[Halo 2]].<br /> <br /> <br /> <br /> ==Post-Mortem==<br /> <br /> ===What Worked===<br /> <br /> ====Declarative Approach====<br /> The declarative approach in the strategic system allowed for more flexibility than the traditional imperative approach. Additionally, it required less direct control of agents. Designers could set ''concepts'' rather than individual ''behaviors''.<br /> <br /> <br /> <br /> ====Hierarchies====<br /> The hierarchical nature of the strategic system allowed for more modularity and scalability. Because of the modular nature of the task system, the O(''n&lt;sup&gt;2&lt;/sup&gt;'') complexity of a rule-based system was avoided. Instead, the system was simply O(''n'').<br /> <br /> <br /> <br /> ====Designer Tools====<br /> Because of the way the system was organized, it allowed for creation of designer tools to streamline the production of the encounters. It was flexible enough to incorporate many of the designers' desired features.<br /> <br /> <br /> <br /> ===What Didn't Work===<br /> <br /> ====Designer Training====<br /> Because of the complexity of the designer authoring tools, designers needed to be trained on the use of the tool, the terminology, and the logical progression of how the canonical system worked.<br /> <br /> <br /> <br /> ====Scripting vs. Objectives====<br /> There were sometimes awkward relationships between the scripting system and the objectives-based system.<br /> <br /> <br /> <br /> ====Fronts====<br /> There were sometimes difficulties in &quot;tying together&quot; allied and enemy fronts so that battles seemed properly &quot;aligned&quot;.<br /> <br /> <br /> <br /> ====Squad Bucketing====<br /> There were situations where the squad level wasn't the best arrangement of resources. For example, if you gave a sniper rifle to someone, he was still a member of the parent squad rather than occupying the &quot;sniper&quot; task.<br /> <br /> <br /> <br /> ===Lessons Learned===<br /> {{NeedsInput}}<br /> <br /> <br /> ==Reception by Public==<br /> (TODO)<br /> <br /> <br /> <br /> ==References==<br /> {{reflist|url=http://www.bungie.net/images/Inside/publications/presentations/betterbattle.zip|sourcename=Building A Better Battle: The Halo 3 AI Objectives System (slides)|author=Damián Isla|year=2008|venue=GDC}}<br /> {{reflist|url=http://www.gdcvault.com/play/497/Building-a-Better-Battle-HALO|sourcename=Building A Better Battle: The Halo 3 AI Objectives System (video)|author=Damián Isla|year=2008|venue=GDC}}<br /> <br /> <br /> ==External Links==<br /> (ADD LATER)</div>

Dave Mark http://gameai.com/wiki/index.php?title=Game_Index 2011-08-07T00:55:53Z

<p>Dave Mark: spacing</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> This is a list of games that currently have ''history of AI'' pages:<br /> <br /> <br /> {{template:TOC}}<br /> <br /> <br /> <br /> ==0-9==<br /> <br /> <br /> ==A==<br /> <br /> <br /> ==B==<br /> {{GameIndexEntry|title=Buffy the Vampire Slayer|page=Buffy the Vampire Slayer|developer=The Collective|publisher=Fox Interactive|year=2002|platforms=Xbox}}<br /> {{GameIndexEntry|title=Black and White|page=Black &amp; White|developer=Lionhead|publisher=Electronic Arts|year=2001|platforms=PC, Mac}}<br /> <br /> ==C==<br /> <br /> <br /> ==D==<br /> <br /> <br /> ==E==<br /> <br /> <br /> ==F==<br /> <br /> <br /> ==G==<br /> <br /> <br /> ==H==<br /> {{GameIndexEntry|title=Halo 2|page=Halo 2|developer=Bungie|publisher=Microsoft Game Studios|year=2004|platforms=Xbox, PC}}<br /> {{GameIndexEntry|title=Halo 3|page=Halo 3|developer=Bungie|publisher=Microsoft Game Studios|year=2007|platforms=Xbox, PC}}<br /> {{GameIndexEntry|title=Halo: Reach|page=Halo: Reach|developer=Bungie|publisher=Microsoft Game Studios|year=2010|platforms=X360}}<br /> <br /> ==I==<br /> {{GameIndexEntry|title=Independence War 2: Edge of Chaos|page=Independence War 2|developer=Particle Systems Ltd.|publisher=Infogrames|year=2001|platforms=PC}}<br /> <br /> ==J==<br /> <br /> <br /> ==K==<br /> <br /> <br /> ==L==<br /> <br /> <br /> ==M==<br /> {{GameIndexEntry|title=Medal of Honor: Underground|page=Medal of Honor: Underground|developer=Dreamworks Interactive|publisher=Electronic Arts|year=2000|platforms=Xbox}}<br /> {{GameIndexEntry|title=Microsoft Baseball 3D|page=Microsoft Baseball 3D|developer=WizBang! Software Productions|publisher=Microsoft Game Studios|platforms=PC|year=1998}}<br /> <br /> ==N==<br /> {{GameIndexEntry|title=NBA Shootout 2003|page=NBA Shootout 2003|developer=989|publisher=Sony Computer Entertainment|year=2002|platforms=PS2}}<br /> {{GameIndexEntry|title=NBA '09: The Inside|page=NBA '09: The Inside|developer=SCE San Diego|publisher=Sony Computer Entertainment|year=2008|platforms=PS2, PS3}}<br /> <br /> ==O==<br /> <br /> <br /> ==P==<br /> {{GameIndexEntry|title=Pac-Man|page=Pac-Man|developer=Namco|publisher=Namco, Midway|platforms=Arcade|year=1980}}<br /> {{GameIndexEntry|title=Powerdrome|page=Powerdrome|developer=Argonaut Software|publisher=Mad Duck Productions|year=2004|platforms=PS2, Xbox, PC}}<br /> <br /> ==Q==<br /> <br /> <br /> ==R==<br /> {{GameIndexEntry|title=Rescue on Fractalus!|page=Rescue on Fractalus!|developer=Lucasfilm Games|publisher=Epyx, Atari, Activision|platforms=Amstrad CPC, Apple II, Atari 5200, Atari 8-bit, Commodore 64, Commodore 128, TRS-80 CoCo, ZX Spectrum|year=1984}}<br /> <br /> ==S==<br /> {{GameIndexEntry|title=SimCity|page=SimCity|developer=Maxis|publisher=Brøderbund|platforms=Amiga, Atari ST, C64, Macintosh, PC|year=1989}}<br /> {{GameIndexEntry|title=The Sims|page=The Sims|developer=Maxis|publisher=Electronic Arts|platforms=PC, Macintosh, PS2, Xbox, GameCube|year=2000}}<br /> {{GameIndexEntry|title=Sims 3|page=Sims 3|developer=Sims 3|publisher=Electronic Arts|platforms=Windows, Mac OS X, iOS, webOS, Android, Symbian^3, Nintendo DS, Nintendo 3DS, Wii, PS3, X360|year=2009}}<br /> <br /> ==T==<br /> <br /> <br /> ==U==<br /> <br /> <br /> ==V==<br /> <br /> <br /> ==W==<br /> <br /> <br /> ==X==<br /> {{GameIndexEntry|title=X3 Reunion|page=X3 Reunion|developer=Egosoft|publisher=Deep Silver, Enlight|platforms=PC|year=2005}}<br /> <br /> ==Y==<br /> <br /> <br /> ==Z==<br /> <br /> ==Misc.==<br /> {{GameIndexEntry|title=Game History Format|page=Game History Format|developer=Use this for new games|publisher=AIGPG|platforms=All|year=2011}}</div>

Dave Mark http://gameai.com/wiki/index.php?title=Halo_3 2011-08-06T21:34:19Z

<p>Dave Mark: spacing</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> <br /> <br /> {{GameInfoBox<br /> |gametitle=Halo 3<br /> |imagefile=Halo3Box.jpg<br /> |developer=Bungie<br /> |publisher=Microsoft Game Studios<br /> |year=2007<br /> |platforms=X360<br /> |genres=FPS<br /> |era=Tactical Reasoning<br /> }}<br /> <br /> Halo 3 is a first-person shooter game taking the player on a series of missions that engage in combat against various forms of alien life.<br /> <br /> ==Description of AI Behavior==<br /> The enemy agents in Halo 3 exhibited typical shooter game behaviors including moving, shooting, using cover, etc. Additionally, they acted in small tactical groups inside the scope of a battle and the battle as a whole exhibited large-scale coordination of all the units so that large team-based goals were accomplished.<br /> <br /> <br /> ===Notable Behaviors===<br /> The large-scale battle management was a hallmark of the Halo 3 AI. By approaching the entire encounter as a ''system'' that can be managed, the perceived result of battles was that all the enemies were working together toward a common goal such as coordinating the defense of a key target. <br /> <br /> <br /> ==Architectures==<br /> <br /> ===Declarative Logic===<br /> {{AuthorStamp|name=Damián Isla|url=http://www.naimadgames.com}}<br /> Halo 2 used hand-designed [[Imperative Logic|imperative logic]] for the behaviors of the agents. That is, designers specified hard rules that the agents followed. The problem with this was that the complexity didn't scale to the levels desired for the design of Halo 3. Instead, Halo 3 utilized [[Declarative Logic|declarative logic]]. <br /> <br /> The underlying approach to this is similar to what is used in games such as [[The Sims]] where objects have &quot;affordances&quot; that can be measured and rated.<br /> <br /> ===Encounter Zones===<br /> {{AuthorStamp|name=Damián Isla|url=http://www.naimadgames.com}}<br /> The battle management system in Halo 3 utilizes designer-placed ''zones'' where the activity takes place. This approach is likened to the &quot;choreography&quot; of the encounter. <br /> <br /> The encounter zones are, in effect, a strategic layer only. Once in the zone, the behavior of each agent is autonomous and, therefore, defined by the agent itself (subject to parameters of the zone).<br /> <br /> [[File:Halo3_zones.png|thumb|alt=Designer-placed zones in Halo 3|Designer-placed zones in Halo 3|250 px]]<br /> As criteria of the zones are met, they change so that the location of the &quot;choreographed&quot; activity changes. For example, a zone could be set up that once the enemy loses a certain number of units, they would fall back to a 2nd zone. If they lose more units, they could be set to fall back again. The result is that it appears that the player is pushing the enemy back to successive strategic locations.<br /> <br /> In addition to the territory for each zone, the designer can specify the rules that are in effect for the zone. This includes:<br /> :* The aggressiveness of the unit<br /> :* The rules of engagement<br /> :* Whether the enemies will follow the player<br /> <br /> ===Task Trees===<br /> {{AuthorStamp|name=Damián Isla|url=http://www.naimadgames.com}}<br /> Instead of specifying details of &quot;who should do what and when&quot;, the designers were able to simply enumerate the tasks that needed doing as part of the mission (usually attached to the encounter zones above) and the system would figure who should do them. Tasks are given relative priorities. For example, a &quot;plain language&quot; version of this would read:<br /> &lt;blockquote&gt;“The most important thing is to guard the door, but if you can, also guard the hallway”&lt;/blockquote&gt;<br /> This could simply be accomplished by setting the values of guarding the door to a numerical priority higher than that of the guarding the hallway. Note that the priorities here are not for the individual actors but for the encounter ''as a whole''. <br /> <br /> Tasks can also have sub-tasks. This would read:<br /> &lt;blockquote&gt;“Guarding the hallway means guarding the front, the middle and the rear of the hallway.”&lt;/blockquote&gt;<br /> [[File:Halo3_task_tree.png|thumb|alt=A tree of tasks|A tree of tasks|250 px]]<br /> While the structure of tasks and sub-tasks may look similar to the structure of a [[behavior tree]], there is a significant difference. While a behavior tree is generally trying to parse out the ''single action'' to take at a given time, the task tree is attempting to intelligently distribute enemies across all of the possible tasks.<br /> <br /> The tasks are self-describing given:<br /> :* a priority, <br /> :* a script fragments specified by the designer to determine when the task is activated, <br /> :* a capacity for the task that is used for assigning the resources.<br /> <br /> The approach for distributing the tasks is to &quot;pour the squads into the top of the tree&quot; and allow them to filter down to the most important tasks that need to be filled ''right now''. As tasks are enabled and disabled, squads can be reassigned throughout the tree. For example, if a higher priority task is enabled, squads will be &quot;pulled up&quot; from lower priority tasks until the higher priority task is filled.<br /> <br /> ===Squad Distribution===<br /> {{AuthorStamp|name=Damián Isla|url=http://www.naimadgames.com}}<br /> The distribution of squads across the task tree follows the following procedure:<br /> <br /> :* Consider a sub-tree fragment<br /> :* Determine which tasks are active (using the script fragments)<br /> :** Any squads assigned to a deactivated task are reassigned up to the parent<br /> :* Divide tasks into groups of equal priority<br /> :* Consider the group with the top priority<br /> :* Collect squads from:<br /> :** The parent<br /> :** Tasks with ''lower'' priority than the current group<br /> :* Distribute squads across tasks in the priority group<br /> :** Recurse down the tree so that tasks that are ''parent'' tasks can distribute their squads accordingly<br /> :* Move to the next lower priority group and repeat until there are no more tasks at that level<br /> <br /> The mapping of squads to tasks needs to respect two factors:<br /> :* Respect the capacity constraint of the task<br /> :* Minimize the cost function for the task<br /> <br /> The capacity restraints are slightly more complicated than simply (''proposed &lt; maximum'') because agents are being assigned by ''squad'' rather than individually. Squads may be different sizes at any given time based on initial size and losses within the squad. This approach is solved using a classic [http://en.wikipedia.org/wiki/Bin_packing_problem bin packing] approach but with tolerances for sub-optimal results. One reason for this is that the focus is on the cost function rather than the optimal arrangement of squads.<br /> <br /> [[File:Halo3 minimizing cost function.png|thumb|alt=Coordinating movement|Coordinating movement|100 px]]<br /> The cost function helps to determine which distribution of squads to tasks is the most preferable. It takes into account the following preferences:<br /> :* Minimize travel distance per squad<br /> :* Act in a coordinated fashion with other squads<br /> :* Balance the task tree<br /> :* Get near to the player<br /> <br /> While iterating through all the possible squad-to-task mappings was potentially expensive (''O(n&lt;sup&gt;2&lt;/sup&gt;m)''), it was manageable due to the small numbers of squads and tasks. Regardless, they made a point to cache the costs of actions since that was the most expensive portion of the process. Additionally, the entire tree was time-sliced. Considering that there were numerous trees processing for different types of enemies, they would restrict that only certain trees were being processed at certain times.<br /> <br /> Filters were added to restrict types of agents were available to be assigned to a task. These included the type of characters, status of characters (in or out of vehicles), etc. This was done by returning an infinite value from the cost function so that the agent would not be considered for that task.<br /> <br /> ===Behavior Trees===<br /> {{NeedsInput}}<br /> Individual agent actions are performed by [[behavior trees]] as they were in [[Halo 2]].<br /> <br /> <br /> <br /> ==Post-Mortem==<br /> <br /> ===What Worked===<br /> <br /> ====Declarative Approach====<br /> The declarative approach in the strategic system allowed for more flexibility than the traditional imperative approach. Additionally, it required less direct control of agents. Designers could set ''concepts'' rather than individual ''behaviors''.<br /> <br /> <br /> <br /> ====Hierarchies====<br /> The hierarchical nature of the strategic system allowed for more modularity and scalability. Because of the modular nature of the task system, the O(''n&lt;sup&gt;2&lt;/sup&gt;'') complexity of a rule-based system was avoided. Instead, the system was simply O(''n'').<br /> <br /> <br /> <br /> ====Designer Tools====<br /> Because of the way the system was organized, it allowed for creation of designer tools to streamline the production of the encounters. It was flexible enough to incorporate many of the designers' desired features.<br /> <br /> <br /> <br /> ===What Didn't Work===<br /> <br /> ====Designer Training====<br /> Because of the complexity of the designer authoring tools, designers needed to be trained on the use of the tool, the terminology, and the logical progression of how the canonical system worked.<br /> <br /> <br /> <br /> ====Scripting vs. Objectives====<br /> There were sometimes awkward relationships between the scripting system and the objectives-based system.<br /> <br /> <br /> <br /> ====Fronts====<br /> There were sometimes difficulties in &quot;tying together&quot; allied and enemy fronts so that battles seemed properly &quot;aligned&quot;.<br /> <br /> <br /> <br /> ====Squad Bucketing====<br /> There were situations where the squad level wasn't the best arrangement of resources. For example, if you gave a sniper rifle to someone, he was still a member of the parent squad rather than occupying the &quot;sniper&quot; task.<br /> <br /> <br /> <br /> ===Lessons Learned===<br /> {{NeedsInput}}<br /> <br /> <br /> ==Reception by Public==<br /> (TODO)<br /> <br /> <br /> <br /> ==References==<br /> {{reflist|url=http://www.bungie.net/images/Inside/publications/presentations/betterbattle.zip|sourcename=Building A Better Battle: The Halo 3 AI Objectives System (slides)|author=Damián Isla|year=2008|venue=GDC}}<br /> {{reflist|url=http://www.gdcvault.com/play/497/Building-a-Better-Battle-HALO|sourcename=Building A Better Battle: The Halo 3 AI Objectives System (video)|author=Damián Isla|year=2008|venue=GDC}}<br /> <br /> <br /> ==External Links==<br /> (ADD LATER)</div>

Dave Mark http://gameai.com/wiki/index.php?title=Halo_3 2011-08-06T21:33:20Z

<p>Dave Mark: /* Behavior Trees */</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> <br /> <br /> {{GameInfoBox<br /> |gametitle=Halo 3<br /> |imagefile=Halo3Box.jpg<br /> |developer=Bungie<br /> |publisher=Microsoft Game Studios<br /> |year=2007<br /> |platforms=X360<br /> |genres=FPS<br /> |era=Tactical Reasoning<br /> }}<br /> <br /> Halo 3 is a first-person shooter game taking the player on a series of missions that engage in combat against various forms of alien life.<br /> <br /> ==Description of AI Behavior==<br /> The enemy agents in Halo 3 exhibited typical shooter game behaviors including moving, shooting, using cover, etc. Additionally, they acted in small tactical groups inside the scope of a battle and the battle as a whole exhibited large-scale coordination of all the units so that large team-based goals were accomplished.<br /> <br /> <br /> ===Notable Behaviors===<br /> The large-scale battle management was a hallmark of the Halo 3 AI. By approaching the entire encounter as a ''system'' that can be managed, the perceived result of battles was that all the enemies were working together toward a common goal such as coordinating the defense of a key target. <br /> <br /> <br /> ==Architectures==<br /> <br /> ===Declarative Logic===<br /> {{AuthorStamp|name=Damián Isla|url=http://www.naimadgames.com}}<br /> Halo 2 used hand-designed [[Imperative Logic|imperative logic]] for the behaviors of the agents. That is, designers specified hard rules that the agents followed. The problem with this was that the complexity didn't scale to the levels desired for the design of Halo 3. Instead, Halo 3 utilized [[Declarative Logic|declarative logic]]. <br /> <br /> The underlying approach to this is similar to what is used in games such as [[The Sims]] where objects have &quot;affordances&quot; that can be measured and rated.<br /> <br /> ===Encounter Zones===<br /> {{AuthorStamp|name=Damián Isla|url=http://www.naimadgames.com}}<br /> The battle management system in Halo 3 utilizes designer-placed ''zones'' where the activity takes place. This approach is likened to the &quot;choreography&quot; of the encounter. <br /> <br /> The encounter zones are, in effect, a strategic layer only. Once in the zone, the behavior of each agent is autonomous and, therefore, defined by the agent itself (subject to parameters of the zone).<br /> <br /> [[File:Halo3_zones.png|thumb|alt=Designer-placed zones in Halo 3|Designer-placed zones in Halo 3|250 px]]<br /> As criteria of the zones are met, they change so that the location of the &quot;choreographed&quot; activity changes. For example, a zone could be set up that once the enemy loses a certain number of units, they would fall back to a 2nd zone. If they lose more units, they could be set to fall back again. The result is that it appears that the player is pushing the enemy back to successive strategic locations.<br /> <br /> In addition to the territory for each zone, the designer can specify the rules that are in effect for the zone. This includes:<br /> :* The aggressiveness of the unit<br /> :* The rules of engagement<br /> :* Whether the enemies will follow the player<br /> <br /> ===Task Trees===<br /> {{AuthorStamp|name=Damián Isla|url=http://www.naimadgames.com}}<br /> Instead of specifying details of &quot;who should do what and when&quot;, the designers were able to simply enumerate the tasks that needed doing as part of the mission (usually attached to the encounter zones above) and the system would figure who should do them. Tasks are given relative priorities. For example, a &quot;plain language&quot; version of this would read:<br /> &lt;blockquote&gt;“The most important thing is to guard the door, but if you can, also guard the hallway”&lt;/blockquote&gt;<br /> This could simply be accomplished by setting the values of guarding the door to a numerical priority higher than that of the guarding the hallway. Note that the priorities here are not for the individual actors but for the encounter ''as a whole''. <br /> <br /> Tasks can also have sub-tasks. This would read:<br /> &lt;blockquote&gt;“Guarding the hallway means guarding the front, the middle and the rear of the hallway.”&lt;/blockquote&gt;<br /> [[File:Halo3_task_tree.png|thumb|alt=A tree of tasks|A tree of tasks|250 px]]<br /> While the structure of tasks and sub-tasks may look similar to the structure of a [[behavior tree]], there is a significant difference. While a behavior tree is generally trying to parse out the ''single action'' to take at a given time, the task tree is attempting to intelligently distribute enemies across all of the possible tasks.<br /> <br /> The tasks are self-describing given:<br /> :* a priority, <br /> :* a script fragments specified by the designer to determine when the task is activated, <br /> :* a capacity for the task that is used for assigning the resources.<br /> <br /> The approach for distributing the tasks is to &quot;pour the squads into the top of the tree&quot; and allow them to filter down to the most important tasks that need to be filled ''right now''. As tasks are enabled and disabled, squads can be reassigned throughout the tree. For example, if a higher priority task is enabled, squads will be &quot;pulled up&quot; from lower priority tasks until the higher priority task is filled.<br /> <br /> ===Squad Distribution===<br /> {{AuthorStamp|name=Damián Isla|url=http://www.naimadgames.com}}<br /> The distribution of squads across the task tree follows the following procedure:<br /> <br /> :* Consider a sub-tree fragment<br /> :* Determine which tasks are active (using the script fragments)<br /> :** Any squads assigned to a deactivated task are reassigned up to the parent<br /> :* Divide tasks into groups of equal priority<br /> :* Consider the group with the top priority<br /> :* Collect squads from:<br /> :** The parent<br /> :** Tasks with ''lower'' priority than the current group<br /> :* Distribute squads across tasks in the priority group<br /> :** Recurse down the tree so that tasks that are ''parent'' tasks can distribute their squads accordingly<br /> :* Move to the next lower priority group and repeat until there are no more tasks at that level<br /> <br /> The mapping of squads to tasks needs to respect two factors:<br /> :* Respect the capacity constraint of the task<br /> :* Minimize the cost function for the task<br /> <br /> The capacity restraints are slightly more complicated than simply (''proposed &lt; maximum'') because agents are being assigned by ''squad'' rather than individually. Squads may be different sizes at any given time based on initial size and losses within the squad. This approach is solved using a classic [http://en.wikipedia.org/wiki/Bin_packing_problem bin packing] approach but with tolerances for sub-optimal results. One reason for this is that the focus is on the cost function rather than the optimal arrangement of squads.<br /> <br /> [[File:Halo3 minimizing cost function.png|thumb|alt=Coordinating movement|Coordinating movement|100 px]]<br /> The cost function helps to determine which distribution of squads to tasks is the most preferable. It takes into account the following preferences:<br /> :* Minimize travel distance per squad<br /> :* Act in a coordinated fashion with other squads<br /> :* Balance the task tree<br /> :* Get near to the player<br /> <br /> While iterating through all the possible squad-to-task mappings was potentially expensive (''O(n&lt;sup&gt;2&lt;/sup&gt;m)''), it was manageable due to the small numbers of squads and tasks. Regardless, they made a point to cache the costs of actions since that was the most expensive portion of the process. Additionally, the entire tree was time-sliced. Considering that there were numerous trees processing for different types of enemies, they would restrict that only certain trees were being processed at certain times.<br /> <br /> Filters were added to restrict types of agents were available to be assigned to a task. These included the type of characters, status of characters (in or out of vehicles), etc. This was done by returning an infinite value from the cost function so that the agent would not be considered for that task.<br /> <br /> ===Behavior Trees===<br /> {{NeedsInput}}<br /> Individual agent actions are performed by [[behavior trees]] as they were in [[Halo 2]].<br /> <br /> ==Post-Mortem==<br /> <br /> ===What Worked===<br /> <br /> ====Declarative Approach====<br /> The declarative approach in the strategic system allowed for more flexibility than the traditional imperative approach. Additionally, it required less direct control of agents. Designers could set ''concepts'' rather than individual ''behaviors''.<br /> <br /> <br /> <br /> ====Hierarchies====<br /> The hierarchical nature of the strategic system allowed for more modularity and scalability. Because of the modular nature of the task system, the O(''n&lt;sup&gt;2&lt;/sup&gt;'') complexity of a rule-based system was avoided. Instead, the system was simply O(''n'').<br /> <br /> <br /> <br /> ====Designer Tools====<br /> Because of the way the system was organized, it allowed for creation of designer tools to streamline the production of the encounters. It was flexible enough to incorporate many of the designers' desired features.<br /> <br /> <br /> <br /> ===What Didn't Work===<br /> <br /> ====Designer Training====<br /> Because of the complexity of the designer authoring tools, designers needed to be trained on the use of the tool, the terminology, and the logical progression of how the canonical system worked.<br /> <br /> <br /> <br /> ====Scripting vs. Objectives====<br /> There were sometimes awkward relationships between the scripting system and the objectives-based system.<br /> <br /> <br /> <br /> ====Fronts====<br /> There were sometimes difficulties in &quot;tying together&quot; allied and enemy fronts so that battles seemed properly &quot;aligned&quot;.<br /> <br /> <br /> <br /> ====Squad Bucketing====<br /> There were situations where the squad level wasn't the best arrangement of resources. For example, if you gave a sniper rifle to someone, he was still a member of the parent squad rather than occupying the &quot;sniper&quot; task.<br /> <br /> <br /> <br /> ===Lessons Learned===<br /> {{NeedsInput}}<br /> <br /> <br /> ==Reception by Public==<br /> (TODO)<br /> <br /> <br /> <br /> ==References==<br /> {{reflist|url=http://www.bungie.net/images/Inside/publications/presentations/betterbattle.zip|sourcename=Building A Better Battle: The Halo 3 AI Objectives System (slides)|author=Damián Isla|year=2008|venue=GDC}}<br /> {{reflist|url=http://www.gdcvault.com/play/497/Building-a-Better-Battle-HALO|sourcename=Building A Better Battle: The Halo 3 AI Objectives System (video)|author=Damián Isla|year=2008|venue=GDC}}<br /> <br /> <br /> ==External Links==<br /> (ADD LATER)</div>

Dave Mark http://gameai.com/wiki/index.php?title=Halo_3 2011-08-06T21:30:19Z

<p>Dave Mark: Initial creation based on Damian's &quot;Better Battle&quot; GDC presentation</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> <br /> <br /> {{GameInfoBox<br /> |gametitle=Halo 3<br /> |imagefile=Halo3Box.jpg<br /> |developer=Bungie<br /> |publisher=Microsoft Game Studios<br /> |year=2007<br /> |platforms=X360<br /> |genres=FPS<br /> |era=Tactical Reasoning<br /> }}<br /> <br /> Halo 3 is a first-person shooter game taking the player on a series of missions that engage in combat against various forms of alien life.<br /> <br /> ==Description of AI Behavior==<br /> The enemy agents in Halo 3 exhibited typical shooter game behaviors including moving, shooting, using cover, etc. Additionally, they acted in small tactical groups inside the scope of a battle and the battle as a whole exhibited large-scale coordination of all the units so that large team-based goals were accomplished.<br /> <br /> <br /> ===Notable Behaviors===<br /> The large-scale battle management was a hallmark of the Halo 3 AI. By approaching the entire encounter as a ''system'' that can be managed, the perceived result of battles was that all the enemies were working together toward a common goal such as coordinating the defense of a key target. <br /> <br /> <br /> ==Architectures==<br /> <br /> ===Declarative Logic===<br /> {{AuthorStamp|name=Damián Isla|url=http://www.naimadgames.com}}<br /> Halo 2 used hand-designed [[Imperative Logic|imperative logic]] for the behaviors of the agents. That is, designers specified hard rules that the agents followed. The problem with this was that the complexity didn't scale to the levels desired for the design of Halo 3. Instead, Halo 3 utilized [[Declarative Logic|declarative logic]]. <br /> <br /> The underlying approach to this is similar to what is used in games such as [[The Sims]] where objects have &quot;affordances&quot; that can be measured and rated.<br /> <br /> ===Encounter Zones===<br /> {{AuthorStamp|name=Damián Isla|url=http://www.naimadgames.com}}<br /> The battle management system in Halo 3 utilizes designer-placed ''zones'' where the activity takes place. This approach is likened to the &quot;choreography&quot; of the encounter. <br /> <br /> The encounter zones are, in effect, a strategic layer only. Once in the zone, the behavior of each agent is autonomous and, therefore, defined by the agent itself (subject to parameters of the zone).<br /> <br /> [[File:Halo3_zones.png|thumb|alt=Designer-placed zones in Halo 3|Designer-placed zones in Halo 3|250 px]]<br /> As criteria of the zones are met, they change so that the location of the &quot;choreographed&quot; activity changes. For example, a zone could be set up that once the enemy loses a certain number of units, they would fall back to a 2nd zone. If they lose more units, they could be set to fall back again. The result is that it appears that the player is pushing the enemy back to successive strategic locations.<br /> <br /> In addition to the territory for each zone, the designer can specify the rules that are in effect for the zone. This includes:<br /> :* The aggressiveness of the unit<br /> :* The rules of engagement<br /> :* Whether the enemies will follow the player<br /> <br /> ===Task Trees===<br /> {{AuthorStamp|name=Damián Isla|url=http://www.naimadgames.com}}<br /> Instead of specifying details of &quot;who should do what and when&quot;, the designers were able to simply enumerate the tasks that needed doing as part of the mission (usually attached to the encounter zones above) and the system would figure who should do them. Tasks are given relative priorities. For example, a &quot;plain language&quot; version of this would read:<br /> &lt;blockquote&gt;“The most important thing is to guard the door, but if you can, also guard the hallway”&lt;/blockquote&gt;<br /> This could simply be accomplished by setting the values of guarding the door to a numerical priority higher than that of the guarding the hallway. Note that the priorities here are not for the individual actors but for the encounter ''as a whole''. <br /> <br /> Tasks can also have sub-tasks. This would read:<br /> &lt;blockquote&gt;“Guarding the hallway means guarding the front, the middle and the rear of the hallway.”&lt;/blockquote&gt;<br /> [[File:Halo3_task_tree.png|thumb|alt=A tree of tasks|A tree of tasks|250 px]]<br /> While the structure of tasks and sub-tasks may look similar to the structure of a [[behavior tree]], there is a significant difference. While a behavior tree is generally trying to parse out the ''single action'' to take at a given time, the task tree is attempting to intelligently distribute enemies across all of the possible tasks.<br /> <br /> The tasks are self-describing given:<br /> :* a priority, <br /> :* a script fragments specified by the designer to determine when the task is activated, <br /> :* a capacity for the task that is used for assigning the resources.<br /> <br /> The approach for distributing the tasks is to &quot;pour the squads into the top of the tree&quot; and allow them to filter down to the most important tasks that need to be filled ''right now''. As tasks are enabled and disabled, squads can be reassigned throughout the tree. For example, if a higher priority task is enabled, squads will be &quot;pulled up&quot; from lower priority tasks until the higher priority task is filled.<br /> <br /> ===Squad Distribution===<br /> {{AuthorStamp|name=Damián Isla|url=http://www.naimadgames.com}}<br /> The distribution of squads across the task tree follows the following procedure:<br /> <br /> :* Consider a sub-tree fragment<br /> :* Determine which tasks are active (using the script fragments)<br /> :** Any squads assigned to a deactivated task are reassigned up to the parent<br /> :* Divide tasks into groups of equal priority<br /> :* Consider the group with the top priority<br /> :* Collect squads from:<br /> :** The parent<br /> :** Tasks with ''lower'' priority than the current group<br /> :* Distribute squads across tasks in the priority group<br /> :** Recurse down the tree so that tasks that are ''parent'' tasks can distribute their squads accordingly<br /> :* Move to the next lower priority group and repeat until there are no more tasks at that level<br /> <br /> The mapping of squads to tasks needs to respect two factors:<br /> :* Respect the capacity constraint of the task<br /> :* Minimize the cost function for the task<br /> <br /> The capacity restraints are slightly more complicated than simply (''proposed &lt; maximum'') because agents are being assigned by ''squad'' rather than individually. Squads may be different sizes at any given time based on initial size and losses within the squad. This approach is solved using a classic [http://en.wikipedia.org/wiki/Bin_packing_problem bin packing] approach but with tolerances for sub-optimal results. One reason for this is that the focus is on the cost function rather than the optimal arrangement of squads.<br /> <br /> [[File:Halo3 minimizing cost function.png|thumb|alt=Coordinating movement|Coordinating movement|100 px]]<br /> The cost function helps to determine which distribution of squads to tasks is the most preferable. It takes into account the following preferences:<br /> :* Minimize travel distance per squad<br /> :* Act in a coordinated fashion with other squads<br /> :* Balance the task tree<br /> :* Get near to the player<br /> <br /> While iterating through all the possible squad-to-task mappings was potentially expensive (''O(n&lt;sup&gt;2&lt;/sup&gt;m)''), it was manageable due to the small numbers of squads and tasks. Regardless, they made a point to cache the costs of actions since that was the most expensive portion of the process. Additionally, the entire tree was time-sliced. Considering that there were numerous trees processing for different types of enemies, they would restrict that only certain trees were being processed at certain times.<br /> <br /> Filters were added to restrict types of agents were available to be assigned to a task. These included the type of characters, status of characters (in or out of vehicles), etc. This was done by returning an infinite value from the cost function so that the agent would not be considered for that task.<br /> <br /> ===Behavior Trees===<br /> Individual agent actions are performed by [[behavior trees]] as they were in [[Halo 2]].<br /> <br /> <br /> <br /> ==Post-Mortem==<br /> <br /> ===What Worked===<br /> <br /> ====Declarative Approach====<br /> The declarative approach in the strategic system allowed for more flexibility than the traditional imperative approach. Additionally, it required less direct control of agents. Designers could set ''concepts'' rather than individual ''behaviors''.<br /> <br /> <br /> <br /> ====Hierarchies====<br /> The hierarchical nature of the strategic system allowed for more modularity and scalability. Because of the modular nature of the task system, the O(''n&lt;sup&gt;2&lt;/sup&gt;'') complexity of a rule-based system was avoided. Instead, the system was simply O(''n'').<br /> <br /> <br /> <br /> ====Designer Tools====<br /> Because of the way the system was organized, it allowed for creation of designer tools to streamline the production of the encounters. It was flexible enough to incorporate many of the designers' desired features.<br /> <br /> <br /> <br /> ===What Didn't Work===<br /> <br /> ====Designer Training====<br /> Because of the complexity of the designer authoring tools, designers needed to be trained on the use of the tool, the terminology, and the logical progression of how the canonical system worked.<br /> <br /> <br /> <br /> ====Scripting vs. Objectives====<br /> There were sometimes awkward relationships between the scripting system and the objectives-based system.<br /> <br /> <br /> <br /> ====Fronts====<br /> There were sometimes difficulties in &quot;tying together&quot; allied and enemy fronts so that battles seemed properly &quot;aligned&quot;.<br /> <br /> <br /> <br /> ====Squad Bucketing====<br /> There were situations where the squad level wasn't the best arrangement of resources. For example, if you gave a sniper rifle to someone, he was still a member of the parent squad rather than occupying the &quot;sniper&quot; task.<br /> <br /> <br /> <br /> ===Lessons Learned===<br /> {{NeedsInput}}<br /> <br /> <br /> ==Reception by Public==<br /> (TODO)<br /> <br /> <br /> <br /> ==References==<br /> {{reflist|url=http://www.bungie.net/images/Inside/publications/presentations/betterbattle.zip|sourcename=Building A Better Battle: The Halo 3 AI Objectives System (slides)|author=Damián Isla|year=2008|venue=GDC}}<br /> {{reflist|url=http://www.gdcvault.com/play/497/Building-a-Better-Battle-HALO|sourcename=Building A Better Battle: The Halo 3 AI Objectives System (video)|author=Damián Isla|year=2008|venue=GDC}}<br /> <br /> <br /> ==External Links==<br /> (ADD LATER)</div>

Dave Mark http://gameai.com/wiki/index.php?title=File:Halo3_minimizing_cost_function.png 2011-08-06T20:57:34Z

<p>Dave Mark: Coordinating movement by agents to minimize a cost function based on distance traveled.</p> <hr /> <div>Coordinating movement by agents to minimize a cost function based on distance traveled.</div>

Dave Mark http://gameai.com/wiki/index.php?title=File:Halo3_task_tree.png 2011-08-06T20:13:13Z

<p>Dave Mark: A tree of tasks in Halo 3. (Take from &quot;Building a Better Battle&quot; by Damián Isla.)</p> <hr /> <div>A tree of tasks in Halo 3. (Take from &quot;Building a Better Battle&quot; by Damián Isla.)</div>

Dave Mark http://gameai.com/wiki/index.php?title=File:Halo3_zones.png 2011-08-06T19:30:20Z

<p>Dave Mark: Example of designer-placed combat zones in Halo 3. (Take from &quot;Building a Better Battle&quot; by Damián Isla.)</p> <hr /> <div>Example of designer-placed combat zones in Halo 3. (Take from &quot;Building a Better Battle&quot; by Damián Isla.)</div>

Dave Mark http://gameai.com/wiki/index.php?title=Game_Index 2011-07-29T03:32:37Z

<p>Dave Mark: Moved Sims to be under &quot;s&quot;</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> This is a list of games that currently have ''history of AI'' pages:<br /> <br /> <br /> {{template:TOC}}<br /> <br /> <br /> <br /> ==0-9==<br /> <br /> <br /> ==A==<br /> <br /> <br /> ==B==<br /> {{GameIndexEntry|title=Buffy the Vampire Slayer|page=Buffy the Vampire Slayer|developer=The Collective|publisher=Fox Interactive|year=2002|platforms=Xbox}}<br /> {{GameIndexEntry|title=Black and White|page=Black &amp; White|developer=Lionhead|publisher=Electronic Arts|year=2001|platforms=PC, Mac}}<br /> <br /> ==C==<br /> <br /> <br /> ==D==<br /> <br /> <br /> ==E==<br /> <br /> <br /> ==F==<br /> <br /> <br /> ==G==<br /> <br /> <br /> ==H==<br /> {{GameIndexEntry|title=Halo 2|page=Halo 2|developer=Bungie|publisher=Microsoft Game Studios|year=2004|platforms=Xbox, PC}}<br /> {{GameIndexEntry|title=Halo 3|page=Halo 3|developer=Bungie|publisher=Microsoft Game Studios|year=2007|platforms=Xbox, PC}}<br /> {{GameIndexEntry|title=Halo: Reach|page=Halo: Reach|developer=Bungie|publisher=Microsoft Game Studios|year=2010|platforms=X360}}<br /> <br /> ==I==<br /> {{GameIndexEntry|title=Independence War 2: Edge of Chaos|page=Independence War 2|developer=Particle Systems Ltd.|publisher=Infogrames|year=2001|platforms=PC}}<br /> <br /> ==J==<br /> <br /> <br /> ==K==<br /> <br /> <br /> ==L==<br /> <br /> <br /> ==M==<br /> {{GameIndexEntry|title=Medal of Honor: Underground|page=Medal of Honor: Underground|developer=Dreamworks Interactive|publisher=Electronic Arts|year=2000|platforms=Xbox}}<br /> {{GameIndexEntry|title=Microsoft Baseball 3D|page=Microsoft Baseball 3D|developer=WizBang! Software Productions|publisher=Microsoft Game Studios|platforms=PC|year=1998}}<br /> <br /> ==N==<br /> {{GameIndexEntry|title=NBA Shootout 2003|page=NBA Shootout 2003|developer=989|publisher=Sony Computer Entertainment|year=2002|platforms=PS2}}<br /> {{GameIndexEntry|title=NBA '09: The Inside|page=NBA '09: The Inside|developer=SCE San Diego|publisher=Sony Computer Entertainment|year=2008|platforms=PS2, PS3}}<br /> <br /> <br /> ==O==<br /> <br /> <br /> ==P==<br /> {{GameIndexEntry|title=Pac-Man|page=Pac-Man|developer=Namco|publisher=Namco, Midway|platforms=Arcade|year=1980}}<br /> {{GameIndexEntry|title=Powerdrome|page=Powerdrome|developer=Argonaut Software|publisher=Mad Duck Productions|year=2004|platforms=PS2, Xbox, PC}}<br /> <br /> ==Q==<br /> <br /> <br /> ==R==<br /> {{GameIndexEntry|title=Rescue on Fractalus!|page=Rescue on Fractalus!|developer=Lucasfilm Games|publisher=Epyx, Atari, Activision|platforms=Amstrad CPC, Apple II, Atari 5200, Atari 8-bit, Commodore 64, Commodore 128, TRS-80 CoCo, ZX Spectrum|year=1984}}<br /> <br /> ==S==<br /> {{GameIndexEntry|title=SimCity|page=SimCity|developer=Maxis|publisher=Brøderbund|platforms=Amiga, Atari ST, C64, Macintosh, PC|year=1989}}<br /> {{GameIndexEntry|title=The Sims|page=The Sims|developer=Maxis|publisher=Electronic Arts|platforms=PC, Macintosh, PS2, Xbox, GameCube|year=2000}}<br /> {{GameIndexEntry|title=Sims 3|page=Sims 3|developer=Sims 3|publisher=Electronic Arts|platforms=Windows, Mac OS X, iOS, webOS, Android, Symbian^3, Nintendo DS, Nintendo 3DS, Wii, PS3, X360|year=2009}}<br /> <br /> ==T==<br /> <br /> <br /> ==U==<br /> <br /> <br /> ==V==<br /> <br /> <br /> ==W==<br /> <br /> <br /> ==X==<br /> {{GameIndexEntry|title=X3 Reunion|page=X3 Reunion|developer=Egosoft|publisher=Deep Silver, Enlight|platforms=PC|year=2005}}<br /> <br /> ==Y==<br /> <br /> <br /> ==Z==<br /> <br /> ==Misc.==<br /> {{GameIndexEntry|title=Game History Format|page=Game History Format|developer=Use this for new games|publisher=AIGPG|platforms=All|year=2011}}</div>

Dave Mark http://gameai.com/wiki/index.php?title=Game_Index 2011-07-29T03:31:00Z

<p>Dave Mark: /* S */ Added Sims 3</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> This is a list of games that currently have ''history of AI'' pages:<br /> <br /> <br /> {{template:TOC}}<br /> <br /> <br /> <br /> ==0-9==<br /> <br /> <br /> ==A==<br /> <br /> <br /> ==B==<br /> {{GameIndexEntry|title=Buffy the Vampire Slayer|page=Buffy the Vampire Slayer|developer=The Collective|publisher=Fox Interactive|year=2002|platforms=Xbox}}<br /> {{GameIndexEntry|title=Black and White|page=Black &amp; White|developer=Lionhead|publisher=Electronic Arts|year=2001|platforms=PC, Mac}}<br /> <br /> ==C==<br /> <br /> <br /> ==D==<br /> <br /> <br /> ==E==<br /> <br /> <br /> ==F==<br /> <br /> <br /> ==G==<br /> <br /> <br /> ==H==<br /> {{GameIndexEntry|title=Halo 2|page=Halo 2|developer=Bungie|publisher=Microsoft Game Studios|year=2004|platforms=Xbox, PC}}<br /> {{GameIndexEntry|title=Halo 3|page=Halo 3|developer=Bungie|publisher=Microsoft Game Studios|year=2007|platforms=Xbox, PC}}<br /> {{GameIndexEntry|title=Halo: Reach|page=Halo: Reach|developer=Bungie|publisher=Microsoft Game Studios|year=2010|platforms=X360}}<br /> <br /> ==I==<br /> {{GameIndexEntry|title=Independence War 2: Edge of Chaos|page=Independence War 2|developer=Particle Systems Ltd.|publisher=Infogrames|year=2001|platforms=PC}}<br /> <br /> ==J==<br /> <br /> <br /> ==K==<br /> <br /> <br /> ==L==<br /> <br /> <br /> ==M==<br /> {{GameIndexEntry|title=Medal of Honor: Underground|page=Medal of Honor: Underground|developer=Dreamworks Interactive|publisher=Electronic Arts|year=2000|platforms=Xbox}}<br /> {{GameIndexEntry|title=Microsoft Baseball 3D|page=Microsoft Baseball 3D|developer=WizBang! Software Productions|publisher=Microsoft Game Studios|platforms=PC|year=1998}}<br /> <br /> ==N==<br /> {{GameIndexEntry|title=NBA Shootout 2003|page=NBA Shootout 2003|developer=989|publisher=Sony Computer Entertainment|year=2002|platforms=PS2}}<br /> {{GameIndexEntry|title=NBA '09: The Inside|page=NBA '09: The Inside|developer=SCE San Diego|publisher=Sony Computer Entertainment|year=2008|platforms=PS2, PS3}}<br /> <br /> <br /> ==O==<br /> <br /> <br /> ==P==<br /> {{GameIndexEntry|title=Pac-Man|page=Pac-Man|developer=Namco|publisher=Namco, Midway|platforms=Arcade|year=1980}}<br /> {{GameIndexEntry|title=Powerdrome|page=Powerdrome|developer=Argonaut Software|publisher=Mad Duck Productions|year=2004|platforms=PS2, Xbox, PC}}<br /> <br /> ==Q==<br /> <br /> <br /> ==R==<br /> {{GameIndexEntry|title=Rescue on Fractalus!|page=Rescue on Fractalus!|developer=Lucasfilm Games|publisher=Epyx, Atari, Activision|platforms=Amstrad CPC, Apple II, Atari 5200, Atari 8-bit, Commodore 64, Commodore 128, TRS-80 CoCo, ZX Spectrum|year=1984}}<br /> <br /> ==S==<br /> {{GameIndexEntry|title=SimCity|page=SimCity|developer=Maxis|publisher=Brøderbund|platforms=Amiga, Atari ST, C64, Macintosh, PC|year=1989}}<br /> {{GameIndexEntry|title=Sims 3|page=Sims 3|developer=Sims 3|publisher=Electronic Arts|platforms=Windows, Mac OS X, iOS, webOS, Android, Symbian^3, Nintendo DS, Nintendo 3DS, Wii, PS3, X360|year=2009}}<br /> <br /> ==T==<br /> {{GameIndexEntry|title=The Sims|page=The Sims|developer=Maxis|publisher=Electronic Arts|platforms=PC, Macintosh, PS2, Xbox, GameCube|year=2000}}<br /> <br /> ==U==<br /> <br /> <br /> ==V==<br /> <br /> <br /> ==W==<br /> <br /> <br /> ==X==<br /> {{GameIndexEntry|title=X3 Reunion|page=X3 Reunion|developer=Egosoft|publisher=Deep Silver, Enlight|platforms=PC|year=2005}}<br /> <br /> ==Y==<br /> <br /> <br /> ==Z==<br /> <br /> ==Misc.==<br /> {{GameIndexEntry|title=Game History Format|page=Game History Format|developer=Use this for new games|publisher=AIGPG|platforms=All|year=2011}}</div>

Dave Mark http://gameai.com/wiki/index.php?title=Game_Index 2011-07-29T03:29:31Z

<p>Dave Mark: /* B */ Added Black &amp; White</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> This is a list of games that currently have ''history of AI'' pages:<br /> <br /> <br /> {{template:TOC}}<br /> <br /> <br /> <br /> ==0-9==<br /> <br /> <br /> ==A==<br /> <br /> <br /> ==B==<br /> {{GameIndexEntry|title=Buffy the Vampire Slayer|page=Buffy the Vampire Slayer|developer=The Collective|publisher=Fox Interactive|year=2002|platforms=Xbox}}<br /> {{GameIndexEntry|title=Black and White|page=Black &amp; White|developer=Lionhead|publisher=Electronic Arts|year=2001|platforms=PC, Mac}}<br /> <br /> ==C==<br /> <br /> <br /> ==D==<br /> <br /> <br /> ==E==<br /> <br /> <br /> ==F==<br /> <br /> <br /> ==G==<br /> <br /> <br /> ==H==<br /> {{GameIndexEntry|title=Halo 2|page=Halo 2|developer=Bungie|publisher=Microsoft Game Studios|year=2004|platforms=Xbox, PC}}<br /> {{GameIndexEntry|title=Halo 3|page=Halo 3|developer=Bungie|publisher=Microsoft Game Studios|year=2007|platforms=Xbox, PC}}<br /> {{GameIndexEntry|title=Halo: Reach|page=Halo: Reach|developer=Bungie|publisher=Microsoft Game Studios|year=2010|platforms=X360}}<br /> <br /> ==I==<br /> {{GameIndexEntry|title=Independence War 2: Edge of Chaos|page=Independence War 2|developer=Particle Systems Ltd.|publisher=Infogrames|year=2001|platforms=PC}}<br /> <br /> ==J==<br /> <br /> <br /> ==K==<br /> <br /> <br /> ==L==<br /> <br /> <br /> ==M==<br /> {{GameIndexEntry|title=Medal of Honor: Underground|page=Medal of Honor: Underground|developer=Dreamworks Interactive|publisher=Electronic Arts|year=2000|platforms=Xbox}}<br /> {{GameIndexEntry|title=Microsoft Baseball 3D|page=Microsoft Baseball 3D|developer=WizBang! Software Productions|publisher=Microsoft Game Studios|platforms=PC|year=1998}}<br /> <br /> ==N==<br /> {{GameIndexEntry|title=NBA Shootout 2003|page=NBA Shootout 2003|developer=989|publisher=Sony Computer Entertainment|year=2002|platforms=PS2}}<br /> {{GameIndexEntry|title=NBA '09: The Inside|page=NBA '09: The Inside|developer=SCE San Diego|publisher=Sony Computer Entertainment|year=2008|platforms=PS2, PS3}}<br /> <br /> <br /> ==O==<br /> <br /> <br /> ==P==<br /> {{GameIndexEntry|title=Pac-Man|page=Pac-Man|developer=Namco|publisher=Namco, Midway|platforms=Arcade|year=1980}}<br /> {{GameIndexEntry|title=Powerdrome|page=Powerdrome|developer=Argonaut Software|publisher=Mad Duck Productions|year=2004|platforms=PS2, Xbox, PC}}<br /> <br /> ==Q==<br /> <br /> <br /> ==R==<br /> {{GameIndexEntry|title=Rescue on Fractalus!|page=Rescue on Fractalus!|developer=Lucasfilm Games|publisher=Epyx, Atari, Activision|platforms=Amstrad CPC, Apple II, Atari 5200, Atari 8-bit, Commodore 64, Commodore 128, TRS-80 CoCo, ZX Spectrum|year=1984}}<br /> <br /> ==S==<br /> {{GameIndexEntry|title=SimCity|page=SimCity|developer=Maxis|publisher=Brøderbund|platforms=Amiga, Atari ST, C64, Macintosh, PC|year=1989}}<br /> <br /> ==T==<br /> {{GameIndexEntry|title=The Sims|page=The Sims|developer=Maxis|publisher=Electronic Arts|platforms=PC, Macintosh, PS2, Xbox, GameCube|year=2000}}<br /> <br /> ==U==<br /> <br /> <br /> ==V==<br /> <br /> <br /> ==W==<br /> <br /> <br /> ==X==<br /> {{GameIndexEntry|title=X3 Reunion|page=X3 Reunion|developer=Egosoft|publisher=Deep Silver, Enlight|platforms=PC|year=2005}}<br /> <br /> ==Y==<br /> <br /> <br /> ==Z==<br /> <br /> ==Misc.==<br /> {{GameIndexEntry|title=Game History Format|page=Game History Format|developer=Use this for new games|publisher=AIGPG|platforms=All|year=2011}}</div>

Dave Mark http://gameai.com/wiki/index.php?title=Black_and_White 2011-07-29T03:21:47Z

<p>Dave Mark: Initial creation for Richard</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> <br /> <br /> {{GameInfoBox<br /> |gametitle=Black &amp; White<br /> |imagefile=BlackAndWhite Cover.png<br /> |developer=Lionhead<br /> |publisher=Electronic Arts<br /> |year= 2001<br /> |platforms=Windows, Mac<br /> |genres=Sim<br /> |era=Tactical Planning<br /> }}<br /> <br /> (Insert a brief description of the game itself.)<br /> <br /> ==Description of AI Behavior==<br /> (What kinds of things was the AI supposed to do?)<br /> <br /> <br /> ===Notable Behaviors===<br /> (What really special things did the AI have to perform that made it stand out?)<br /> <br /> <br /> <br /> ==Architectures==<br /> <br /> ===Each Arch. Should Have a Heading Like This===<br /> &lt;!-- If you are filling this out based on first-hand knowledge<br /> fill out the AuthorStamp below. Else delete it. --&gt;<br /> {{AuthorStamp|name=Your Name|url=Your Name}}<br /> <br /> ===Another Architecture===<br /> <br /> <br /> <br /> ==Post-Mortem==<br /> <br /> ===What Worked===<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ===What Didn't Work===<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ===Lessons Learned===<br /> <br /> <br /> <br /> ==Reception by Public==<br /> (Was there positive or negative reception from the players and/or media?)<br /> <br /> <br /> <br /> ==References==<br /> ''Name of Source'', Author, Publication or Venue, 19--<br /> <br /> <br /> <br /> ==External Links==<br /> (ADD LATER)</div>

Dave Mark http://gameai.com/wiki/index.php?title=File:BlackAndWhite_Cover.png 2011-07-29T03:20:24Z

<p>Dave Mark: </p> <hr /> <div></div>

Dave Mark http://gameai.com/wiki/index.php?title=Sims_3 2011-07-29T03:16:39Z

<p>Dave Mark: Initial creation for Richard</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> <br /> <br /> {{GameInfoBox<br /> |gametitle=Sims 3<br /> |imagefile=Sims3.jpg<br /> |developer=Sims Studio<br /> |publisher=Electronic Arts<br /> |year= 2009<br /> |platforms=Windows, Mac OS X, iOS, webOS, Android, Symbian^3, Nintendo DS, Nintendo 3DS, Wii, PS3, X360<br /> |genres=Sim<br /> |era=Tactical Planning<br /> }}<br /> <br /> (Insert a brief description of the game itself.)<br /> <br /> ==Description of AI Behavior==<br /> (What kinds of things was the AI supposed to do?)<br /> <br /> <br /> ===Notable Behaviors===<br /> (What really special things did the AI have to perform that made it stand out?)<br /> <br /> <br /> <br /> ==Architectures==<br /> <br /> ===Each Arch. Should Have a Heading Like This===<br /> &lt;!-- If you are filling this out based on first-hand knowledge<br /> fill out the AuthorStamp below. Else delete it. --&gt;<br /> {{AuthorStamp|name=Your Name|url=Your Name}}<br /> <br /> ===Another Architecture===<br /> <br /> <br /> <br /> ==Post-Mortem==<br /> <br /> ===What Worked===<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ===What Didn't Work===<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ===Lessons Learned===<br /> <br /> <br /> <br /> ==Reception by Public==<br /> (Was there positive or negative reception from the players and/or media?)<br /> <br /> <br /> <br /> ==References==<br /> ''Name of Source'', Author, Publication or Venue, 19--<br /> <br /> <br /> <br /> ==External Links==<br /> (ADD LATER)</div>

Dave Mark http://gameai.com/wiki/index.php?title=File:Sims3.jpg 2011-07-29T03:15:51Z

<p>Dave Mark: </p> <hr /> <div></div>

Dave Mark http://gameai.com/wiki/index.php?title=Game_Index 2011-07-25T02:39:24Z

<p>Dave Mark: Added NBA titles</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> This is a list of games that currently have ''history of AI'' pages:<br /> <br /> <br /> {{template:TOC}}<br /> <br /> <br /> <br /> ==0-9==<br /> <br /> <br /> ==A==<br /> <br /> <br /> ==B==<br /> {{GameIndexEntry|title=Buffy the Vampire Slayer|page=Buffy the Vampire Slayer|developer=The Collective|publisher=Fox Interactive|year=2002|platforms=Xbox}}<br /> <br /> ==C==<br /> <br /> <br /> ==D==<br /> <br /> <br /> ==E==<br /> <br /> <br /> ==F==<br /> <br /> <br /> ==G==<br /> <br /> <br /> ==H==<br /> {{GameIndexEntry|title=Halo 2|page=Halo 2|developer=Bungie|publisher=Microsoft Game Studios|year=2004|platforms=Xbox, PC}}<br /> {{GameIndexEntry|title=Halo 3|page=Halo 3|developer=Bungie|publisher=Microsoft Game Studios|year=2007|platforms=Xbox, PC}}<br /> {{GameIndexEntry|title=Halo: Reach|page=Halo: Reach|developer=Bungie|publisher=Microsoft Game Studios|year=2010|platforms=X360}}<br /> <br /> ==I==<br /> {{GameIndexEntry|title=Independence War 2: Edge of Chaos|page=Independence War 2|developer=Particle Systems Ltd.|publisher=Infogrames|year=2001|platforms=PC}}<br /> <br /> ==J==<br /> <br /> <br /> ==K==<br /> <br /> <br /> ==L==<br /> <br /> <br /> ==M==<br /> {{GameIndexEntry|title=Medal of Honor: Underground|page=Medal of Honor: Underground|developer=Dreamworks Interactive|publisher=Electronic Arts|year=2000|platforms=Xbox}}<br /> {{GameIndexEntry|title=Microsoft Baseball 3D|page=Microsoft Baseball 3D|developer=WizBang! Software Productions|publisher=Microsoft Game Studios|platforms=PC|year=1998}}<br /> <br /> ==N==<br /> {{GameIndexEntry|title=NBA Shootout 2003|page=NBA Shootout 2003|developer=989|publisher=Sony Computer Entertainment|year=2002|platforms=PS2}}<br /> {{GameIndexEntry|title=NBA '09: The Inside|page=NBA '09: The Inside|developer=SCE San Diego|publisher=Sony Computer Entertainment|year=2008|platforms=PS2, PS3}}<br /> <br /> <br /> ==O==<br /> <br /> <br /> ==P==<br /> {{GameIndexEntry|title=Pac-Man|page=Pac-Man|developer=Namco|publisher=Namco, Midway|platforms=Arcade|year=1980}}<br /> {{GameIndexEntry|title=Powerdrome|page=Powerdrome|developer=Argonaut Software|publisher=Mad Duck Productions|year=2004|platforms=PS2, Xbox, PC}}<br /> <br /> ==Q==<br /> <br /> <br /> ==R==<br /> {{GameIndexEntry|title=Rescue on Fractalus!|page=Rescue on Fractalus!|developer=Lucasfilm Games|publisher=Epyx, Atari, Activision|platforms=Amstrad CPC, Apple II, Atari 5200, Atari 8-bit, Commodore 64, Commodore 128, TRS-80 CoCo, ZX Spectrum|year=1984}}<br /> <br /> ==S==<br /> {{GameIndexEntry|title=SimCity|page=SimCity|developer=Maxis|publisher=Brøderbund|platforms=Amiga, Atari ST, C64, Macintosh, PC|year=1989}}<br /> <br /> ==T==<br /> {{GameIndexEntry|title=The Sims|page=The Sims|developer=Maxis|publisher=Electronic Arts|platforms=PC, Macintosh, PS2, Xbox, GameCube|year=2000}}<br /> <br /> ==U==<br /> <br /> <br /> ==V==<br /> <br /> <br /> ==W==<br /> <br /> <br /> ==X==<br /> {{GameIndexEntry|title=X3 Reunion|page=X3 Reunion|developer=Egosoft|publisher=Deep Silver, Enlight|platforms=PC|year=2005}}<br /> <br /> ==Y==<br /> <br /> <br /> ==Z==<br /> <br /> ==Misc.==<br /> {{GameIndexEntry|title=Game History Format|page=Game History Format|developer=Use this for new games|publisher=AIGPG|platforms=All|year=2011}}</div>

Dave Mark http://gameai.com/wiki/index.php?title=NBA_%2709:_The_Inside 2011-07-25T02:36:49Z

<p>Dave Mark: Initial creation for Brian</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> <br /> <br /> {{GameInfoBox<br /> |gametitle=NBA '09: The Inside<br /> |imagefile=NBA09TheInside.jpg<br /> |developer=SCE San Diego<br /> |publisher=Sony Computer Entertainment<br /> |year= 2008<br /> |platforms=PS2, PS3<br /> |genres=Sports<br /> |era=Strategic<br /> }}<br /> <br /> (Insert a brief description of the game itself.)<br /> <br /> ==Description of AI Behavior==<br /> (What kinds of things was the AI supposed to do?)<br /> <br /> <br /> ===Notable Behaviors===<br /> (What really special things did the AI have to perform that made it stand out?)<br /> <br /> <br /> <br /> ==Architectures==<br /> <br /> ===Each Arch. Should Have a Heading Like This===<br /> &lt;!-- If you are filling this out based on first-hand knowledge<br /> fill out the AuthorStamp below. Else delete it. --&gt;<br /> {{AuthorStamp|name=Your Name|url=Your Name}}<br /> <br /> ===Another Architecture===<br /> <br /> <br /> <br /> ==Post-Mortem==<br /> <br /> ===What Worked===<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ===What Didn't Work===<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ===Lessons Learned===<br /> <br /> <br /> <br /> ==Reception by Public==<br /> (Was there positive or negative reception from the players and/or media?)<br /> <br /> <br /> <br /> ==References==<br /> ''Name of Source'', Author, Publication or Venue, 19--<br /> <br /> <br /> <br /> ==External Links==<br /> (ADD LATER)</div>

Dave Mark http://gameai.com/wiki/index.php?title=File:NBA09TheInside.jpg 2011-07-25T02:35:44Z

<p>Dave Mark: </p> <hr /> <div></div>

Dave Mark http://gameai.com/wiki/index.php?title=Independence_War_2:_Edge_of_Chaos 2011-07-25T02:33:24Z

<p>Dave Mark: added era</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> <br /> <br /> {{GameInfoBox<br /> |gametitle=Independence War 2: Edge of Chaos<br /> |imagefile=IndependenceWar2Box.jpg<br /> |developer=Particle Systems Ltd.<br /> |publisher=Infogrames<br /> |year= 2001<br /> |platforms=PC<br /> |genres=Space Combat Sim.<br /> |era=Tactical Reasoning<br /> }}<br /> <br /> [http://en.wikipedia.org/wiki/Independence_War_2:_Edge_of_Chaos Independence War 2: Edge of Chaos] is a space combat simulation game in the style of the game &quot;Elite&quot;. Players pilot their upgradable spacecraft around the galaxy for trade, piracy, special missions, and, when necessary, combat.<br /> <br /> ==Description of AI Behavior==<br /> (What kinds of things was the AI supposed to do?)<br /> <br /> <br /> ===Notable Behaviors===<br /> (What really special things did the AI have to perform that made it stand out?)<br /> <br /> <br /> <br /> ==Architectures==<br /> <br /> ===Naviagation===<br /> &lt;!-- If you are filling this out based on first-hand knowledge<br /> fill out the AuthorStamp below. Else delete it. --&gt;<br /> {{AuthorStamp|name=Your Name|url=Your Name}}<br /> <br /> ===Another Architecture===<br /> <br /> <br /> <br /> ==Post-Mortem==<br /> <br /> ===What Worked===<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ===What Didn't Work===<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ===Lessons Learned===<br /> <br /> <br /> <br /> ==Reception by Public==<br /> (Was there positive or negative reception from the players and/or media?)<br /> <br /> <br /> <br /> ==References==<br /> {{reflist|sourcename=|title=|venue=|year=|url=}}<br /> <br /> <br /> <br /> ==External Links==<br /> (ADD LATER)</div>

Dave Mark http://gameai.com/wiki/index.php?title=Template:GameInfoBox 2011-07-25T02:32:14Z

<p>Dave Mark: </p> <hr /> <div>{| class=&quot;infobox&quot; <br /> |-<br /> ! colspan=&quot;2&quot; scope=&quot;col&quot; |'''{{{gametitle}}}'''<br /> |-<br /> ! colspan=&quot;2&quot; | [[File:{{{imagefile}}}|250px]]<br /> |-<br /> | width=&quot;80px&quot; |'''Developer:''' ||{{{developer}}}<br /> |-<br /> |'''Publisher:''' ||{{{publisher}}}<br /> |-<br /> |'''Year:''' ||{{{year}}}<br /> |-<br /> |'''Platforms:''' ||{{{platforms}}}<br /> |-<br /> |'''Genre:''' ||{{{genres}}}<br /> |-<br /> |'''[[Game AI Eras|AI Era]]:''' ||[[Game AI Eras#{{{era}}}|{{{era}}}]]<br /> |}</div>

Dave Mark http://gameai.com/wiki/index.php?title=Template:GameInfoBox 2011-07-25T02:31:13Z

<p>Dave Mark: </p> <hr /> <div>{| class=&quot;infobox&quot; <br /> |-<br /> ! colspan=&quot;2&quot; scope=&quot;col&quot; |'''{{{gametitle}}}'''<br /> |-<br /> ! colspan=&quot;2&quot; | [[File:{{{imagefile}}}|width=250]]<br /> |-<br /> | width=&quot;80px&quot; |'''Developer:''' ||{{{developer}}}<br /> |-<br /> |'''Publisher:''' ||{{{publisher}}}<br /> |-<br /> |'''Year:''' ||{{{year}}}<br /> |-<br /> |'''Platforms:''' ||{{{platforms}}}<br /> |-<br /> |'''Genre:''' ||{{{genres}}}<br /> |-<br /> |'''[[Game AI Eras|AI Era]]:''' ||[[Game AI Eras#{{{era}}}|{{{era}}}]]<br /> |}</div>

Dave Mark http://gameai.com/wiki/index.php?title=NBA_Shootout_2003 2011-07-25T02:29:38Z

<p>Dave Mark: Initial creation for Brian</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> <br /> <br /> {{GameInfoBox<br /> |gametitle=NBA Shootout 2003<br /> |imagefile=NBAShootout2003.jpg<br /> |developer=989 Studios<br /> |publisher=Sony Computer Entertainment<br /> |year= 2002<br /> |platforms=PS2<br /> |genres=Sports<br /> |era=Strategic<br /> }}<br /> <br /> (Insert a brief description of the game itself.)<br /> <br /> ==Description of AI Behavior==<br /> (What kinds of things was the AI supposed to do?)<br /> <br /> <br /> ===Notable Behaviors===<br /> (What really special things did the AI have to perform that made it stand out?)<br /> <br /> <br /> <br /> ==Architectures==<br /> <br /> ===Each Arch. Should Have a Heading Like This===<br /> &lt;!-- If you are filling this out based on first-hand knowledge<br /> fill out the AuthorStamp below. Else delete it. --&gt;<br /> {{AuthorStamp|name=Your Name|url=Your Name}}<br /> <br /> ===Another Architecture===<br /> <br /> <br /> <br /> ==Post-Mortem==<br /> <br /> ===What Worked===<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ===What Didn't Work===<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ===Lessons Learned===<br /> <br /> <br /> <br /> ==Reception by Public==<br /> (Was there positive or negative reception from the players and/or media?)<br /> <br /> <br /> <br /> ==References==<br /> ''Name of Source'', Author, Publication or Venue, 19--<br /> <br /> <br /> <br /> ==External Links==<br /> (ADD LATER)</div>

Dave Mark http://gameai.com/wiki/index.php?title=File:NBAShootout2003.jpg 2011-07-25T02:27:44Z

<p>Dave Mark: </p> <hr /> <div></div>

Dave Mark http://gameai.com/wiki/index.php?title=Halo:_Reach 2011-07-24T20:17:58Z

<p>Dave Mark: Initial creation</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> <br /> <br /> {{GameInfoBox<br /> |gametitle=Halo Reach<br /> |imagefile=Halo-_Reach_box_art.png<br /> |developer=Bungie<br /> |publisher=Microsoft Game Studios<br /> |year= 2010<br /> |platforms=X360<br /> |genres=FPS<br /> |era=Tactical Reasoning<br /> }}<br /> <br /> [http://en.wikipedia.org/wiki/Halo_reach Halo: Reach] is a first-person shooter game that was a prequel to the events of the Halo series. It takes the player on a series of missions that engage in combat against various forms of alien life, often in a squad-based environment.<br /> <br /> ==Description of AI Behavior==<br /> (What kinds of things was the AI supposed to do?)<br /> <br /> <br /> ===Notable Behaviors===<br /> (What really special things did the AI have to perform that made it stand out?)<br /> <br /> <br /> <br /> ==Architectures==<br /> <br /> ===Each Arch. Should Have a Heading Like This===<br /> &lt;!-- If you are filling this out based on first-hand knowledge<br /> fill out the AuthorStamp below. Else delete it. --&gt;<br /> {{AuthorStamp|name=Your Name|url=Your Name}}<br /> <br /> ===Another Architecture===<br /> <br /> <br /> <br /> ==Post-Mortem==<br /> <br /> ===What Worked===<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ===What Didn't Work===<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ===Lessons Learned===<br /> <br /> <br /> <br /> ==Reception by Public==<br /> (Was there positive or negative reception from the players and/or media?)<br /> <br /> <br /> <br /> ==References==<br /> <br /> <br /> <br /> <br /> ==External Links==<br /> (ADD LATER)</div>

Dave Mark http://gameai.com/wiki/index.php?title=File:Halo-_Reach_box_art.png 2011-07-24T20:16:10Z

<p>Dave Mark: </p> <hr /> <div></div>

Dave Mark http://gameai.com/wiki/index.php?title=Game_Index 2011-07-24T20:11:35Z

<p>Dave Mark: /* H */ added Reach</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> This is a list of games that currently have ''history of AI'' pages:<br /> <br /> <br /> {{template:TOC}}<br /> <br /> <br /> <br /> ==0-9==<br /> <br /> <br /> ==A==<br /> <br /> <br /> ==B==<br /> {{GameIndexEntry|title=Buffy the Vampire Slayer|page=Buffy the Vampire Slayer|developer=The Collective|publisher=Fox Interactive|year=2002|platforms=Xbox}}<br /> <br /> ==C==<br /> <br /> <br /> ==D==<br /> <br /> <br /> ==E==<br /> <br /> <br /> ==F==<br /> <br /> <br /> ==G==<br /> <br /> <br /> ==H==<br /> {{GameIndexEntry|title=Halo 2|page=Halo 2|developer=Bungie|publisher=Microsoft Game Studios|year=2004|platforms=Xbox, PC}}<br /> {{GameIndexEntry|title=Halo 3|page=Halo 3|developer=Bungie|publisher=Microsoft Game Studios|year=2007|platforms=Xbox, PC}}<br /> {{GameIndexEntry|title=Halo: Reach|page=Halo: Reach|developer=Bungie|publisher=Microsoft Game Studios|year=2010|platforms=X360}}<br /> <br /> ==I==<br /> {{GameIndexEntry|title=Independence War 2: Edge of Chaos|page=Independence War 2|developer=Particle Systems Ltd.|publisher=Infogrames|year=2001|platforms=PC}}<br /> <br /> ==J==<br /> <br /> <br /> ==K==<br /> <br /> <br /> ==L==<br /> <br /> <br /> ==M==<br /> {{GameIndexEntry|title=Medal of Honor: Underground|page=Medal of Honor: Underground|developer=Dreamworks Interactive|publisher=Electronic Arts|year=2000|platforms=Xbox}}<br /> {{GameIndexEntry|title=Microsoft Baseball 3D|page=Microsoft Baseball 3D|developer=WizBang! Software Productions|publisher=Microsoft Game Studios|platforms=PC|year=1998}}<br /> <br /> ==N==<br /> <br /> <br /> ==O==<br /> <br /> <br /> ==P==<br /> {{GameIndexEntry|title=Pac-Man|page=Pac-Man|developer=Namco|publisher=Namco, Midway|platforms=Arcade|year=1980}}<br /> {{GameIndexEntry|title=Powerdrome|page=Powerdrome|developer=Argonaut Software|publisher=Mad Duck Productions|year=2004|platforms=PS2, Xbox, PC}}<br /> <br /> ==Q==<br /> <br /> <br /> ==R==<br /> <br /> <br /> ==S==<br /> {{GameIndexEntry|title=SimCity|page=SimCity|developer=Maxis|publisher=Brøderbund|platforms=Amiga, Atari ST, C64, Macintosh, PC|year=1989}}<br /> <br /> ==T==<br /> {{GameIndexEntry|title=The Sims|page=The Sims|developer=Maxis|publisher=Electronic Arts|platforms=PC, Macintosh, PS2, Xbox, GameCube|year=2000}}<br /> <br /> ==U==<br /> <br /> <br /> ==V==<br /> <br /> <br /> ==W==<br /> <br /> <br /> ==X==<br /> {{GameIndexEntry|title=X3 Reunion|page=X3 Reunion|developer=Egosoft|publisher=Deep Silver, Enlight|platforms=PC|year=2005}}<br /> <br /> ==Y==<br /> <br /> <br /> ==Z==<br /> <br /> ==Misc.==<br /> {{GameIndexEntry|title=Game History Format|page=Game History Format|developer=Use this for new games|publisher=AIGPG|platforms=All|year=2011}}</div>

Dave Mark http://gameai.com/wiki/index.php?title=Game_Index 2011-07-24T20:04:15Z

<p>Dave Mark: Added Buffy and MoH:U</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> This is a list of games that currently have ''history of AI'' pages:<br /> <br /> <br /> {{template:TOC}}<br /> <br /> <br /> <br /> ==0-9==<br /> <br /> <br /> ==A==<br /> <br /> <br /> ==B==<br /> {{GameIndexEntry|title=Buffy the Vampire Slayer|page=Buffy the Vampire Slayer|developer=The Collective|publisher=Fox Interactive|year=2002|platforms=Xbox}}<br /> <br /> ==C==<br /> <br /> <br /> ==D==<br /> <br /> <br /> ==E==<br /> <br /> <br /> ==F==<br /> <br /> <br /> ==G==<br /> <br /> <br /> ==H==<br /> {{GameIndexEntry|title=Halo 2|page=Halo 2|developer=Bungie|publisher=Microsoft Game Studios|year=2004|platforms=Xbox, PC}}<br /> {{GameIndexEntry|title=Halo 3|page=Halo 3|developer=Bungie|publisher=Microsoft Game Studios|year=2007|platforms=Xbox, PC}}<br /> ==I==<br /> {{GameIndexEntry|title=Independence War 2: Edge of Chaos|page=Independence War 2|developer=Particle Systems Ltd.|publisher=Infogrames|year=2001|platforms=PC}}<br /> <br /> ==J==<br /> <br /> <br /> ==K==<br /> <br /> <br /> ==L==<br /> <br /> <br /> ==M==<br /> {{GameIndexEntry|title=Medal of Honor: Underground|page=Medal of Honor: Underground|developer=Dreamworks Interactive|publisher=Electronic Arts|year=2000|platforms=Xbox}}<br /> {{GameIndexEntry|title=Microsoft Baseball 3D|page=Microsoft Baseball 3D|developer=WizBang! Software Productions|publisher=Microsoft Game Studios|platforms=PC|year=1998}}<br /> <br /> ==N==<br /> <br /> <br /> ==O==<br /> <br /> <br /> ==P==<br /> {{GameIndexEntry|title=Pac-Man|page=Pac-Man|developer=Namco|publisher=Namco, Midway|platforms=Arcade|year=1980}}<br /> {{GameIndexEntry|title=Powerdrome|page=Powerdrome|developer=Argonaut Software|publisher=Mad Duck Productions|year=2004|platforms=PS2, Xbox, PC}}<br /> <br /> ==Q==<br /> <br /> <br /> ==R==<br /> <br /> <br /> ==S==<br /> {{GameIndexEntry|title=SimCity|page=SimCity|developer=Maxis|publisher=Brøderbund|platforms=Amiga, Atari ST, C64, Macintosh, PC|year=1989}}<br /> <br /> ==T==<br /> {{GameIndexEntry|title=The Sims|page=The Sims|developer=Maxis|publisher=Electronic Arts|platforms=PC, Macintosh, PS2, Xbox, GameCube|year=2000}}<br /> <br /> ==U==<br /> <br /> <br /> ==V==<br /> <br /> <br /> ==W==<br /> <br /> <br /> ==X==<br /> {{GameIndexEntry|title=X3 Reunion|page=X3 Reunion|developer=Egosoft|publisher=Deep Silver, Enlight|platforms=PC|year=2005}}<br /> <br /> ==Y==<br /> <br /> <br /> ==Z==<br /> <br /> ==Misc.==<br /> {{GameIndexEntry|title=Game History Format|page=Game History Format|developer=Use this for new games|publisher=AIGPG|platforms=All|year=2011}}</div>

Dave Mark http://gameai.com/wiki/index.php?title=Buffy_the_Vampire_Slayer 2011-07-24T20:00:11Z

<p>Dave Mark: Initial creation for Brian</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> <br /> <br /> {{GameInfoBox<br /> |gametitle=Buffy the Vampire Slayer<br /> |imagefile=Buffy_the_Vampire_Slayer_Coverart.png<br /> |developer=The Collective<br /> |publisher=Fox Interactive<br /> |year=2002<br /> |platforms=Xbox<br /> |genres=Action Brawler<br /> |era=Tactical Reasoning<br /> }}<br /> <br /> (Insert a brief description of the game itself.)<br /> <br /> ==Description of AI Behavior==<br /> (What kinds of things was the AI supposed to do?)<br /> <br /> <br /> ===Notable Behaviors===<br /> (What really special things did the AI have to perform that made it stand out?)<br /> <br /> <br /> <br /> ==Architectures==<br /> <br /> ===Each Arch. Should Have a Heading Like This===<br /> &lt;!-- If you are filling this out based on first-hand knowledge<br /> fill out the AuthorStamp below. Else delete it. --&gt;<br /> {{AuthorStamp|name=Your Name|url=Your Name}}<br /> <br /> ===Another Architecture===<br /> <br /> <br /> <br /> ==Post-Mortem==<br /> <br /> ===What Worked===<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ===What Didn't Work===<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ===Lessons Learned===<br /> <br /> <br /> <br /> ==Reception by Public==<br /> (Was there positive or negative reception from the players and/or media?)<br /> <br /> <br /> <br /> ==References==<br /> ''Name of Source'', Author, Publication or Venue, 19--<br /> <br /> <br /> <br /> ==External Links==<br /> (ADD LATER)</div>

Dave Mark http://gameai.com/wiki/index.php?title=File:Buffy_the_Vampire_Slayer_Coverart.png 2011-07-24T19:56:12Z

<p>Dave Mark: </p> <hr /> <div></div>

Dave Mark http://gameai.com/wiki/index.php?title=Medal_of_Honor:_Underground 2011-07-24T19:50:30Z

<p>Dave Mark: Initial creation for Brian</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> <br /> <br /> {{GameInfoBox<br /> |gametitle=Medal of Honor: Underground<br /> |imagefile=Medal_of_Honor_-_Underground_Coverart.png<br /> |developer=Dreamworks Interactive<br /> |publisher=Electronic Arts<br /> |year=2000<br /> |platforms=PSX<br /> |genres=FPS<br /> |era=Tactical Reasoning<br /> }}<br /> <br /> ''[http://en.wikipedia.org/wiki/Medal_of_Honor:_Underground Medal of Honor: Underground]'' is a videogame that is the prequel to the World War II hit ''Medal of Honor''. In ''Underground'', the player takes the role of Manon Batiste (Based on Helene Deschamps Adams), a French woman who appeared in the first game as an adviser. <br /> <br /> ==Description of AI Behavior==<br /> (What kinds of things was the AI supposed to do?)<br /> <br /> <br /> ===Notable Behaviors===<br /> (What really special things did the AI have to perform that made it stand out?)<br /> <br /> <br /> <br /> ==Architectures==<br /> <br /> ===Each Arch. Should Have a Heading Like This===<br /> &lt;!-- If you are filling this out based on first-hand knowledge<br /> fill out the AuthorStamp below. Else delete it. --&gt;<br /> {{AuthorStamp|name=Your Name|url=Your Name}}<br /> <br /> ===Another Architecture===<br /> <br /> <br /> <br /> ==Post-Mortem==<br /> <br /> ===What Worked===<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ===What Didn't Work===<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ===Lessons Learned===<br /> <br /> <br /> <br /> ==Reception by Public==<br /> (Was there positive or negative reception from the players and/or media?)<br /> <br /> <br /> <br /> ==References==<br /> ''Name of Source'', Author, Publication or Venue, 19--<br /> <br /> <br /> <br /> ==External Links==<br /> (ADD LATER)</div>

Dave Mark http://gameai.com/wiki/index.php?title=File:Medal_of_Honor_-_Underground_Coverart.png 2011-07-24T19:45:59Z

<p>Dave Mark: </p> <hr /> <div></div>

Dave Mark http://gameai.com/wiki/index.php?title=Powerdrome 2011-07-23T17:41:08Z

<p>Dave Mark: /* Multi-tier planning architecture through virtual yoke */ formatted the list of behaviors</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> <br /> <br /> {{GameInfoBox<br /> |gametitle=Powerdrom<br /> |imagefile=PowerdromeBox.jpg<br /> |developer=Argonaut Software<br /> |publisher=Mad Duck Productions<br /> |year= 2004<br /> |platforms=PS2, XBox, PC<br /> |genres=Racing<br /> |era=Tactical Reasoning<br /> }}<br /> <br /> Powerdrome is a futuristic racing game where players race jet-engined, anti-gravity bikes called 'blades' around closed tracks.<br /> <br /> ==Description of AI Behavior==<br /> Being a pure racing simulation, the A.I. attempted to provide a competative race on a multitude of tracks often with multiple routes. It tried to do this reflecting the personality of each of the relevant characters <br /> <br /> ===Notable Behaviors===<br /> Notable behaviours including some degree of gesturing based on personality and move execution.<br /> <br /> ==Architectures==<br /> ===Player assisted learning===<br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}Various people in the company drove a number of laps around various tracks recording telemetry. The best were chosen primarily to provide appropriate attack velocities and lines for things like corners. A combination of the multiple routes were driven.<br /> <br /> For A.I. training, the single player time trial mode was used. The A.I. continually aimed to beat the best time, driving the best line as closely as possible and dropping telemetry as it went. If it set a new time, this became that which it tried to achieved. The natural curvature of the improved driving line therefore started to reflect what the A.I., for that particular blade, could drive inside it's own heuristics.<br /> <br /> ===Multi-tier planning architecture through virtual yoke===<br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}Divided into a number of feed forward sections: a line following layer, a personality layer, the A.I. passed signals down through a stack based virtual yoke. This generated (predominantly) gas and steering signals similar to the player.<br /> <br /> Noted here is the personality layer which was based on blades around it&amp;mdash;and the relationship to those blades&amp;mdash;could chose to affect the signals of the line following layer with extra steering: <br /> * Towards blade as it came level =&gt; side ram (aggressive)<br /> * -ve ram =&gt; getting out of the way (friendly)<br /> * Sidewards bias with a blade in front =&gt; (overtaking)<br /> * Overdriven acceleration to a blade in front =&gt; forward ram (aggressive)<br /> * Artificially deceleration to a blade behind =&gt; blocking (aggressive).<br /> <br /> The use of boost was also intended to be plugged into personality with the idea that some characters would just like to get ahead, rather than be conservative.<br /> <br /> ===Inverse kinematics===<br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}The A.I. attempts to accelerate/decelerate to acquire the given best line speed * some slightly increased scaler. It tries to acquire the speed at the next time step, clamped by an acceptable acceleration [worked out by engine max F/m]. Because they fly under the same mechanics as the player, this usually means the players speed is reasonably attainable. By using a scaler to slightly increase target values so that it is never quite, a smoothed continuous signal is obtained.<br /> <br /> Steering was originally based on a fan approach generated off line for each blade. Various degrees of steer were recorded under different conditions, the physics being integrated over a set time window to work out the relative translation from forward direction, expected in the future. This would form part of an ''n''-directional table where various key factors, side slip, speed bracket were weighted into the equation. <br /> <br /> As the data grew, the effort was somewhat scaled back to just be hard left and hard right steering. Then a given run time state of blade, would provide the relevant hard left, hard right table entry and linear interpolation from -1 being the left most point to +1 being the right determined the best steering value.<br /> <br /> ===Obstacle avoidance===<br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}The OOBB of known obstacles were translated into 2D (horizontal occupation + distance) track space and this used to affect steering values. By mini-maxing the horizontal occupation, obstacle clusters could be avoided [Laming, AI Wisdom 2]<br /> <br /> ==Post-Mortem==<br /> <br /> ===What Worked===<br /> <br /> ====Player assisted learning====<br /> <br /> Really allowed some nice player quirks to come out, tempered by an A.I. that then refined your lap.<br /> <br /> ====Gesturing in replays====<br /> <br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}Although gestures were partly driven by race time, by the personality layer determining a move, most of it was actually a cheat - added instead during replay. Depending on the replay telemetry, we increased the number of gestures at key times (after collisions - accidental or not), on entering 1st place etc.. and provided the rules were reasonable it looked like they all had more personality than they really did<br /> <br /> ====Debugging====<br /> <br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}Graphical debugging of avoidance, track and steering feathers. The ability to pause the simulation (but not camera) and look around. [Laming, AI Wisdom 2]<br /> <br /> ===What Didn't Work===<br /> <br /> ====Steering by table====<br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}Fitting steering curves by a multidimensional table of dependent variable brackets. Reallistically there were too many parameters and we were relying on instinct to tell us which ones to base things on. The table quickly went n-dimensional. These days, you'd alter at runtime using a PID controller<br /> <br /> ====Imparting personality at 1200km/h====<br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}Trying to co-ordinate aggressive movements at speeds approaching 1200km/h is difficult. Often rams or swipes would miss, or at most be ineffectual. <br /> <br /> ====Artistically fitted tracks vs physical speed====<br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}The artists treated both track and blade as a traditional racing circuit. But when you're flying a tonne of metal without friction at 1200km/h, bends need a huge track width. Because both player and A.I. often couldn't make them, the side force field profile needed to be ridiculously ramped up - taking away some of the skill<br /> <br /> ===Lessons Learned===<br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}Having a realistic race, isn't necessary the best race. We probably should have used light rubber bandedness to keep blades together more.<br /> <br /> ==Reception by Public==<br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}The game received mixed reviews and a 69% Metacritic. To our knowledge the A.I. was never accused of being too stupid or obviously cheating, passing the A.I. was just there test.<br /> <br /> ==References==<br /> A.I. Wisdom 2 - todo.<br /> <br /> <br /> <br /> ==External Links==</div>

Dave Mark http://gameai.com/wiki/index.php?title=Powerdrome 2011-07-22T00:49:50Z

<p>Dave Mark: Fixed author stamps</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> <br /> <br /> {{GameInfoBox<br /> |gametitle=Powerdrom<br /> |imagefile=PowerdromeBox.jpg<br /> |developer=Argonaut Software<br /> |publisher=Mad Duck Productions<br /> |year= 2004<br /> |platforms=PS2, XBox, PC<br /> |genres=Racing<br /> |era=Tactical Reasoning<br /> }}<br /> <br /> Powerdrome is a futuristic racing game where players race jet-engined, anti-gravity bikes called 'blades' around closed tracks.<br /> <br /> ==Description of AI Behavior==<br /> Being a pure racing simulation, the A.I. attempted to provide a competative race on a multitude of tracks often with multiple routes. It tried to do this reflecting the personality of each of the relevant characters <br /> <br /> ===Notable Behaviors===<br /> Notable behaviours including some degree of gesturing based on personality and move execution.<br /> <br /> ==Architectures==<br /> ===Player assisted learning===<br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}Various people in the company drove a number of laps around various tracks recording telemetry. The best were chosen primarily to provide appropriate attack velocities and lines for things like corners. A combination of the multiple routes were driven.<br /> <br /> For A.I. training, the single player time trial mode was used. The A.I. continually aimed to beat the best time, driving the best line as closely as possible and dropping telemetry as it went. If it set a new time, this became that which it tried to achieved. The natural curvature of the improved driving line therefore started to reflect what the A.I., for that particular blade, could drive inside it's own heuristics.<br /> <br /> ===Multi-tier planning architecture through virtual yoke===<br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}Divided into a number of feed forward sections: a line following layer, a personality layer, the A.I. passed signals down through a stack based virtual yoke. This generated (predominantly) gas and steering signals similar to the player.<br /> <br /> Noted here is the personality layer, which based on blades around it - and the relationship to those blades - could chose to affect the signals of the line following layer with extra steering - towards blade as it came level =&gt; side ram (aggressive), -ve ram =&gt; getting out of the way (friendly), sidewards bias with a blade in front =&gt; (overtaking), overdriven acceleration to a blade in front =&gt; forward ram (aggressive), artificially deceleration to a blade behind =&gt; blocking (aggressive).<br /> <br /> The use of boost was also intended to be plugged into personality with the idea that some characters would just like to get ahead, rather than be conservative.<br /> <br /> ===Inverse kinematics===<br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}The A.I. attempts to accelerate/decelerate to acquire the given best line speed * some slightly increased scaler. It tries to acquire the speed at the next time step, clamped by an acceptable acceleration [worked out by engine max F/m]. Because they fly under the same mechanics as the player, this usually means the players speed is reasonably attainable. By using a scaler to slightly increase target values so that it is never quite, a smoothed continuous signal is obtained.<br /> <br /> Steering was originally based on a fan approach generated off line for each blade. Various degrees of steer were recorded under different conditions, the physics being integrated over a set time window to work out the relative translation from forward direction, expected in the future. This would form part of an ''n''-directional table where various key factors, side slip, speed bracket were weighted into the equation. <br /> <br /> As the data grew, the effort was somewhat scaled back to just be hard left and hard right steering. Then a given run time state of blade, would provide the relevant hard left, hard right table entry and linear interpolation from -1 being the left most point to +1 being the right determined the best steering value.<br /> <br /> ===Obstacle avoidance===<br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}The OOBB of known obstacles were translated into 2D (horizontal occupation + distance) track space and this used to affect steering values. By mini-maxing the horizontal occupation, obstacle clusters could be avoided [Laming, AI Wisdom 2]<br /> <br /> ==Post-Mortem==<br /> <br /> ===What Worked===<br /> <br /> ====Player assisted learning====<br /> <br /> Really allowed some nice player quirks to come out, tempered by an A.I. that then refined your lap.<br /> <br /> ====Gesturing in replays====<br /> <br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}Although gestures were partly driven by race time, by the personality layer determining a move, most of it was actually a cheat - added instead during replay. Depending on the replay telemetry, we increased the number of gestures at key times (after collisions - accidental or not), on entering 1st place etc.. and provided the rules were reasonable it looked like they all had more personality than they really did<br /> <br /> ====Debugging====<br /> <br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}Graphical debugging of avoidance, track and steering feathers. The ability to pause the simulation (but not camera) and look around. [Laming, AI Wisdom 2]<br /> <br /> ===What Didn't Work===<br /> <br /> ====Steering by table====<br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}Fitting steering curves by a multidimensional table of dependent variable brackets. Reallistically there were too many parameters and we were relying on instinct to tell us which ones to base things on. The table quickly went n-dimensional. These days, you'd alter at runtime using a PID controller<br /> <br /> ====Imparting personality at 1200km/h====<br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}Trying to co-ordinate aggressive movements at speeds approaching 1200km/h is difficult. Often rams or swipes would miss, or at most be ineffectual. <br /> <br /> ====Artistically fitted tracks vs physical speed====<br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}The artists treated both track and blade as a traditional racing circuit. But when you're flying a tonne of metal without friction at 1200km/h, bends need a huge track width. Because both player and A.I. often couldn't make them, the side force field profile needed to be ridiculously ramped up - taking away some of the skill<br /> <br /> ===Lessons Learned===<br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}Having a realistic race, isn't necessary the best race. We probably should have used light rubber bandedness to keep blades together more.<br /> <br /> ==Reception by Public==<br /> {{AuthorStamp|name=Brett Laming|url=http://www.linkedin.com/in/brettlaming}}The game received mixed reviews and a 69% Metacritic. To our knowledge the A.I. was never accused of being too stupid or obviously cheating, passing the A.I. was just there test.<br /> <br /> ==References==<br /> A.I. Wisdom 2 - todo.<br /> <br /> <br /> <br /> ==External Links==</div>

Dave Mark http://gameai.com/wiki/index.php?title=Template:Verification 2011-07-21T22:11:10Z

<p>Dave Mark: added question mark to explanation</p> <hr /> <div>&lt;table class=&quot;stamp&quot;&gt;&lt;tr&gt;&lt;td&gt;'''This section&lt;br /&gt;&lt;span style=&quot;color: #ff4;&quot;&gt;needs verification&lt;/span&gt;&lt;br /&gt;by an AIGPG member.'''[[File:Question_mark.png|link=AIGPG_Stamps#Needs_Verification|alt=What does this mean?]]&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;</div>

Dave Mark http://gameai.com/wiki/index.php?title=Template:NeedsInput 2011-07-21T22:08:28Z

<p>Dave Mark: added question mark to explanation</p> <hr /> <div>&lt;table class=&quot;stamp&quot;&gt;&lt;tr&gt;&lt;td&gt;'''This section&lt;br /&gt;&lt;span style=&quot;color: #4ff;&quot;&gt;needs input&lt;/span&gt;&lt;br /&gt;from an AIGPG member.'''[[File:Question_mark.png|link=AIGPG_Stamps#Needs_Input|alt=What does this mean?]]&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;</div>

Dave Mark http://gameai.com/wiki/index.php?title=Template:NDA 2011-07-21T22:07:12Z

<p>Dave Mark: added question mark to explanation</p> <hr /> <div>&lt;table class=&quot;stamp&quot;&gt;&lt;tr&gt;&lt;td&gt;'''Details on this topic are&lt;br /&gt;&lt;span style=&quot;color: #e0e;&quot;&gt;currently under NDA.&lt;/span&gt;&lt;br /&gt;Wish we could say more!'''[[File:Question_mark.png|link=AIGPG_Stamps#NDA|alt=What does this mean?]]&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;</div>

Dave Mark http://gameai.com/wiki/index.php?title=Template:AuthorStamp 2011-07-21T22:04:30Z

<p>Dave Mark: added question mark to explanation</p> <hr /> <div>&lt;table class=&quot;stamp&quot;&gt;&lt;tr&gt;&lt;td&gt;'''This section is based on&lt;br /&gt;&lt;span style=&quot;color: #3c3;&quot;&gt;first-hand knowledge&lt;/span&gt;&lt;br /&gt;by AIGPG member,&lt;br /&gt; [{{{url}}} {{{name}}}].'''[[File:Question_mark.png|link=AIGPG_Stamps#First-Hand_Knowledge|alt=What does this mean?]]&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;</div>

Dave Mark http://gameai.com/wiki/index.php?title=File:Question_mark.png 2011-07-21T21:57:49Z

<p>Dave Mark: </p> <hr /> <div></div>

Dave Mark http://gameai.com/wiki/index.php?title=File:Question_mark.gif 2011-07-21T21:51:43Z

<p>Dave Mark: </p> <hr /> <div></div>

Dave Mark http://gameai.com/wiki/index.php?title=Halo_3 2011-07-20T01:08:28Z

<p>Dave Mark: Initial creation</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> <br /> <br /> {{GameInfoBox<br /> |gametitle=Halo 3<br /> |imagefile=Halo3Box.jpg<br /> |developer=Bungie<br /> |publisher=Microsoft Game Studios<br /> |year=2007<br /> |platforms=X360<br /> |genres=FPS<br /> |era=Tactical Reasoning<br /> }}<br /> <br /> Halo 3 is a first-person shooter game taking the player on a series of missions that engage in combat against various forms of alien life.<br /> <br /> ==Description of AI Behavior==<br /> (What kinds of things was the AI supposed to do?)<br /> <br /> <br /> ===Notable Behaviors===<br /> (What really special things did the AI have to perform that made it stand out?)<br /> <br /> <br /> <br /> ==Architectures==<br /> <br /> ===Each Arch. Should Have a Heading Like This===<br /> &lt;!-- If you are filling this out based on first-hand knowledge<br /> fill out the AuthorStamp below. Else delete it. --&gt;<br /> {{AuthorStamp|name=Your Name|url=Your Name}}<br /> <br /> ===Another Architecture===<br /> <br /> <br /> <br /> ==Post-Mortem==<br /> <br /> ===What Worked===<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ===What Didn't Work===<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ===Lessons Learned===<br /> <br /> <br /> <br /> ==Reception by Public==<br /> (Was there positive or negative reception from the players and/or media?)<br /> <br /> <br /> <br /> ==References==<br /> <br /> <br /> <br /> <br /> ==External Links==<br /> (ADD LATER)</div>

Dave Mark http://gameai.com/wiki/index.php?title=File:Halo3Box.jpg 2011-07-20T01:04:59Z

<p>Dave Mark: </p> <hr /> <div></div>

Dave Mark http://gameai.com/wiki/index.php?title=Halo_2 2011-07-20T01:02:55Z

<p>Dave Mark: Initial creation</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> <br /> <br /> {{GameInfoBox<br /> |gametitle=Halo 2<br /> |imagefile=Halo2Box.png<br /> |developer=Bungie<br /> |publisher=Microsoft Game Studios<br /> |year= 2004<br /> |platforms=Xbox, PC<br /> |genres=FPS<br /> |era=Tactical Reasoning<br /> }}<br /> <br /> Halo 2 is a first-person shooter game taking the player on a series of missions that engage in combat against various forms of alien life.<br /> <br /> ==Description of AI Behavior==<br /> (What kinds of things was the AI supposed to do?)<br /> <br /> <br /> ===Notable Behaviors===<br /> (What really special things did the AI have to perform that made it stand out?)<br /> <br /> <br /> <br /> ==Architectures==<br /> <br /> ===Each Arch. Should Have a Heading Like This===<br /> &lt;!-- If you are filling this out based on first-hand knowledge<br /> fill out the AuthorStamp below. Else delete it. --&gt;<br /> {{AuthorStamp|name=Your Name|url=Your Name}}<br /> <br /> ===Another Architecture===<br /> <br /> <br /> <br /> ==Post-Mortem==<br /> <br /> ===What Worked===<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ===What Didn't Work===<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ===Lessons Learned===<br /> <br /> <br /> <br /> ==Reception by Public==<br /> (Was there positive or negative reception from the players and/or media?)<br /> <br /> <br /> <br /> ==References==<br /> <br /> <br /> <br /> <br /> ==External Links==<br /> (ADD LATER)</div>

Dave Mark http://gameai.com/wiki/index.php?title=File:Halo2Box.png 2011-07-20T01:00:47Z

<p>Dave Mark: </p> <hr /> <div></div>

Dave Mark http://gameai.com/wiki/index.php?title=Game_Index 2011-07-20T00:57:58Z

<p>Dave Mark: Added Halo 2 and 3</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> This is a list of games that currently have ''history of AI'' pages:<br /> <br /> <br /> {{template:TOC}}<br /> <br /> <br /> <br /> ==0-9==<br /> <br /> <br /> ==A==<br /> <br /> <br /> ==B==<br /> <br /> <br /> ==C==<br /> <br /> <br /> ==D==<br /> <br /> <br /> ==E==<br /> <br /> <br /> ==F==<br /> <br /> <br /> ==G==<br /> <br /> <br /> ==H==<br /> {{GameIndexEntry|title=Halo 2|page=Halo 2|developer=Bungie|publisher=Microsoft Game Studios|year=2004|platforms=Xbox, PC}}<br /> {{GameIndexEntry|title=Halo 3|page=Halo 3|developer=Bungie|publisher=Microsoft Game Studios|year=2007|platforms=Xbox, PC}}<br /> ==I==<br /> {{GameIndexEntry|title=Independence War 2: Edge of Chaos|page=Independence War 2|developer=Particle Systems Ltd.|publisher=Infogrames|year=2001|platforms=PC}}<br /> <br /> ==J==<br /> <br /> <br /> ==K==<br /> <br /> <br /> ==L==<br /> <br /> <br /> ==M==<br /> {{GameIndexEntry|title=Microsoft Baseball 3D|page=Microsoft Baseball 3D|developer=WizBang! Software Productions|publisher=Microsoft Game Studios|platforms=PC|year=1998}}<br /> <br /> ==N==<br /> <br /> <br /> ==O==<br /> <br /> <br /> ==P==<br /> {{GameIndexEntry|title=Pac-Man|page=Pac-Man|developer=Namco|publisher=Namco, Midway|platforms=Arcade|year=1980}}<br /> {{GameIndexEntry|title=Powerdrome|page=Powerdrome|developer=Argonaut Software|publisher=Mad Duck Productions|year=2004|platforms=PS2, Xbox, PC}}<br /> <br /> ==Q==<br /> <br /> <br /> ==R==<br /> <br /> <br /> ==S==<br /> {{GameIndexEntry|title=SimCity|page=SimCity|developer=Maxis|publisher=Brøderbund|platforms=Amiga, Atari ST, C64, Macintosh, PC|year=1989}}<br /> <br /> ==T==<br /> {{GameIndexEntry|title=The Sims|page=The Sims|developer=Maxis|publisher=Electronic Arts|platforms=PC, Macintosh, PS2, Xbox, GameCube|year=2000}}<br /> <br /> ==U==<br /> <br /> <br /> ==V==<br /> <br /> <br /> ==W==<br /> <br /> <br /> ==X==<br /> {{GameIndexEntry|title=X3 Reunion|page=X3 Reunion|developer=Egosoft|publisher=Deep Silver, Enlight|platforms=PC|year=2005}}<br /> <br /> ==Y==<br /> <br /> <br /> ==Z==<br /> <br /> ==Misc.==<br /> {{GameIndexEntry|title=Game History Format|page=Game History Format|developer=Use this for new games|publisher=AIGPG|platforms=All|year=2011}}</div>

Dave Mark http://gameai.com/wiki/index.php?title=Powerdrome 2011-07-20T00:55:15Z

<p>Dave Mark: Initial creation for Brett</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> <br /> <br /> {{GameInfoBox<br /> |gametitle=Powerdrom<br /> |imagefile=PowerdromeBox.jpg<br /> |developer=Argonaut Software<br /> |publisher=Mad Duck Productions<br /> |year= 2004<br /> |platforms=PS2, XBox, PC<br /> |genres=Racing<br /> |era=Tactical Reasoning<br /> }}<br /> <br /> Powerdrome is a futuristic racing game where players race jet-engined, anti-gravity bikes called 'blades' around closed tracks.<br /> <br /> ==Description of AI Behavior==<br /> (What kinds of things was the AI supposed to do?)<br /> <br /> <br /> ===Notable Behaviors===<br /> (What really special things did the AI have to perform that made it stand out?)<br /> <br /> <br /> <br /> ==Architectures==<br /> <br /> ===Each Arch. Should Have a Heading Like This===<br /> &lt;!-- If you are filling this out based on first-hand knowledge<br /> fill out the AuthorStamp below. Else delete it. --&gt;<br /> {{AuthorStamp|name=Your Name|url=Your Name}}<br /> <br /> ===Another Architecture===<br /> <br /> <br /> <br /> ==Post-Mortem==<br /> <br /> ===What Worked===<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ===What Didn't Work===<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ===Lessons Learned===<br /> <br /> <br /> <br /> ==Reception by Public==<br /> (Was there positive or negative reception from the players and/or media?)<br /> <br /> <br /> <br /> ==References==<br /> <br /> <br /> <br /> <br /> ==External Links==<br /> (ADD LATER)</div>

Dave Mark http://gameai.com/wiki/index.php?title=File:PowerdromeBox.jpg 2011-07-20T00:51:16Z

<p>Dave Mark: </p> <hr /> <div></div>

Dave Mark http://gameai.com/wiki/index.php?title=Game_Index 2011-07-20T00:49:29Z

<p>Dave Mark: Added Powerdrome</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> This is a list of games that currently have ''history of AI'' pages:<br /> <br /> <br /> {{template:TOC}}<br /> <br /> <br /> <br /> ==0-9==<br /> <br /> <br /> ==A==<br /> <br /> <br /> ==B==<br /> <br /> <br /> ==C==<br /> <br /> <br /> ==D==<br /> <br /> <br /> ==E==<br /> <br /> <br /> ==F==<br /> <br /> <br /> ==G==<br /> <br /> <br /> ==H==<br /> <br /> <br /> ==I==<br /> {{GameIndexEntry|title=Independence War 2: Edge of Chaos|page=Independence War 2|developer=Particle Systems Ltd.|publisher=Infogrames|year=2001|platforms=PC}}<br /> <br /> ==J==<br /> <br /> <br /> ==K==<br /> <br /> <br /> ==L==<br /> <br /> <br /> ==M==<br /> {{GameIndexEntry|title=Microsoft Baseball 3D|page=Microsoft Baseball 3D|developer=WizBang! Software Productions|publisher=Microsoft Game Studios|platforms=PC|year=1998}}<br /> <br /> ==N==<br /> <br /> <br /> ==O==<br /> <br /> <br /> ==P==<br /> {{GameIndexEntry|title=Pac-Man|page=Pac-Man|developer=Namco|publisher=Namco, Midway|platforms=Arcade|year=1980}}<br /> {{GameIndexEntry|title=Powerdrome|page=Powerdrome|developer=Argonaut Software|publisher=Mad Duck Productions|year=2004|platforms=PS2, Xbox, PC}}<br /> <br /> ==Q==<br /> <br /> <br /> ==R==<br /> <br /> <br /> ==S==<br /> {{GameIndexEntry|title=SimCity|page=SimCity|developer=Maxis|publisher=Brøderbund|platforms=Amiga, Atari ST, C64, Macintosh, PC|year=1989}}<br /> <br /> ==T==<br /> {{GameIndexEntry|title=The Sims|page=The Sims|developer=Maxis|publisher=Electronic Arts|platforms=PC, Macintosh, PS2, Xbox, GameCube|year=2000}}<br /> <br /> ==U==<br /> <br /> <br /> ==V==<br /> <br /> <br /> ==W==<br /> <br /> <br /> ==X==<br /> {{GameIndexEntry|title=X3 Reunion|page=X3 Reunion|developer=Egosoft|publisher=Deep Silver, Enlight|platforms=PC|year=2005}}<br /> <br /> ==Y==<br /> <br /> <br /> ==Z==<br /> <br /> ==Misc.==<br /> {{GameIndexEntry|title=Game History Format|page=Game History Format|developer=Use this for new games|publisher=AIGPG|platforms=All|year=2011}}</div>

Dave Mark http://gameai.com/wiki/index.php?title=Independence_War_2:_Edge_of_Chaos 2011-07-20T00:45:04Z

<p>Dave Mark: Initial creation for Brett</p> <hr /> <div>{{template:HistoryOfAI}}<br /> <br /> <br /> <br /> {{GameInfoBox<br /> |gametitle=Independence War 2: Edge of Chaos<br /> |imagefile=IndependenceWar2Box.jpg<br /> |developer=Particle Systems Ltd.<br /> |publisher=Infogrames<br /> |year= 2001<br /> |platforms=PC<br /> |genres=Space Combat Sim.<br /> |era=<br /> }}<br /> <br /> [http://en.wikipedia.org/wiki/Independence_War_2:_Edge_of_Chaos Independence War 2: Edge of Chaos] is a space combat simulation game in the style of the game &quot;Elite&quot;. Players pilot their upgradable spacecraft around the galaxy for trade, piracy, special missions, and, when necessary, combat.<br /> <br /> ==Description of AI Behavior==<br /> (What kinds of things was the AI supposed to do?)<br /> <br /> <br /> ===Notable Behaviors===<br /> (What really special things did the AI have to perform that made it stand out?)<br /> <br /> <br /> <br /> ==Architectures==<br /> <br /> ===Naviagation===<br /> &lt;!-- If you are filling this out based on first-hand knowledge<br /> fill out the AuthorStamp below. Else delete it. --&gt;<br /> {{AuthorStamp|name=Your Name|url=Your Name}}<br /> <br /> ===Another Architecture===<br /> <br /> <br /> <br /> ==Post-Mortem==<br /> <br /> ===What Worked===<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ====Individual Good Thing====<br /> <br /> Something really went well.<br /> <br /> ===What Didn't Work===<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ====Individual Bad Thing====<br /> Something really sucked.<br /> <br /> ===Lessons Learned===<br /> <br /> <br /> <br /> ==Reception by Public==<br /> (Was there positive or negative reception from the players and/or media?)<br /> <br /> <br /> <br /> ==References==<br /> {{reflist|sourcename=|title=|venue=|year=|url=}}<br /> <br /> <br /> <br /> ==External Links==<br /> (ADD LATER)</div>

Dave Mark http://gameai.com/wiki/index.php?title=File:IndependenceWar2Box.jpg 2011-07-20T00:36:49Z

<p>Dave Mark: </p> <hr /> <div></div>

Dave Mark