1 / 27

SKULLS OF THE SHOGUn AI POST-MORTEM

SKULLS OF THE SHOGUn AI POST-MORTEM. Borut Pfeifer. Developer: Haunted Temple Studios Publisher: Microsoft Platforms: XBLA, Windows Phone, Windows 8 Release Date: February 2012 Fall 2012. Background. SKULLS OF THE SHOGUN. CONSTRAINTS. Combination of RTS & TBS elements

raanan
Télécharger la présentation

SKULLS OF THE SHOGUn AI POST-MORTEM

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SKULLS OF THE SHOGUnAI POST-MORTEM Borut Pfeifer Developer: Haunted Temple Studios Publisher: Microsoft Platforms: XBLA, Windows Phone, Windows 8 Release Date: February 2012Fall 2012

  2. Background

  3. SKULLS OF THE SHOGUN

  4. CONSTRAINTS • Combination of RTS & TBS elements • Turn based/board gamey • No grid/analog world • An action is a resource (5 orders per turn) • Arcade-strategy: fast, no “waiting for AI”

  5. GAME MECHANICS - Units

  6. GAME MECHANICS - Resources

  7. GAME MECHANICS - TERRAIN

  8. GAME MECHANICS - Advanced ABILITIES

  9. 1stsKULL

  10. Objective Evaluation NxM problem: • All units vs. all targets • Infeasible, but ideal, right? • Eval big list of unit-target pairs • Utility theory based approach Issues: • Hard to compare strategic differences with so many pairs. • Huge diff in utility between available/unavailable objectives. • Deciding to defend required a lot more context (want to avoid duplicating this logic in each low level objective).

  11. Pathfinding Pathfinding in analog space • Use grid even though inexact. • Needs dynamic obstacle avoidance. • Can’t avoid inaccuracies.

  12. 1st PASS Lessons • Must organize objective comparisons. • Architecture must be very fault-tolerant. • Target distance key in comparing objectives. • Must know all pair distances, fast, at turn start - can’t avoid NxM problem here.

  13. 2nd sKULL

  14. EstimatING Strategic Distances Est. distances for strategic decisions: • Use quad tree w/fewer nodes • More inaccurate • Use estimates when assigning objectives • Still need full path when starting action

  15. Decision Making • Single list of objectives/targets • Split by type: • Resources • Attack • Defense • High level strategy modes: • Build up resources • Attack • Last ditch (losing badly)

  16. Decision Making Algorithm • Run pathfinding on quad tree for all pairs • Rank objectives in each category • ex: prioritize enemies on periphery as easier to kill • Find available units for every objective • in range this turn • Run high level strategy check • Easy to manage, 1-2 pages of if statements • Assign 5 orders to top objectives by strategy • resources strategy = 3 resource objectives, 2 attack, 1 defense • Fallback to other available objectives, then unavailable.

  17. 2nd Pass Lessons • Comparing objectives more manageable. • Lost some unimportant comparisons. • (When Unit X is better than Y for 2 objectives, but is way better fit for lower priority objective.) • Quad tree introduces error: • Before objective starts, look for real path (dynamic obstacles can still cause failure) • Re-eval objectives on failure: looks “human”, because it tries one thing, finds it can’t succeed, tries another.

  18. 3rdsKULL

  19. STILL Missing Elements • Need to prioritize unavailable objectives sometimes: Reinforcements! • Simple set of tests in high level strategy analysis • < 3-4 avail objectives for > 2 turns, if extra units • Need more tactical info for objectives comparisons: Influence maps! • Besides avoiding counterattacks or prioritizing available targets, why is one target better than another? • Difficulty modes, advanced spell use

  20. Influence map – Red Army

  21. Influence map – Blue Army

  22. Influence map – Blue Army Resource appeal Resource strength – enemy influence (normalized)

  23. Influence map – Blue Army Threat Level Threat = Red team – Blue team influence Activity = Red team + Blue team influence Vulnerability = Threat - activity Threat to Blue = Red team – Blue team influence

  24. Influence Map usage • Easily plugged in to objective eval. • Influence used for base objective score. • Each objective multiplies that score. • Maybe 3-7 cases per objective to modify score (easy to manage).

  25. Oh Yeah… Advanced AI: • Ledges: Positioning to knock off, avoiding, forming walls • Advanced spells: Simple, conservative scoring (costs rice). • Difficulty: Categorize behaviors for novice vs. expert. Things the AI still doesn’t do: • Use Spawn Oni spell (barbarian unit – too chaotic!) • Not very zen like (doesn’t follow master level strategies).

  26. Learning is fun! • Always Be Architecting • Never spend too much time up front - you’ll be wrong. • Apply prototyping methodology - throw stuff out. • Leave spaces - code w/flexibility in mind,so you won’t have to. • Apples to Apples • Split up decision making to compare similar utilities. • Push common analysis (e.g. defense) to higher level to take advantage of broader strategies. • Fault Tolerance at every level • Shit happens, your game model will never be accurate enough. • Always try to deal w/error 1 level above, possibly pass it higher up.

  27. More Info Skulls of the Shogun - Fall 2012 XBLA, Windows Phone, Windows 8 borut@skullsoftheshogun.com

More Related