Game replay

A game replay is a form of user-generated content. In most instances, a game replay is a recording of a battle between opponents in a video game which can then be viewed by other players.

It is most common in real-time strategy games like StarCraft, Command & Conquer, World in Conflict, Company of Heroes, and Age of Empires, as well as some first-person shooter games such as Counter-Strike (via console command). Recently, game replays are being used on non-computer platforms and games, such as Halo Wars.

A number of websites allow users to upload replays of certain games so that other players can download and watch them, either for entertainment or improving their own skills.

Uses

Game replays are commonly used in the prevention and detection of cheating, especially when used in electronic sports. Game replays are often watched to develop skill at a game, by watching better players and their techniques and build orders. Replays are also used to raise stature in a particular game's community, and entire websites are dedicated to the replays.

Replays are the driving force behind replay reviews. A replay review can be loosely defined as a review of a game replay by an experienced player to determine what can be done to improve and expand upon the initial gamer's skill. Entire websites are dedicated to these reviews, such as Gamereplays.org.

Methods of recording

Replays are normally saved in proprietary formats made by the developers. Replays recorded using third party tools, such as FRAPS, are a form of user-generated content. They capture the on-screen action and compile it into a video format. These replays have the advantage of supporting online playback via video sharing sites, like YouTube or Veoh, but take much more hard disk space than conventional replays.

Other utilities, such as Wegame interact directly with the game, and do not record directly from the screen.[1]

gollark: There are probably horrible issues in the code I hackily tweaked, but I can't see them and it doesn't cause immediate crashing, so I ignored it.
gollark: It leaks 28 bytes of memory once, because I thought it wasn't worth adding extra code to deallocate it on exit.
gollark: Although the current version, as far as I can tell, lacks any issues except a *minor* memory leak.
gollark: Sorry, happen.
gollark: Have you seen my code? Such things definitely happens.

See also

References
  1. Wegame Archived 2009-07-21 at the Wayback Machine; Retrieved on 6/07/09
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.