Random encounter
A random encounter is a feature commonly used in various role-playing games whereby combat encounters with non-player character (NPC) enemies or other dangers occur sporadically and at random, usually without the enemy being physically detected beforehand. In general, random encounters are used to simulate the challenges associated with being in a hazardous environment—such as a monster-infested wilderness or dungeon—with uncertain frequency of occurrence and makeup (as opposed to a "placed" encounter). Frequent random encounters are common in Japanese role-playing games like Dragon Quest,[1], Pokémon, and the Final Fantasy series.
Role-playing games
Random encounters—sometimes called wandering monsters—were a feature of Dungeons & Dragons from its beginnings in the 1970s, and persist in that game and its offshoots to this day. Random encounters are usually determined by the gamemaster by rolling dice against a random encounter table. The tables are usually based on terrain (and/or time/weather), and have a chance for differing encounters with different numbers or types of creatures. The results may be modified by other tables, such as whether the encounter is friendly, neutral or hostile. GMs are often encouraged to make their own tables. Specific adventures often have specific tables for locations, like a temple's hallways.
Wandering monsters are often used to wear down player characters and force them to use up consumable resources, such as hit points, magic spells and healing potions, as a way of punishing them for spending too much time in a dangerous area.
Video games
Random encounters were incorporated into early role-playing video games and have been common throughout the genre.[2][3][4] Placed and random encounters were both used in 1981s Wizardry[5] and by the mid-1980s, random encounters made up the bulk of battles in genre-defining games such as Dragon Warrior,[1]Final Fantasy, and The Bard's Tale.[6] Random encounters happen when the player is traversing the game world (often through the use of a "world map" or overworld). Most often, the player encounters enemies to battle, but occasionally friendly or neutral characters can appear, with whom the player might interact differently than with enemies. Random encounters are random in the respect that players cannot anticipate the exact moment of encounter or what will be encountered, as the occurrence of the event is based on factors such as programmed probabilities; Pseudo-random number generators create the sequence of numbers used to determine if an encounter will happen. The form and frequency can vary depending on a number of factors, such as where the player is located in the game world and the statistics of the player character. In some games, items can be found to increase or decrease the frequency of random encounters, even to eliminate them outright, or increase the odds of having a particular encounter.
Random encounters often occur more frequently in caves, forests, and swamps than in open plains. The simplest sort of random encounter algorithm would be as follows:
- Each step, set X to a random integer between 0 and 99.
- If in plains, and X < 8, a random encounter occurs.
- If in swamp, desert, or forest, and X < 16, a random encounter occurs.
The problem with this algorithm is that random encounters occur "too" randomly for the tastes of most players, as there will be "droughts" and "floods" in their distribution. Random encounters in rapid succession are considered undesirable[7][3][8] as they lead to the player's perception of getting "bogged down", but with the simple algorithm, it is possible to have an encounter from taking only one step after an encounter. The early games in the Dragon Quest series, for example, allow random encounters to occur one step after the other. A more elaborate random encounter algorithm (and similar to those used in many games[citation needed]) would be the following:
- Set X to a random integer between 64 and 255.
- For each step in plains, decrement X by 4. For each step in forest, swamp, or desert, decrement X by 8.
- When X < 0, a fight ensues. Go to step 1.
This ensures that, in any terrain, the player will not experience more than one random encounter every eight steps. A game with this type of system can sometimes be taken advantage of by initiating some action that will reset the counter (pausing, opening a menu, saving), especially when using an emulator. This is a popular trick in speedruns to skip time-consuming or dangerous battles or it can be used to ensure that each battle results in a rare or valuable encounter.
Random encounters have become less popular in video games with the passage of time, as gamers often complain that they are annoying, repetitive or discouraging to exploration. The Final Fantasy and Tales series have abandoned random encounter systems with successive games, while relatively newer franchises such as the Chrono series and Kingdom Hearts have never used them.
A more commonly used tactic in later RPGs (used in Final Fantasy XII, Radiata Stories, Fallout 1 and 2, Legend of Legaia and all Kingdom Hearts games) is to set a finite number of enemies in a given area. This cuts down on grinding and does not discourage exploration to the same extent. A similar approach is spawning, where monsters always (re)appear at the same location, as seen in Chrono Trigger[9] and most of Dragon Quest IX.[10][11] Both approaches give players the opportunity to anticipate, evade, or select encounters.
References
^ ab "Features - The History of Dragon Quest". Gamasutra. Retrieved 2010-11-09..mw-parser-output cite.citation{font-style:inherit}.mw-parser-output q{quotes:"""""""'""'"}.mw-parser-output code.cs1-code{color:inherit;background:inherit;border:inherit;padding:inherit}.mw-parser-output .cs1-lock-free a{background:url("//upload.wikimedia.org/wikipedia/commons/thumb/6/65/Lock-green.svg/9px-Lock-green.svg.png")no-repeat;background-position:right .1em center}.mw-parser-output .cs1-lock-limited a,.mw-parser-output .cs1-lock-registration a{background:url("//upload.wikimedia.org/wikipedia/commons/thumb/d/d6/Lock-gray-alt-2.svg/9px-Lock-gray-alt-2.svg.png")no-repeat;background-position:right .1em center}.mw-parser-output .cs1-lock-subscription a{background:url("//upload.wikimedia.org/wikipedia/commons/thumb/a/aa/Lock-red-alt-2.svg/9px-Lock-red-alt-2.svg.png")no-repeat;background-position:right .1em center}.mw-parser-output .cs1-subscription,.mw-parser-output .cs1-registration{color:#555}.mw-parser-output .cs1-subscription span,.mw-parser-output .cs1-registration span{border-bottom:1px dotted;cursor:help}.mw-parser-output .cs1-hidden-error{display:none;font-size:100%}.mw-parser-output .cs1-visible-error{font-size:100%}.mw-parser-output .cs1-subscription,.mw-parser-output .cs1-registration,.mw-parser-output .cs1-format{font-size:95%}.mw-parser-output .cs1-kern-left,.mw-parser-output .cs1-kern-wl-left{padding-left:0.2em}.mw-parser-output .cs1-kern-right,.mw-parser-output .cs1-kern-wl-right{padding-right:0.2em}
^ John, Tracey (2010-05-16). "Scott Pilgrim Video Game References". UGO.com. Archived from the original on 2010-05-21. Retrieved 2010-11-09.
^ ab Michael, Christopher (2010-10-03). "Shadow Madness - Overview". allgame. Retrieved 2010-11-09.
^ Stuart, Keith (2009-12-10). "Serious games case study: the RPG that could save lives | Technology | guardian.co.uk". Guardian. Retrieved 2010-11-09.
^ "Features - Game Design Essentials: 20 RPGs". Gamasutra. Retrieved 2010-11-09.
^ "The History of Computer Role-Playing Games Part 2: The Golden Age(1985-1993)". Gamasutra.com. 2007-02-23. Retrieved 2010-11-09.
^ "> Retroview > Lunar 2: Eternal Blue". RPGamer. Retrieved 2010-11-09.
^ "PlanetDreamcast: Features - Editorials - Random Battles Must Die!". Planetdc.segaretro.org. Retrieved 2010-11-09.
^ "Random Battles - Painful Pleasure or Punishment?". 1up.com. 2010-01-04. Archived from the original on 2012-07-16. Retrieved 2010-11-09.
^ "Dragon Quest IX: Sentinels of the Starry Skies Review: Do Good, Inc". Kotaku.com. 2010-07-23. Retrieved 2010-11-09.
^ "1UP's RPG Blog : My Dragon Quest, Day 14". 1up.com. 2009-07-24. Archived from the original on 2012-10-17. Retrieved 2010-11-09.