Swift Hold - Revision history

Cinero: /* ICE */

2026-04-23T00:38:20Z

‎ICE

Cinero: /* Possible Actions */

2022-06-18T20:43:10Z

‎Possible Actions

Cinero: /* Gates, Keys, and Maps */

2022-06-18T20:42:39Z

‎Gates, Keys, and Maps

Cinero: /* Nodes */

2022-06-18T20:42:12Z

‎Nodes

Cinero: /* Holders */

2022-06-18T20:41:20Z

‎Holders

Cinero: /* Types of Holds */

2022-06-18T20:40:28Z

‎Types of Holds

Cinero: /* Defining Ideal */

2022-06-18T20:39:41Z

‎Defining Ideal

Cinero at 20:38, 18 June 2022

2022-06-18T20:38:20Z

Cinero at 20:38, 18 June 2022

2022-06-18T20:38:11Z

Cinero at 19:16, 18 June 2022

2022-06-18T19:16:23Z

@@ Line 47: / Line 47: @@
 Different kinds of ICE specialize in different roles:
-* '''Foreman''': supervisors workers and other ICE
+* '''Foreman''': supervises workers and other ICE
 * '''Prowler''': patrols the hold
 * '''Sentry''': guards the perimeter or a sensitive location

@@ Line 79: / Line 79: @@
 Here are some possible actions in a Swift hold:
-* Charm a holder (e.g., cast ‘’Charm Person’’)
+* Charm a holder (e.g., cast ''Charm Person'')
-* Hide from a holder (e.g., use the Hide action, cast ‘’Invisibility’’)
+* Hide from a holder (e.g., use the Hide action, cast ''Invisibility'')
 * Pickpocket a key or map (e.g., use Sleight of Hand) (Remember that only some holders have maps.)
-* Pretend to be a holder (e.g., cast ‘’Alter Self’’)
+* Pretend to be a holder (e.g., cast ''Alter Self'')
-* Sneak by ICE (e.g., use Stealth, cast ‘’Pass Without Trace’’)
+* Sneak by ICE (e.g., use Stealth, cast ''Pass Without Trace'')
 [[Category:Idea]]
 [[Category:Magic]]
 [[Category:Technology]]

@@ Line 70: / Line 70: @@
 == Gates, Keys, and Maps ==
-In a secure hold, the links between nodes are often blocked by gates. Holders carry keys to pass through the gates. Different gates may require different keys. Based on their responsibilities and necessary movements, different holders often have different keys.
+In a secure hold, the links between nodes are often blocked by gates. Holders carry keys to pass through the gates. Different gates may require different keys. Based on their responsibilities and necessary movements, different holders may have different keys.
 Some holders don’t move between nodes, or only know specific node-to-node paths. However, some holders carry a map of the whole hold.

@@ Line 62: / Line 62: @@
 * '''Tool Node''': controls devices on the Grid (e.g., an elevator)
 * '''Transit Node''': allows beings and/or information to move in and out of the hold
-* '''UX Node''': User Experience: manages interactions with the Swift hold (e.g., displays a login screen)
+* '''UX Node''' (User Experience): manages interactions with the hold (e.g., displays a login screen)
 A node’s security rating is usually between 5-30. When an unauthorized visitor tries interact with a node, they may need to overcome the security first.

@@ Line 35: / Line 35: @@
 There are generally two kinds of holders:
-* Workers
+* '''Workers'''
 ** Non-combatants
 ** Focus on the “business” of the hold, whatever that may be
 ** Example: the Fey spirits who clean and maintain a Seldarine sacred grove
-* Intrusion Countermeasures (ICE)
+* Intrusion Countermeasures ('''ICE''')
 ** Combatants
 ** Manage access to the hold and movement throughout it

@@ Line 21: / Line 21: @@
 There are many types of Swift holds, including:
-* '''Blighthold''': an area conjoined with devastation on the Grid. Example: ground zero after a major explosion.
+* '''Blighthold''': an area conjoined with devastation on the Grid (e.g., ground zero after a major explosion)
-* '''Faith hold''': holy ground. Example: a temple.
+* '''Faith hold''': holy ground (e.g., a temple)
-* '''Lorehold''': an area that is particularly dense with information. Example: a library.
+* '''Lorehold''': an area that is particularly dense with information (e.g., a library)
-* '''Spirithold''': an area claimed by one or more spirits. Example: a city spirit’s home.
+* '''Spirithold''': an area claimed by one or more spirits (e.g., a city spirit’s home)
-* '''Stronghold''': an area secured against unwanted visitors. Example: an internet security company.
+* '''Stronghold''': an area secured against unwanted visitors (e.g., an internet security company)
 == Holders ==

@@ Line 13: / Line 13: @@
 The defining ideal can come from a consciousness. Only a powerful consciousness can create and maintain a Swift hold. Beings with this capacity include but aren’t limited to: powerful fiends, celestials, spirits, and undead.
-In addition or instead, the ideal can be the influence of a powerful and/or ongoing phenomenon. This especially includes holy ground. For example, a Swift hold can be created and maintained through the faith of many lesser beings. Such beings may not even realize what they’re doing. “Holy” is a relative term: faith of any kind can shape the Swift (e.g., a demonic cult).
+In addition or instead, a hold can be created and maintained through the faith of many lesser beings. Such beings may not even realize what they’re doing.
 == Types of Holds ==

@@ Line 5: / Line 5: @@
 A Swift hold is an area of the Swift with a strongly-defined landscape and/or architecture.
-Like anywhere in the Swift, a Swift hold is still tied to the Grid (i.e., the closest plane). It’s also still the border of many other planes (e.g., Ethereal). However, a hold is distinguished by a singular ideal, called the '''defining ideal'''.
+Like anywhere in the Swift, a Swift hold is still tied to the Grid (i.e., the closest plane). It’s also still the border of many other planes (e.g., Ethereal). However, a hold is distinguished by a singular ideal, called the ''defining ideal''.
 == Defining Ideal ==

@@ Line 19: / Line 19: @@
 There are many types of Swift holds, including:
-* ‘’’Blighthold’’’: an area conjoined with devastation on the Grid. Example: ground zero after a major explosion.
+* '''Blighthold''': an area conjoined with devastation on the Grid. Example: ground zero after a major explosion.
-* ‘’’Faith hold’’’: holy ground. Example: a temple.
+* '''Faith hold''': holy ground. Example: a temple.
-* ‘’’Lorehold‘’’: an area that is particularly dense with information. Example: a library.
+* '''Lorehold''': an area that is particularly dense with information. Example: a library.
-* ‘’’Spirithold‘’’: an area claimed by one or more spirits. Example: a city spirit’s home.
+* '''Spirithold''': an area claimed by one or more spirits. Example: a city spirit’s home.
-* ‘’’Stronghold‘’’: an area secured against unwanted visitors. Example: an internet security company.
+* '''Stronghold''': an area secured against unwanted visitors. Example: an internet security company.
 == Holders ==
@@ Line 45: / Line 45: @@
 Different kinds of ICE specialize in different roles:
-* ‘’’Foreman’’’: supervisors workers and other ICE
+* '''Foreman''': supervisors workers and other ICE
-* ‘’’Prowler‘’’: patrols the hold
+* '''Prowler''': patrols the hold
-* ‘’’Sentry‘’’: guards the perimeter or a sensitive location
+* '''Sentry''': guards the perimeter or a sensitive location
-* ‘’’Trapper‘’’: restrains a hostile being
+* '''Trapper''': restrains a hostile being
 == Nodes ==
@@ Line 55: / Line 55: @@
 The types include:
-* ‘’’Data Node’’’: stores information
+* '''Data Node''': stores information
-* ‘’’Processing Node’’’: manipulates and changes information
+* '''Processing Node''': manipulates and changes information
-* ‘’’Sensor Node’’’: collects information from the Grid (e.g., from a security camera)
+* '''Sensor Node''': collects information from the Grid (e.g., from a security camera)
-* ‘’’Tool Node’’’: controls devices on the Grid (e.g., an elevator)
+* '''Tool Node''': controls devices on the Grid (e.g., an elevator)
-* ‘’’Transit Node’’’: allows beings and/or information to move in and out of the hold
+* '''Transit Node''': allows beings and/or information to move in and out of the hold
-* ‘’’UX Node’’’: User Experience: manages interactions with the Swift hold (e.g., displays a login screen)
+* '''UX Node''': User Experience: manages interactions with the Swift hold (e.g., displays a login screen)
 A node’s security rating is usually between 5-30. When an unauthorized visitor tries interact with a node, they may need to overcome the security first.