Bastion: Difference between revisions

379 bytes removed ,  7 months ago
remove header
(code blocks)
(remove header)
(6 intermediate revisions by the same user not shown)
Line 11:
 
Note that due to the high creation cost of bastions, it makes little sense to reinforce them with anything other than diamond.
 
 
{| class="wikitable"
Line 75 ⟶ 74:
 
{| class="wikitable"
|-+
|+Bastions comparison
!Name
!Break time
Line 121 ⟶ 120:
 
50% of the damage dealt to vault bastions will also be inflicted on all other bastions within a 5 blocks radius (center block + 5) from the vault bastions which were not affected by the initial damage.<ref>https://www.reddit.com/r/civclassics/comments/ggtkdx/changelog_20200510/</ref>
 
 
== Placement Tips ==
Line 127 ⟶ 125:
=== Overlapping Fields ===
 
[[File:Hjaltland Vault 09.24.17.png|thumb|[[Hjaltland]]'s vault ason it stood in September 2017[[CivClassic]]. UseThe use of overlapping bastion fields makes advancingit difficult to break through even a single ring difficult.]]
 
While it is efficient to spread bastions out, defensive structures make use of overlapping bastion fields to ensure breaking a single bastion won't grant the breaker access to a full 21*21 area. In open spaces, blocks placed in the overlap would be a liability (since both bastions would take full damage) but vaults use walls and other physical barriers to prevent attackers from doing so. Immense subdivision and traps make ground assaults against such a structure difficult.
Line 133 ⟶ 131:
[[File:Skybunker Bastions.png|thumb|Only two layers protect this skybunker, but they provide a large and durable area of safety for defenders.]]
 
One other form of field overlap involves the vertical dimension. You can protect an area in the sky (typically at sky limit, but not always) by forcing attackers to break one bastion at a time. This is achieved by separating bastion layers by 8 blocks (to prevent mining) and moving each successive layer one block diagonally away from the center. Unless they can find a way to place bastions closer to the center (either on the outside of your structure or on top of it) they can only break a single bastion layer at a time.
 
== Glitches ==
 
=== Block glitching ===
Although vault bastions remove block placements, placed blocks can be walked on for a tick. This can be used, for example, to pillar out of holes inside vault bastion fields.
 
[[Mainline]] servers have been mixed on allowing block glitching.
Vault bastions remove block placements, yet for a tick the block appears as normal. Server rules allow using block glitching to pillar out from holes. Block glitching more than a few blocks high is possible although timings make it difficult.
 
=== Exile glitching ===
 
ExileExiled players are teleported outside of bastion fields. WithBy aligning bastion fields in a correctcontiguous setupline, thisplayers can allowuse teleportationthis overto teleport large distances. This is generally against server rules.
 
 
== Command Reference ==
Line 153 ⟶ 151:
!Description
|-
|<code><code>/bslhelp bastion</code>
|Lists all Bastion commands.
|Displays list of all bastions player is on Namelayer group for and their type, location and maturity
|-
|<code>/bsga <group>bsl</code>
|DisplaysLists list of allthe bastions the player is on Namelayerthe [[NameLayer]] group forof, andincluding their type, location, and maturity.
|-
|<code>/bsi</code>
|(INFOEnters bastion info mode). UsingRight USE keyclicking on block within a bastion fieldblock displays whether a bastion is present and if player is addedon tothat bastion's group. If the bastion block itself is clicked, the bastions maturity is shown : e.g. "Bastion: Some Strength" if maturing and a percentage equal to however much health of the bastion remains.
|-
|<code>/bsga <group></code>
| Add a Namelayer group to a set of "allowed to build" groups for a Bastion's Namelayer group. People on are thus able to build on areas covered by the bastions on . The person running command does not need to be on the added namelayer group.
|-
|<code>/bsgd <group></code>
|Removes a previously allowed group from a Bastion's Namelayer group
|-
|<code>/bsgl <group></code>
|list allowed groups in bastion groups
|}{{Template:Mechanics}}
2,287

edits