Code (city orientation)

Code - in urban orientations, a sequence of letters and / or numbers is a password confirming the fulfillment of a certain task ^[1] ^[2] ^[3] .

An example of writing an Encounter code.

The code, together with the location where it is located, serves as a control point .

The complexity of the search code depends on the complexity of the game. Usually the organizers draw pointers to the code in the form of arrows, which facilitate the search for the code. Either a graphic symbol or a designation of a project (for example, CX, EN, DR) is placed next to the arrow. In complex games, the code can be in a coal mine, a metallurgical plant, on a tower of a television tower.

Content

Code classification

An example of writing code in the game Dozor .

By influence on the outcome of the game

The main code is required to complete the task.
Bonus code - entering this code gives the team a bonus time.

At the place of writing

Usually one code refers to one task. Also possible:

Composite code - a set of basic codes of a single task (in the case of more than one code).
Collective code - parts of the code are distributed by location.
Runaway code - parts of the code are distributed in different locations, with the first one being sent to the next one.

By way of writing

Usually codes are written with paint or marker , besides that there are:

UV code - written with a special marker or paint, visible only when illuminated with ultraviolet light .
Glowing code - written in phosphorescent paint, visible only in complete darkness ^[4] .
Not a standard - writing a code is different from the accepted content (for example, the code does not use the designation of the project, or the code is presented in the form of a crossword puzzle or a rebus) or a way of writing (for example, the code is executed using volumetric characters and is located to the touch).

In relation to the participants

Usually, authors use common codes on locations, but personal and dynamic codes sometimes make it possible to reveal the unfair play of some teams ^[5] .

General code - the code valid for all participants in the game.
Personal code - a code provided for a specific participant or team.
Dynamic code - the code is changed by the authors during the game. The location of the code does not change, and the code for each command is new.
Grail - the code can be taken only by one of the teams. Usually performed as a bonus mission.

Notes

↑ See p.2 of the rules of the game Fight (rus.) . The appeal date was July 17, 2009. Archived June 28, 2012.
↑ See clause 2.3 of the Encounter game rules (rus.) . Archived June 28, 2012.
↑ See p. 6.6 of the rules of the game DozoR (rus.) . The appeal date was July 17, 2009. Archived June 28, 2012.
↑ Glowing codes
↑ Evgeny Shaposhnikov. Plums and inter-command "help" (rus.) . Encounter project. The appeal date is November 13, 2009.

Literature

Articles on coding objects .

Links

Frequently asked questions about the game DozoR (rus.) . The appeal date is July 17, 2009. Archived May 19, 2012.

Description of the game "Fight" (rus.) . The appeal date is July 17, 2009. Archived May 19, 2012.

[1] See p.2 of the rules of the game Fight (rus.) . The appeal date was July 17, 2009. Archived June 28, 2012.

[2] See clause 2.3 of the Encounter game rules (rus.) . Archived June 28, 2012.

[3] See p. 6.6 of the rules of the game DozoR (rus.) . The appeal date was July 17, 2009. Archived June 28, 2012.

[4] Glowing codes

[5] Evgeny Shaposhnikov. Plums and inter-command "help" (rus.) . Encounter project. The appeal date is November 13, 2009.