-
Notifications
You must be signed in to change notification settings - Fork 6
/
F_creuss.php
118 lines (107 loc) · 10.7 KB
/
F_creuss.php
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
<?php include "prefix.php"?>
<header>The Ghosts of Creuss</header>
<article>
<h1>Quantum Entanglement</h1>
<ol class="note">
<li>The effect of the <i>Enforced Travel Ban</i> law does not affect the Creuss player.</li>
<li>If the Creuss player has units or controls planets in a system with an alpha wormhole, and another player has units or controls planets in a system with an beta wormhole, or vice versa, then the Creuss player and that player are neighbors.</li>
<ol><li>The Mentak player may use their <sc>Pillage</sc> ability against the Creuss player in this manner.</li></ol>
<li>If Mecatol Rex contains an alpha wormhole, then the for effect of the <i>Ixthian Artifact</i> agenda will not affect the Creuss player’s units in a system with a beta wormhole (and no alpha wormhole), and vice versa.</li>
<li>The Creuss player’s <sc>Quantum Entanglement</sc> ability applies to their units with the <sc>Deep Space Cannon</sc> ability. Other players cannot use <sc>Quantum Entanglement</sc> to produce hits from a unit with the <sc>Deep Space Cannon</sc> ability against the Creuss player’s units.</li>
</ol>
<h1>Slipstream</h1>
<ol class="note">
<li><sc>Slipstream</sc> does not apply to the Creuss Gate or to the <i>Hil Colish</i>, or to gamma wormholes.</li>
</ol>
<h1>Creuss Gate</h1>
<ol class="note">
<li>A frontier token is placed in the Creuss Gate system during setup.</li>
<li>Both the Creuss Gate and the Creuss home system (in standard game board setups) are on the edge of the board.</li>
</ol>
<h1>Creuss IFF <sub>(Promissory Note)</sub></h1>
<ol class="note">
<li>A player may receive the <i>Creuss IFF</i> in a transaction during their turn. If received at the start of that player’s turn, that player may play it immediately.</li>
<ol>
<li>The active player may perform a transaction with each other player at most once per turn. As such, the active player cannot receive the <i>Creuss IFF</i> more than once per turn.</li>
<li>If the active player received the <i>Creuss IFF</i> on a previous turn, they may play it and immediately perform a transaction with the Creuss player to regain it. However, the <i>Creuss IFF</i> cannot be played twice in one timing window. The active player cannot play the <i>Creuss IFF</i> again until their next turn.</li>
</ol>
<li>Any deal between the Creuss player and another player regarding where the wormhole tokens will be placed, if made before the <i>Creuss IFF</i> is exchanged, is non–binding.</li>
<li>The <i>Creuss IFF</i> may be played even if the Creuss player has not researched <i>Wormhole Generator</i>.</li>
<li>The <i>Creuss IFF</i> cannot place wormhole tokens in the home system of an eliminated player.</li>
</ol>
<h1>Dimensional Splicer <sub>(Technology)</sub></h1>
<ol class="note">
<li>Any wormhole may trigger <i>Dimensional Splicer</i>, including the one produced by the ability of the <i>Hil Colish</i></li>
<li>One hit will be produced even if the system contains multiple wormholes.</li>
<li>The Creuss player chooses which ship the hit is assigned to.</li>
<li>The <i>Shields Holding</i> action card may be used to cancel the hit.</li>
<li>The chosen ship may cancel the hit by using its <sc>Sustain Damage</sc> ability, if present. A different ship with the <sc>Sustain Damage</sc> ability cannot do so.</li>
<ol>
<li>If the chosen ship does so, the <i>Direct Hit</i> and/or <i>Reflective Shielding</i> action cards may be used.</li>
</ol>
</ol>
<h1>Wormhole Generator <sub>(Technology)</sub></h1>
<ol class="note">
<li>This ability is mandatory for the Creuss player in every status phase after it has been researched.</li>
<ol><li>The Creuss player may move a wormhole token from the system it is in into the same system.</li></ol>
<li><i>Wormhole Generator</i> cannot place wormhole tokens in the home system of an eliminated player.</li>
</ol>
<h1>Wormhole Generator Ω <sub>(Technology)</sub></h1>
<ol class="note">
<li>The Creuss player may move a wormhole token from the system it is in into the same system.</li>
<li><i>Wormhole Generator</i> cannot place wormhole tokens in the home system of an eliminated player.</li>
</ol>
<h1>Hil Colish <sub>(Flagship)</sub></h1>
<ol class="note">
<li>If the <i>Hil Colish</i> moves first, then the Creuss player uses the new position of the <i>Hil Colish</i> when determining if the active system may be reached by their other ships.</li>
<li>If the <i>Hil Colish</i> moves last, then it may move itself into (or though, if its move value is increased) the Creuss Gate or Creuss home system. Before it does so, the Creuss player’s other ships may move through the wormhole created by the <i>Hil Colish</i>.</li>
<ol><li>The delta wormhole moves with the <i>Hil Colish</i>; it cannot move back to its origin system using its own delta wormhole.</li></ol>
<li>The Creuss player must declare all ships that will moving before they move the <i>Hil Colish</i> or their other ships. They then declare the path that the first ship(s) to move will travel along, and move those ship(s). Then then declare the path that the other ship(s) to move will travel along, and move those ships. Any ships that were declared to move must, if it is possible to do so.</li>
<ol>
<li>If the <i>Hil Colish</i> is moved first, and is removed due to the effect of a gravity rift, other ships that were declared to move that can reach the destination system must do so, even if the path is through the gravity rift. Ships that cannot reach the active system do not move.</li>
<li>The Creuss player cannot wait to see the result of their other ships’ gravity rift rolls before deciding to move the <i>Hil Colish</i>; they must declare if the <i>Hil Colish</i> is moving at the same time they declare which other ships are moving.</li>
</ol>
<li>If the <i>Hil Colish</i> moves before or after other ships, it does not generate a second <b>Space Cannon Offense</b> step.</li>
<li>A unit with the <sc>Deep Space Cannon</sc> ability may produce hits in systems adjacent to that unit via the delta wormhole in the <i>Hil Colish</i>’s system. Most commonly, this will allow the Creuss player to target units in the <i>Hil Colish</i>’s system from the space cannon rolls of units in their home system.</li>
<li>If an effect allows another player to move through a system that contains the Creuss player’s ships (such as the <i>Light/Wave Deflector</i> technology), that player may move through the delta wormhole in the <i>Hil Colish</i>’s system.</li>
<li>During space combat involving the <i>Hil Colish</i>, either player may retreat to another system containing a delta wormhole, if that system meets the other requirements for retreating.</li>
<ol><li>If the <i>Hil Colish</i> is destroyed between the <b>Announce Retreats</b> step and the <b>Retreat</b> step, then the retreating player must retreat to a different eligible system. If no such system exists, then their retreat is cancelled.</li></ol>
<li>When the <i>Hil Colish</i> retreats, it may retreat before or after the Creuss player’s other ships, but cannot retreat in such a way that would prevent the other ships from retreating to the same system.</li>
</ol>
<h1>Emissary Taivra <sub>(Agent)</sub></h1>
<ol class="note">
<li>The Creuss player may use this ability to access the inactive wormhole nexus without a gamma wormhole. Moving ships into the wormhole nexus this way will cause it to flip.</li>
<li>A delta wormhole in the system (such as from the <i>Hil Colish</i>) does not prevent this ability from being usable.</li>
<li>If this ability is used, the active system will be adjacent to systems with delta wormholes.</li>
<li>If a ship moves from the system containing the Ion Storm, it will not flip, unless the active player may move ships through the Ion Storm wormhole and chooses to do so.</li>
<li>The system must have a non–delta wormhole in it at the moment of activation. If a wormhole is placed in a system with no other wormholes using the ability of an Icarus Drive, then Emissary Taivra cannot be used during the same activation.</li>
<ol><li>If a wormhole is placed at the start of a player’s turn in the system using the Creuss IFF, then Emissary Taivra may be used for the activation immediately following.</li></ol>
</ol>
<h1>Sai Seravus <sub>(Commander)</sub></h1>
<ol class="note">
<li>The fighters are placed one at a time, until either one has been placed for each ship with capacity that moved through a wormhole, or the capacity of the system is reached.</li>
<ol>
<li>The Creuss player cannot remove a ground force to create capacity for a fighter.</li>
<li>The Creuss cannot place additional fighters once they have fighters and infantry in the space area equal to their capacity in that system, even if they have unused fleet pool and the fighter II unit upgrade technology.</li>
<li>If the Creuss player has a space dock in the active system, they may consider some of the fighters they place as held by the space dock, in order to continue placing fighters.</li>
</ol>
<li>This ability may be used whenever the Creuss player’s ships move, not just during the movement step of a tactical action.</li>
<ol>
<li>While this ability would trigger after the Creuss player retreats, retreating will leave no capacity in the active system.</li>
<li>If the Mahact player uses their <i>Benediction</i> hero ability to move the Creuss player’s ships, then the Creuss player may use this ability.</li>
</ol>
<li>A ship may move out of a system and back into the same system during tactical action movement, if its move value is high enough. If the Creuss player does this with a ship with capacity, and moves in this manner via a wormhole, they may place a fighter, if possible.</li>
<li>When the Creuss player moves a ship through a wormhole, ending in a system that contains an alpha or beta wormhole and unlocks Sai Seravus, they cannot apply its ability to that movement.</li>
<ol><li>If the Creuss player moves the <i>Hil Colish</i> separately from other ships during the same <b>Move Ships</b> step, Sai Seravus cannot unlock until all movement is completed.</li></ol>
</ol>
<h1>Riftwalker Meian — Singularity Reactor <sub>(Hero)</sub></h1>
<ol class="note">
<li>Any units and tokens on either system are moved with their system.</li>
</ol>
<h1>Icarus Drive <sub>(Mech)</sub></h1>
<ol class="note">
<li>The Icarus Drive does not have to be in the activated system.</li>
<li>The wormhole token is placed in the system the Icarus Drive was in.</li>
</ol>
</article>
<?php include "suffix.php"?>