Difference between revisions of "User:51mplex/drydock"

From RogueBasin
Jump to navigation Jump to search
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
Races are the highest level character differentiators in the roguelike genre: they define the major characteristics which differentiate all the characters, including attributes, skills and appearance. Usually the "races" would more correctly be defined as different "species" or even "types" – golems, for example, are neither a race nor a species, but a class of magically-powered artificial beings.
'''Quests''' are one of the characteristic features of computer role-playing games (further simply RPGs in this article, as the nature of tabletop RPGs is very different). By definition, an RPG relies on them to develop the plot and keep the player entertained.


Most roguelikes use classic races from Tolkien's books, like humans, elves, dwarves, trolls, etc. However, there is a growing tendency to explore different universes with a brand new stock of races. Certainly, non-fantasy themed roguelikes will generally require a different set. The races offered in a game can provide setting flavor, offer different difficulty levels, or offer qualitatively different gaming experiences (although only a few exotic races actually fulfill this last function, the most challenging to achieve and have it work well).
A distinction is usually made between ''the'' main quest, whose completion traditionally marks the end of the game, and side quests, which are generally optional and are done for rewards.


Several typical tolkienesque races are briefly described in this article.
==The structure of a quest==
A quest can be defined as a ''series of actions that have to be taken to reach an ultimate goal''. To be complete and to have sense, a quest must have several basic elements:
; Target: What your character is supposed to change in the game world. The most typical example is a fetch quest, in which the player must acquire some item and bring it back.
; Chain of prerequisites: What must be done to achieve the quest target. A simple beginners' quest might have no such chain of prerequisites, but to complicate things for the player, most quests have some chain of requirements. For example, on a quest to retrieve a dragon tooth (the target), the player must first level up to some point, accumulate good equipment, find the golden key (a quest item) to get the whistle of sound sleep (another quest item), ask a hermit for directions and only then actually fight the dragon.
; Reward: Players won't do quests for nothing, but expect to get some benefits in return, for example an artefact item with special properties or some perk unattainable by conventional means. An exception may be the main quest, which simply ends the game and as such can't supply any other reward than a credits screen.
; Decorum: Everything else that exists only to create the atmosphere – why the quest giver wants you to do the job for them, the way they speak, the style of the quest items, and so on.


==Mundane: Humans==
The terms used above are in no way standardised or universal, but were defined for the needs of this article.
There is a general tendency to include our human species in many works of fantasy, using ''Homo sapiens'' as a standard race to which others are compared. Humans usually have the most average statistics, and possess no unique abilities. They are the most common humanoid species in many game universes.


==High men: Elves==
==Quests in roguelikes==
While humans are portrayed as average, tolkienesque elves by convention are better in most respects, from lifespan to morality and alignment. Elves are habitually the most magically empowered, and as such are often cast into wizard or druid roles. Another characteristic feature is pride or even hubris.
Due to the complexity of interesting and involving quests, the main quest is almost always static. However, lesser side quests which aren't so developed are more feasibly generated by an algorithm.


An alternate depiction is one of a race deeply connected with nature and forests in particular. Such elves are usually smaller and more similar to gnomes or smurfs.
==Creating dynamic quests algorithmically==


==Stout men: Dwarves==
Tolkien's dwarves are also a proud race, but instead of living in harmony in nature, dwarves prefer mining and industry, and a proper axe instead of magical incantations. For this reason, they are often shown as elves' counterparts.


The original nordic dwarves are actually ''dark elves'', and weren't said to be smaller than humans before the 13th century.
==HTML and CSS==
The standard method for user interaction is via HTML, CSS and its Document Object Model (DOM). Thanks to this, JavaScript supplies perhaps one of the most portable APIs for development. In the current state of things, there are actually several environments for visual presentation and interaction within a modern web browser:


==Cute: Hobbits and gnomes==
; HTML, CSS and the DOM (Document Object Model)
This group of humanoids combines fantasy with down-to-earthness, which results in a race that is quite similar to humans. Hobbits/gnomes generally don't possess special powers or great physical might, but this is usually offset by them being good, simple, cute farmers.
: The oldest presentational API, which is also known collectively with JavaScript as DHTML, for Dynamic HTML. It involves using pre-defined HTML elements and changing their style to create a dynamically-changing web page. Traditional DHTML is only of utility to very simple games, since it is not possible to escape the limits of presentational HTML markup – it is not possible to draw free shapes without going to extreme lengths to do so.


==Evil: Orcs==
; Canvas 2D context
Orcs are the standard wild, pillaging horde race in tolkienesque settings. They have poorer equipment, but they make up for it with their numberscand physical strength.
: A standard that first appeared in 2004, and is currently supported by all popular modern web browsers (with Internet Explorer being an exception up to version 9). Canvas 2D in itself is a rather simple 2D API with a set of basic functions for drawing lines, arcs, curves and polygons. It also has the useful ability of


==Giant: Trolls and ogres==
{{stub}}
 
 
==Magical: Fairies==
 
<nowiki>{{DISPLAYTITLE:iOS}}
'''iOS''' is the operating system for the iPhone, iPod Touch and iPad. As of 2013, its only major competitor is the [[Android]] platform. Generally speaking, iOS is more closed than Android, due to Apple's control of both the hardware and software. The only source for apps
</nowiki>

Latest revision as of 20:07, 20 March 2014

Quests are one of the characteristic features of computer role-playing games (further simply RPGs in this article, as the nature of tabletop RPGs is very different). By definition, an RPG relies on them to develop the plot and keep the player entertained.

A distinction is usually made between the main quest, whose completion traditionally marks the end of the game, and side quests, which are generally optional and are done for rewards.

The structure of a quest

A quest can be defined as a series of actions that have to be taken to reach an ultimate goal. To be complete and to have sense, a quest must have several basic elements:

Target
What your character is supposed to change in the game world. The most typical example is a fetch quest, in which the player must acquire some item and bring it back.
Chain of prerequisites
What must be done to achieve the quest target. A simple beginners' quest might have no such chain of prerequisites, but to complicate things for the player, most quests have some chain of requirements. For example, on a quest to retrieve a dragon tooth (the target), the player must first level up to some point, accumulate good equipment, find the golden key (a quest item) to get the whistle of sound sleep (another quest item), ask a hermit for directions and only then actually fight the dragon.
Reward
Players won't do quests for nothing, but expect to get some benefits in return, for example an artefact item with special properties or some perk unattainable by conventional means. An exception may be the main quest, which simply ends the game and as such can't supply any other reward than a credits screen.
Decorum
Everything else that exists only to create the atmosphere – why the quest giver wants you to do the job for them, the way they speak, the style of the quest items, and so on.

The terms used above are in no way standardised or universal, but were defined for the needs of this article.

Quests in roguelikes

Due to the complexity of interesting and involving quests, the main quest is almost always static. However, lesser side quests which aren't so developed are more feasibly generated by an algorithm.

Creating dynamic quests algorithmically

HTML and CSS

The standard method for user interaction is via HTML, CSS and its Document Object Model (DOM). Thanks to this, JavaScript supplies perhaps one of the most portable APIs for development. In the current state of things, there are actually several environments for visual presentation and interaction within a modern web browser:

HTML, CSS and the DOM (Document Object Model)
The oldest presentational API, which is also known collectively with JavaScript as DHTML, for Dynamic HTML. It involves using pre-defined HTML elements and changing their style to create a dynamically-changing web page. Traditional DHTML is only of utility to very simple games, since it is not possible to escape the limits of presentational HTML markup – it is not possible to draw free shapes without going to extreme lengths to do so.
Canvas 2D context
A standard that first appeared in 2004, and is currently supported by all popular modern web browsers (with Internet Explorer being an exception up to version 9). Canvas 2D in itself is a rather simple 2D API with a set of basic functions for drawing lines, arcs, curves and polygons. It also has the useful ability of
This page is a stub. Please help RogueBasin by expanding it. Click here to edit this page.


Retrieved from "http://roguebasin.com/index.php?title=User:51mplex/drydock&oldid=37831"