-
-
Save drtshock/705d40097e31d6eab625 to your computer and use it in GitHub Desktop.
Default HCFactions config.yml as of today.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# HCFactions by drtshock and milkywayz | |
# Report issues https://github.com/drtshock/HCFProblems/issues/new | |
# Live support http://webchat.esper.net/?channels=drtshock&prompt=1 | |
# Made with love <3 | |
# Debug | |
# Turn this on if you are having issues with something and working on resolving them. | |
# This will spam your console with information that is useful if you know how to read the source. | |
# It's suggested that you only turn this on at the direction of a developer. | |
debug: false | |
# Prevent find factions exploit | |
# This will help limit how many times a player can be sent a map of factions. | |
# Set this to the cooldown you want, in miliseconds, for a map to be shown to a player. | |
# If you want to log when a player violates this (only happens on chunk enter so it shouldn't be too spammy), | |
# set log to true and it will be logged to console as "player tried to show a faction map too soon and triggered exploit blocker." | |
findfactionsexploit: | |
cooldown: 2000 # in miliseconds. 2000 = 2 seconds. | |
log: false | |
# Default Relation allows you to change the default relation for Factions. | |
# Example usage would be so people can't leave then make a new Faction while Raiding | |
# in order to be able to execute commands if the default relation is neutral. | |
# This has always been neutral. | |
default-relation: "neutral" | |
# Portal Creation | |
# Do you want to limit portal creation? | |
portals: | |
limit: false # will disable the below check if set to false | |
# What should the minimum relation be to create a portal in territory? | |
# Goes in the order of: ENEMY, NEUTRAL, ALLY, MEMBER. | |
# Minimum relation allows that and all listed to the right to create portals. | |
# Example: put ALLY to allow ALLY and MEMBER to be able to create portals. | |
minimum-relation: MEMBER # If typed incorrectly, defaults to NEUTRAL. | |
# Warps | |
# What should be the max amount of warps that a Factoin can set? | |
max-warps: 5 | |
# This is the cost section for warps. | |
# It will charge them each time the command would be successful. (won't charge on erroneous /f warp attempts). | |
# You can use decimal places here. | |
# If enabled is set to false, it will ignore the values. | |
warp-cost: | |
enabled: false | |
setwarp: 5.0 | |
delwarp: 5.0 | |
warp: 5.0 | |
# Pistons | |
# Should we disable pistons in Faction territory? This will prevent people from doing something like: | |
# http://i.gyazo.com/6a1a31222e58a5d60ff341c13f6a8404.gif | |
disable-pistons-in-territory: false | |
# ToolTips | |
# This section is to configure tooltips for things like /f list | |
tooltips: | |
# List | |
# This shows up when someone does /f list for the top factions. | |
# It will not sure up for factionless of course, just actual factions. | |
# You can use color codes here. | |
list: | |
- "&6Leader: &f{leader}" | |
- "&6Claimed: &f{chunks}" | |
- "&6Raidable: &f{raidable}" | |
- "&6Warps: &f{warps}" | |
- "&6Members: &f{online}/{members}" | |
# Show | |
# This shows up when someone does /f show. | |
# It adds tooltips to each player in the list here, nothing else. | |
# {group} will show the players primary group if you have vault installed. | |
# {balance} will show their balance if you have vault installed. | |
# {lastSeen} will show human readable info on when the player was last seen, or online. | |
show: | |
- "&6Last Seen: &f{lastSeen}" | |
- "&6Rank: &f{group}" | |
- "&6Balance: &a${balance}" | |
# Configuration section for Scoreboards | |
# This will allow you to completely customize how your scoreboards look. | |
# Make sure that no lines are duplicates of each other otherwise only the first will display. | |
# Use &0-9a-f for colors and include messages in "quotes" | |
scoreboard: | |
# How long do we want scoreboards to stay if set temporarily. | |
expiration: 7 | |
# FInfo scoreboard is displayed when a player walks into a new Faction's territory. | |
# Scoreboard disappears after <expiration> seconds. | |
# Things to be replaced in this: | |
# {chunks} - total claimed chunks. {members} - total members. | |
# {online} - online members. {leader} - faction's leader. {open} - shows either true or false if open. | |
# {raidable} - true if the faction can be claimed over, otherwise false. | |
# {warps} - the number of warps that a faction has set. | |
# The title of the scoreboard will be the Faction's tag and colored according to the relation with the player's Faction. | |
# Commenting this section out will cause the info to appear in chat as the plugin originally did. | |
finfo-enabled: false # Default to false to keep original functionality. | |
finfo: | |
- "&3Members" | |
- "{online}/{members}" | |
- "&4Leader" | |
- "{leader}" | |
- "&bTerritory" | |
- "{chunks}" | |
# Default board that will always show up if a player wants it to. | |
# This can show any arbitrary text or you can use a lot of variables to replace things. | |
# Replace {name} - player's name. {faction} - player's faction title, factionless if none. | |
# {totalOnline} - total players on the server. {balance} - player's balance. | |
# {maxPower} - player's max power. | |
# {powerBoost} - player's powerboost. | |
default-enabled: false # Default to false to keep original functionality. | |
default-title: "i love drt" # Can use any of the values from above but this won't update once it's set (so don't set {balance}). | |
default-update-interval: 2 # in seconds. | |
# This will show faction prefixes colored based on relation on nametags and in the tab. | |
# The scoreboard needs to be enabled for this to work. | |
default-prefixes: true | |
default: | |
- "&6Your Faction" | |
- "{faction}" | |
- "&aBalance" | |
- "${balance}" | |
# Configration section for warmups. | |
# Warmup times are in seconds - if a value of 0 is set, there is no warmup. | |
warmups: | |
# Delay for /f home | |
f-home: 0 | |
# Delay for /f warp | |
f-warp: 0 | |
# Max Relation Types | |
# Limits factions to having a max number of each relation. | |
# Setting to 0 means none allowed. -1 for disabled. | |
# This will have no effect on default or existing relations, only when relations are changed. | |
# It is advised that you set the default relation to -1 so they can always go back to that. | |
# Otherwise Factions could be stuck with not being able to unenemy other Factions. | |
max-relations: | |
enabled: false | |
ally: 10 | |
truce: 10 | |
neutral: -1 | |
enemy: 10 | |
# WorldBorder support | |
# A buffer of 0 means faction claims can go right up to the border of the world. | |
# The buffer is in chunks, so 1 as a buffer means an entire chunk of buffer between | |
# the border of the world and what can be claimed to factions | |
world-border: | |
buffer: 0 | |
# Configurable f show output | |
# Order in list does not matter, this does not let you re-arrange the output | |
# Only allows you to disable certain messages you dont want | |
# To change the actual text, visit the lang.yml file and find the corresponding keys | |
# Variables: | |
# {description}, {joining}, {peaceful?}, {land}, {maxland}, {dtr}, {maxdtr}, | |
# {raidable}, {world}, {x}, {y}, {z}, {timeleft}, {value}, {refund}, {balance}, {allies}, | |
# {enemies}, {membersonline}, {membersoffline} | |
# | |
# | |
fshow: | |
- '<a>Description: <i>{description}' | |
- '<a>Joining: <i>{joining} {peaceful?}' | |
- '<a>Land / Max: <i> {land} / {maxland}' | |
- '<a>DTR: <i>{dtr} / {maxdtr} <a>Raidable: <i>{raidable}' | |
- '<a>Faction Home: <i>{world}, {x}, {y}, {z}' | |
- '<a>DTR Freeze: <i>{timeleft}' | |
- '<a>This faction is permanent, remaining even with no members.' | |
- '<a>Total land value: <i>{value} {refund}' | |
- '<a>Bank contains: <i>{balance}' | |
- 'Allies: {allies} ' | |
- 'Enemies: {enemies} ' | |
- 'Members online: {online}' | |
- 'Members offline: {offline}' | |
# Raids | |
# Allow a faction to be raided if their DTR is <= 0 | |
# This will make claimed territory lose all protections | |
# allowing factions to open chests, break blocks, etc. | |
hcf: | |
# DTR (death till raidable) will be in /f show if enabled. Configure the message in the lang.yml | |
# When DTR is below 0, the faction is considered raidable | |
# DTR is the sum of all faction member's DTR value, or MaxFactionDTR if it's larger | |
dtr: | |
# Maximum DTR a faction can have | |
max-faction-dtr: 5.5 | |
# How much DTR should we charge a faction for kicking a player when they are frozen | |
# Set to 0 to disable penalty, but remember a faction can kick low dtr players to remain unraidable if theres no penalty! | |
kick-penalty: 1.0 | |
# Minimum DTR a faction can have | |
min-faction-dtr: -6.0 | |
# How much DTR is lost on death | |
death-dtr: 1.0 | |
# How much DTR is replenished per faction member per minute | |
minute-dtr: 0.01 | |
# Maximum DTR a player can have | |
max-player-dtr: .51 | |
# DTR Freeze | |
# After a player dies, how long should the faction not be able to regen dtr? | |
# This resets on each death but does not accumulate. | |
# Set to 0 for no freeze. Time is in seconds. | |
dtr-freeze: 0 | |
# DTR Freeze background regeneration | |
# When a DTR freeze is started, current DTR will not change, but | |
# IF we set allow-background-regen to true, then after the freeze, | |
# the faction will have recovered the DTR that generated during the freeze. | |
# If set to false, then the DTR the faction would have generated during the | |
# DTR freeze period is simply ignored, so therefore a more harsh penalty :p | |
allow-background-regen: false | |
# Max land a faction can have claimed | |
faction-land-max: 40 | |
# How much land a faction gets per member | |
land-per-player: 5 | |
# Buffer Zone | |
# Buffer Zone is an chunk area required between claims of different Factions. | |
# This is default to 0 and has always been that way. Meaning Factions can have | |
# claims that border each other. | |
# If this is set to 3, then Factions need to have 3 chunks between their claim | |
# and another Faction's claim. | |
# It's recommended to keep this pretty low as the radius check could be a | |
# heavy operation if set to a large number. | |
# If this is set to 0, we won't even bother checking which is how Factions has | |
# always been. | |
buffer-zone: 0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment