-
Notifications
You must be signed in to change notification settings - Fork 19
Home
Adapted from DevotedMC Wiki
See also Civclassic external Wiki
- Citadel - A Minecraft plugin to protect your chests and builds using in-game materials. Requires an attacker to break each block a certain number of times.
- Namelayer - A Citadel reinforcement group manager. Allows the creation of groups in Minecraft. From buildings to chat messages, one can selectivity restrict or expand which players have access.
See also
- Factorymod - More efficient item production - configured on CivClassic as the method to produce bastions
Bastions are a block that when placed prevent certain player actions such as block placements for players in range and not on the bastion Namelayer group. The bastions effects apply to an admin configurable horizontal range centered on the bastion block and from the bastion y level or the y level above the bastion up to sky limit. Bastion range shapes can be square or circular.
Bastions have health, which can be degraded by block placements (or anything else the bastion is admin-configured to block : e.g. ender pearls or elytra) from players not on the bastion Namelayer group, and checked with the command /bsi. When this health reaches zero, the bastion is broken and its effects no longer apply. Health can be admin configured to heal a certain amount of hitpoints daily, which can be used to negate minor daily damage from compounding and completely eroding the bastion. Bastions have an admin configurable maturation time, in which they take vastly increased hitpoint damage. Additionally during this time certain bastion effects can be disabled, for example on CivClassic maturing bastions will not block ender pearls from being thrown. This can help prevent their power as an offensive tool.
The config allows for multiple bastion types, each with different attributes. For example CivClassic has a vault bastion with a short range and powerful effects and a city bastion with a much larger range yet less powerful effects.
After a player damages a bastion there is a short configurable cooldown before they are able to damage the bastion again. Multiple players can damage a single bastion simultaneously. Damage to maturing bastions can be calculated as (finalScaleFactor - startScaleFactor)*(TimeSincePlaced/warmUpTime+startScaleFactor).
The 'ScaleFactor' option is present for all means of damaging bastions : block placements, elytra and pearling.
If action damaging bastion health is performed on an area where multiple bastion fields intersect, all bastions that effect the block in question are damaged.
'onlyDirectDestroy' option means bastion must be mined and cannot be broken via block placements. 'destroyOnRemove' option means the bastion block will be deleted after its hitpoints have been destroyed.
- Block placements
- If 'blockReinforcements' is set to false, blocks can be placed inside field yet they cannot be reinforced (See Citadel)
- Pearls
- 'block: true' means pearls landing in a bastion field will not teleport player, 'blockMidair: true' means any pearls thrown will be instantly used and no teleportation will occur, 'allowPearlingOut: true' means pearls will not be blocked if they are thrown from within the bastion field to outside the bastion field.
- Elytra
- Piston extensions causing block to enter bastion field
- Lava and water from flowing into bastion field
- Dispensers dispensing liquids are also blocked.
- Exiled players from entering bastion field
- (See ExilePearl)
- Entities (including falling entities such as sand when launched inside bastion field from outside)
- Dragon eggs
- Bonemeal usage
| Command | Explanation |
|---|---|
| /bsi | (INFO mode) Using USE key on block within a bastion field displays whether a bastion is present and if player is added to bastion 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. |
| /bsl | Displays list of all bastions player is on Namelayer group for and their type and location |
| /bsga | 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 |
| /bsgd | Removes a previously allowed group from a Bastion's Namelayer group |
| /bsgl | Lists all the allowed groups in a Bastion's Namelayer group |
Warning : Some of these commands do not appear to work as intended and can result in the loss of bastions.
| Command | Explanation |
|---|---|
| /bsf | Allows you to reinforce a sponge block without turning it into a bastion. Note: After this command is used, it may not be possible to turn sponge block back into bastion - the /bsb command does not appear to work. If you wish to display a bastion block without it applying an effect, simply place it down without reinforcing |
| /bsb | (BASTION mode) Any reinforced target sponge block will become a Bastion Block. Note: This does not appear to work : if one wishes to place a bastion block they should simply place in normal mode, which requires no command. |
| /bsd | (DELETE mode) Click bastions to delete them Note: This does not appear to serve a function - if one wishes to remove a bastion they own they can simply mine the bastion and do not have to delete the block and in the process lose the bastion. |
| /bso | (NORMAL mode) Changes all bastion modes to normal. Note: Is not needed unless one is using DELETE or BASTION modes, which are also necessary. One can place bastions without using any bastion command, simply by reinforcing the bastion block. |
| /bsc | No longer a command |
To-Do
- More extensive list of what gets blocked and what does not
- Is water flowing into bastion field actually prevented? When?
- What is the purpose of having both 'blockMidair' and 'allowpearlingout' ?
- Examples of /bsga instead of managing namelayer command directly.
- Explain blocksToErode and erosionPerDay
- cc config marks onlyDirectDestroy as true for city bastions - is this accurate?
- startScaleFactor and finalScaleFactor - do these apply to block placements or maturation e.t.c