Enclosure - Revision history

Staffan Björk at 09:52, 13 May 2022

2022-05-13T09:52:04Z

Staffan Björk: /* Using the pattern */

2022-05-13T09:42:24Z

‎Using the pattern

Staffan Björk at 16:36, 9 August 2016

2016-08-09T16:36:08Z

Staffan Björk at 16:35, 9 August 2016

2016-08-09T16:35:27Z

Staffan Björk at 16:33, 9 August 2016

2016-08-09T16:33:36Z

Staffan Björk: /* Relations */

2016-08-09T16:26:10Z

‎Relations

Staffan Björk: /* Anti-Examples */

2016-08-09T16:16:26Z

‎Anti-Examples

Staffan Björk at 16:16, 9 August 2016

2016-08-09T16:16:13Z

Staffan Björk: /* Relations */

2016-08-09T16:08:49Z

‎Relations

Staffan Björk: /* Relations */

2016-08-09T16:06:12Z

‎Relations

@@ Line 18: / Line 18: @@
 == Consequences ==
-[[Enclosure]] is a type of [[Configuration]] which typically requires [[Connection]] between what is enclosed and what encloses it or between enclosing game elements. Succeeding with an [[Enclosure]] typically leads to a [[Capture]].
+[[Enclosure]] is a type of [[Configuration]] which typically requires [[Connection]] between what is enclosed and what encloses it or between enclosing game elements. Succeeding with an [[Enclosure]] typically leads to a [[Capture]] or succeeding with a [[Gain Ownership]] goal.
 == Relations ==
@@ Line 25: / Line 25: @@
 [[Connection]],
 [[Configuration]],
-[[Game Element Removal]]
+[[Game Element Removal]],
 === Can Modulate ===
 [[Game Element Insertion]],
 [[Movement]]

@@ Line 15: / Line 15: @@
 == Using the pattern ==
-Designing for [[Enclosure]] goals are primarily concerns with what should be enclosed and what can be used to enclose. Typically in both cases these are (different types of) game elements but for the latter the goal of [[Enclosure]] influences the [[Game Element Insertion]] or [[Movement]] of these. Another concern is players should [[Gain Ownership]] of what is enclosed or if they should be removed through [[Game Element Removal]].
+Designing for [[Enclosure]] goals are primarily concerns with what should be enclosed and what can be used to enclose. Typically in both cases these are (different types of) game elements but for the latter the goal of [[Enclosure]] influences the [[Game Element Insertion]] or [[Movement]] of these. Another concern is whether players should [[Gain Ownership]] of what is enclosed or if they should be removed through [[Game Element Removal]].
 == Consequences ==

@@ Line 2: / Line 2: @@
 [[Category:Goal Patterns]]
 [[Category:Mechanical Patterns]]
 [[Category:Needs revision]]
 [[Category:Needs references]]
 [[Category:To be Published]]
 ''The goal of surrounding game elements by a continuous line or wall of other game elements.''

@@ Line 11: / Line 11: @@
 [[Category:Staffan's current workpage]]
 ''The goal of surrounding game elements by a continuous line or wall of other game elements.''
 === Examples ===

@@ Line 11: / Line 11: @@
 [[Category:Staffan's current workpage]]
 ''The goal of surrounding game elements by a continuous line or wall of other game elements.''
 === Examples ===
-Example: Loop, by gameLab, is an example of how Enclosure can be a visually very strong element. In this game there are several butterflies of different color fluttering around the screen. The player's task is to enclose butterflies of the same color by drawing a loop with a mouse around two or more butterflies of the same color. The player can also enclose three or more butterflies if each of them is of a different color.
+The oldest, and perhaps best known, example of [[Enclosure]] is [[Go]] in which completely enclosing the opponent's group when it has no empty space inside it causes it to be removed from the board. The board game [[Carcassonne]] uses [[Enclosure]] in a couple of different ways: the building of towns where rewards are not given until the town walls enclose the area inside; cloisters that have to be surrounding by tiles to give points; and fields that may be enclosed to guarantee control.
-Example: The board game Carcassonne (Klaus-Jürgen Wrede 2000) is a clear example of using Enclosure in a couple of different ways: the building of towns where rewards are not given until the town walls enclose the area inside; cloisters that have to be surrounding by tiles to give points; and fields that may be enclosed to guarantee control.
+In [[Qix]] game elements are captured and removed from play by enclosing them in the smaller of the two subdivisions that are created whenever the player completes a line between two parts of the game edge. [[Nibbler]] and [[Snake]] are examples where avoiding an [[Enclosure]] lets players survive to pursue the primary goal of eating.
 == Using the pattern ==

@@ Line 29: / Line 29: @@
 == Relations ==
 === Can Instantiate ===
 [[Capture]],
@@ Line 39: / Line 36: @@
 === Can Modulate ===
-[[Gain Ownership]]
+[[Gain Ownership]],
 === Can Be Instantiated By ===

← Older revision		Revision as of 16:16, 9 August 2016
Line 21:		Line 21:

	Example: The board game Carcassonne (Klaus-Jürgen Wrede 2000) is a clear example of using Enclosure in a couple of different ways: the building of towns where rewards are not given until the town walls enclose the area inside; cloisters that have to be surrounding by tiles to give points; and fields that may be enclosed to guarantee control.		Example: The board game Carcassonne (Klaus-Jürgen Wrede 2000) is a clear example of using Enclosure in a couple of different ways: the building of towns where rewards are not given until the town walls enclose the area inside; cloisters that have to be surrounding by tiles to give points; and fields that may be enclosed to guarantee control.
−
−	~~==== Anti-Examples ====~~
−	~~optional~~

	== Using the pattern ==		== Using the pattern ==

@@ Line 36: / Line 36: @@
 == Relations ==
-Instantiates: Connection, Configuration
+Instantiates: [[Connection]], [[Configuration]]
 [[Capture]]