Difference between revisions of "Categories"

From RogueBasin
Jump to navigation Jump to search
(→‎Roguelike engines: remove duplication)
(→‎Evolutionary Branch Classification: remove obvious rogue parenthetical; NetHack inspired Diablo's developers, calling it Bandish seems a stretch ; clarify language ; logic seems muddled)
Line 13: Line 13:
== Evolutionary Branch Classification ==
== Evolutionary Branch Classification ==


These are the two main evolutionary branches taken from [[Rogue]]. Of course, many roguelikes belong to neither branch, especially the newer ones which take ideas from other gaming genres such as simulation and strategy. (Rogue itself, for example, can't be meaningfully ascribed to one branch or the other)
These are the two main evolutionary branches taken from [[Rogue]]. Of course, many roguelikes belong to neither, especially more recent games which often borrow from other genres, such as simulation and strategy.


*[[Hacklike]]. These are games that owe inspiration primarily from the [[Hack]] line of games. [[NetHack]] is the most advanced in this genre. [[ADOM]] and [[Crawl]] may also be considered Hacklikes.
*[[Hacklike]]. These games take inspiration primarily from the [[Hack]] and its descendent. [[NetHack]] is the most advanced in this genre. [[ADOM]] and [[Crawl]] may also be considered Hacklikes.
*[[Band]].  These are games which owe inspiration from the [[Moria]] line of games. Properly, this would only refer to [[Angband]] and its variants (see [[Angband Variants]]), but one can extend it to other games with similar playstyle. [[Diablo]] is considered a Band by those who consider it a roguelike.
*[[Band]].  These are games take inspiration from [[Moria]] and its descendent. Properly, this term would only refer to [[Angband]] and its variants (see [[Angband Variants]]), but one can extend it to other games with similar playstyle. Many consider [[Diablo]] to be a Band.


Another way to look at this is to build a tree of roguelike evolution. One problem with this approach is how to draw the lines.  In some cases, it may be clear that one roguelike derives from another. [[NetHack]] continued with the source code of [[Hack]], so a connection seems clear.  Othertimes it is more difficult.  Where does [[ADOM]] fit?  It is a [[Hacklike]], but doesn't share any code from any other roguelikes. Similarly, [[Avanor]] is based on the gameplay of [[ADOM]], but again shares no code.
Another approach is to build a tree of roguelike evolution. In some cases, it may be clear that one roguelike derives from another. For example, [[NetHack]] was built atop [[Hack]], so its lineage seems clear.  Other times, determining relations proves more difficult.  Where does [[ADOM]] fit?  It appears to be a [[Hacklike]], but does not share its codebase with any other game. Similarly, [[Avanor]] adopts the gameplay, but not the actual code, of [[ADOM]].


<code>
<code>
Line 26: Line 26:
   [[Moria]]  [[Larn]]  [[Omega]]        [[Hack]]
   [[Moria]]  [[Larn]]  [[Omega]]        [[Hack]]
     |            |            |
     |            |            |
  [[Angband]]        |          [[Nethack]]
  [[Angband]]        |          [[NetHack]]
                 |  __________|__________
                 |  __________|__________
                 |  |    |        |      |
                 |  |    |        |      |
                 [[ADOM]]  [[Zap'm]]  [[Slash'em]]  [[Crawl]]
                 [[ADOM]]  [[Zap'm]]  [[SLASH'EM]]  [[Crawl]]
   
   
   
   
  ''Schematic family tree of popular roguelike games, showing inheritance by playstyle.''
  ''Schematic family tree of popular roguelike games, showing inheritance by play style.''
</code>
</code>


What I think we should do is create a series of differentiators for Roguelikes.  We can then have a standard nomenclature for describing Roguelikes and then can determine what taxonomic groups of roguelikes we should create.
Forming a series of differentiators might offer a standard nomenclature for describing roguelikes from which one might construct taxonomic groups of roguelikes.


List of Differentiators:
List of Differentiators:
* Plot vs No Plot.  A plot based Roguelike has a non trivial plot. Note that quests, "kill the bad guy at the bottom", etc, do not constitute a non-trivial plot.  Plot based roguelikes would be [[ADOM]] and [[Gearhead]]
* Plot vs. Plotless.  A plot-based roguelike sports a non-trivial plot. Note that quests ("kill the bad guy at the bottom", etc.) do not a non-trivial plot make.  Plot-based roguelikes would include [[ADOM]] and [[Gearhead]].
* Persistent Dungeons.  Persistent dungeons imply many differences to gameplay.  They often mean you have a finite number of resources available.  On the other hand, they mean you have unlimitted storage capacity.  They also mean there may be little alternative to facing a bad encounter. Pacing thus differs radically, and this becomes a significant differentiator.  [[ADOM]], despite the infinite dungeon, would be in the Persistent Dungeon camp.  [[Band]]s are almost uniformly non-persistent dungeons.
* Dungeon Persistence.  Persistent dungeons impact gameplay in many ways.  They lead to finite in-game resources countered by unlimitted storage capacity (assuming object peristence, as well).  They also leave few alternatives to confronting difficult obstacles and foes. Pacing thus differs radically, and this becomes a significant differentiator.  [[ADOM]], despite the infinite dungeon, would fall into this camp.  [[Band]]s are almost uniformly non-persistent.
* Equipment Upgrade Path.  How likely are you to finalize a piece of equipment early in your game?  [[Band]]s tend to have a deep upgrade cycle, where a large part of the game is chosing when and how to upgrade.  [[Hacklike]]s tend to have a trivial equipment upgrade, where the difficulty part may be acquiring the equipment rather than deciding whether to use it.
* Equipment Upgrade Path.  How likely are you to finalize a piece of equipment early in your game?  [[Band]]s tend to have a deep upgrade cycle, where a large portion of the game lies in choosing when and how to upgrade.  [[Hacklike]]s tend to have a trivial equipment upgrade, where the difficulty lies in acquiring equipment rather than in deciding whether to use it.
* Inventory Size.  A relatively wide spectrum is present here.  [[Band]]s often have fixed inventory slots that make this an important part of the game.  However, [[NetHack]] also has limited inventory - 52 slots or so, until one acquires a bag.  Even with a bag, items in the bag are not in ready reach.  [[ADOM]], by contrast, allows one to cart along pages of inventory provided one has the Strength of Atlas spell.
* Inventory Size.  A relatively wide spectrum is present here.  [[Band]]s often have fixed inventory slots that make this an important part of the game.  However, [[NetHack]] also has limited inventory &mdash; 52 slots or so, until one acquires a bag.  Even with a bag, items stored therein are not within ready reach.  [[ADOM]], by contrast, allows one to cart along pages of inventory provided one has the Strength of Atlas.
* Dungeon Size.  Do dungeon levels fit on one screen?  Most [[Band]]s make levels that do not fit on a screen.  [[Hacklike]]s tend to fit on one screen.  Note that [[Crawl]] is an exception to this.  There are important gameplay differences when one can see the entire dungeon at the same time.  Consider the effect on Detect Monster like spells.  (While [[ADOM]] resizes to fit the screen, note that it will always fit the screen!)
* Dungeon Size.  Do dungeon levels fit on one screen?  Most [[Band]]s make levels that do not fit on a screen.  [[Hacklike]]s tend to fit on one screen.  Note that [[Crawl]] represents an exception to this.  There are important gameplay differences when one can see the entire dungeon at the same time.  Consider the effect on Detect Monster like spells.  (While [[ADOM]] resizes to fit the screen, note that it will always fit the screen!)
* Wilderness.  Is there a wilderness area outside of the dungeon?  [[ZAngband]] and [[ADOM]] are examples of this.
* Wilderness.  Is there a wilderness area outside of the dungeon?  [[ZAngband]] and [[ADOM]] are examples of this.
* Town with Supplies.  Are there surface towns that carry needed adventuring supplies?
* Town with Supplies.  Are there surface towns that carry needed adventuring supplies?
Line 49: Line 49:
* [[Hacklike]] - Persistent Dungeons, Little Equipment Upgrade Path, Large Inventory Size, Single Screen Dungeon Size, No Town With Supplies
* [[Hacklike]] - Persistent Dungeons, Little Equipment Upgrade Path, Large Inventory Size, Single Screen Dungeon Size, No Town With Supplies
* [[Band]] - Non-Persistent Dungeons, Equipment Upgrade Path, Limitted Inventory Size, Multi Screen Dungeons, Town with Supplies.
* [[Band]] - Non-Persistent Dungeons, Equipment Upgrade Path, Limitted Inventory Size, Multi Screen Dungeons, Town with Supplies.
* AdomLike - [[Hacklike]] + Plot + Wilderness
* ADOMlike - [[Hacklike]] + Plot + Wilderness
* ZAngbandLike - [[Band]] + Wilderness
* ZAngbandLike - [[Band]] + Wilderness

Revision as of 03:33, 22 May 2005

Official Development State classification

  • Major Roguelikes: Time-tested and found worthy of attention; foremost representatives of the genre.
  • Stable games: Playable games in their given state, merely lacking the fanbase to enter the ranks of the majors.
  • Beta Projects: In general release, but not yet considered to be complete. Players are cautioned to expect and possibly await more polished releases.
  • Alpha Projects: Proof of concept releases; generally unplayable.
  • Talkie Talkie Projects: Projects under discussion for which no actual code or executable has circulated.

Roguelike engines

There also exist RogueLike Engines, which in and of themselves are not games, but offer the means to construct new games.

Evolutionary Branch Classification

These are the two main evolutionary branches taken from Rogue. Of course, many roguelikes belong to neither, especially more recent games which often borrow from other genres, such as simulation and strategy.

  • Hacklike. These games take inspiration primarily from the Hack and its descendent. NetHack is the most advanced in this genre. ADOM and Crawl may also be considered Hacklikes.
  • Band. These are games take inspiration from Moria and its descendent. Properly, this term would only refer to Angband and its variants (see Angband Variants), but one can extend it to other games with similar playstyle. Many consider Diablo to be a Band.

Another approach is to build a tree of roguelike evolution. In some cases, it may be clear that one roguelike derives from another. For example, NetHack was built atop Hack, so its lineage seems clear. Other times, determining relations proves more difficult. Where does ADOM fit? It appears to be a Hacklike, but does not share its codebase with any other game. Similarly, Avanor adopts the gameplay, but not the actual code, of ADOM.

              Rogue
    ____________|_____________
   |     |      |             |
 Moria  Larn  Omega         Hack
   |            |             |
Angband         |          NetHack
                |   __________|__________
                |  |    |        |       |
                ADOM  Zap'm  SLASH'EM  Crawl


Schematic family tree of popular roguelike games, showing inheritance by play style.

Forming a series of differentiators might offer a standard nomenclature for describing roguelikes from which one might construct taxonomic groups of roguelikes.

List of Differentiators:

  • Plot vs. Plotless. A plot-based roguelike sports a non-trivial plot. Note that quests ("kill the bad guy at the bottom", etc.) do not a non-trivial plot make. Plot-based roguelikes would include ADOM and Gearhead.
  • Dungeon Persistence. Persistent dungeons impact gameplay in many ways. They lead to finite in-game resources countered by unlimitted storage capacity (assuming object peristence, as well). They also leave few alternatives to confronting difficult obstacles and foes. Pacing thus differs radically, and this becomes a significant differentiator. ADOM, despite the infinite dungeon, would fall into this camp. Bands are almost uniformly non-persistent.
  • Equipment Upgrade Path. How likely are you to finalize a piece of equipment early in your game? Bands tend to have a deep upgrade cycle, where a large portion of the game lies in choosing when and how to upgrade. Hacklikes tend to have a trivial equipment upgrade, where the difficulty lies in acquiring equipment rather than in deciding whether to use it.
  • Inventory Size. A relatively wide spectrum is present here. Bands often have fixed inventory slots that make this an important part of the game. However, NetHack also has limited inventory — 52 slots or so, until one acquires a bag. Even with a bag, items stored therein are not within ready reach. ADOM, by contrast, allows one to cart along pages of inventory provided one has the Strength of Atlas.
  • Dungeon Size. Do dungeon levels fit on one screen? Most Bands make levels that do not fit on a screen. Hacklikes tend to fit on one screen. Note that Crawl represents an exception to this. There are important gameplay differences when one can see the entire dungeon at the same time. Consider the effect on Detect Monster like spells. (While ADOM resizes to fit the screen, note that it will always fit the screen!)
  • Wilderness. Is there a wilderness area outside of the dungeon? ZAngband and ADOM are examples of this.
  • Town with Supplies. Are there surface towns that carry needed adventuring supplies?

We can thus create the following adhoc categories:

  • Hacklike - Persistent Dungeons, Little Equipment Upgrade Path, Large Inventory Size, Single Screen Dungeon Size, No Town With Supplies
  • Band - Non-Persistent Dungeons, Equipment Upgrade Path, Limitted Inventory Size, Multi Screen Dungeons, Town with Supplies.
  • ADOMlike - Hacklike + Plot + Wilderness
  • ZAngbandLike - Band + Wilderness