############################################################
# +------------------------------------------------------+ #
# | Notes | #
# +------------------------------------------------------+ #
############################################################
# If you want to use special characters in this document, such as accented letters, you MUST save the file as UTF-8, not ANSI.
# If you receive an error when Essentials loads, ensure that:
# - No tabs are present: YAML only allows spaces
# - Indents are correct: YAML hierarchy is based entirely on indentation
# - You have "escaped" all apostrophes in your text: If you want to write "don't", for example, write "don''t" instead (note the doubled apostrophe)
# - Text with symbols is enclosed in single or double quotation marks
# If you have problems join the Essentials help support channel:
http://tiny.cc/EssentialsChat
############################################################
# +------------------------------------------------------+ #
# | Essentials (Global) | #
# +------------------------------------------------------+ #
############################################################
# A color code between 0-9 or a-f. Set to 'none' to disable.
ops-name-color: 'none'
# The character(s) to prefix all nicknames, so that you know they are not true usernames.
nickname-prefix: ''
# Disable this if you have any other plugin, that modifies the displayname of a user.
change-displayname: true
# When this option is enabled, the (tab) player list will be updated with the displayname.
# The value of change-displayname (above) has to be true.
#change-playerlist: true
# Adds the prefix and suffix to the displayname of the player, so it will be displayed in messages and lists.
# The prefix/suffix can be set using Permissions, Group Manager or PermissionsEx.
# The value of change-displayname (above) has to be true.
# If you don't set this, it will default to true if essentials chat is installed.
# Don't forget to remove the # in front of the line
#add-prefix-suffix: false
# The delay, in seconds, required between /home, /tp, etc.
teleport-cooldown: 3
# The delay, in seconds, before a user actually teleports. If the user moves or gets attacked in this timeframe, the teleport never occurs.
teleport-delay: 1
# The delay, in seconds, a player can't be attacked by other players after they have been teleported by a command
# This will also prevent the player attacking other players
teleport-invulnerability: 2
# The delay, in seconds, required between /heal attempts
heal-cooldown: 60
# What to prevent from /i /give
# e.g item-spawn-blacklist: 46,11,10
item-spawn-blacklist:
# Set this to true if you want permission based item spawn rules
# Note: The blacklist above will be ignored then.
# Permissions:
# - essentials.itemspawn.item-all
# - essentials.itemspawn.item-[itemname]
# - essentials.itemspawn.item-[itemid]
# - essentials.give.item-all
# - essentials.give.item-[itemname]
# - essentials.give.item-[itemid]
permission-based-item-spawn: false
# Mob limit on the /spawnmob command per execution
spawnmob-limit: 1
# Shall we notify users when using /lightning
warn-on-smite: true
# motd and rules are now configured in the files motd.txt and rules.txt
# When a command conflicts with another plugin, by default, Essentials will try to force the OTHER plugin to take priority.
# Commands in in this list, will tell Essentials to 'not give up' the command to other plugins.
# In this state, which plugin 'wins' appears to be almost random.
#
# If you have two plugin with the same command and you wish to force Essentials to take over, you need an alias.
# To force essentials to take 'god' alias 'god' to 'egod'.
# See
http://wiki.bukkit.org/Bukkit.yml#aliases for more information
overridden-commands:
# - god
# Disabled commands will be completely unavailable on the server.
# Disabling commands here will have no effect on command conflicts.
disabled-commands:
# - nick
# If you do not wish to use a permission system, you can define a list of 'player perms' below.
# This list has no effect if your using a supported permissions system.
# If your using an unsupported permissions system simply delete this section.
# Whitelist the commands and permissions you wish to give players by default (everything else is op only).
# These are the permissions without the "essentials." part.
player-commands:
- afk
- afk.auto
- back
- back.ondeath
- balance
- balance.others
- balancetop
- build
- chat.color
- chat.format
- chat.shout
- chat.question
- clearinventory
- compass
- depth
- delhome
- getpos
- geoip.show
- help
- helpop
- home
- home.others
- ignore
- info
- itemdb
- kit
- kits.tools
- list
- mail
- mail.send
- me
- motd
- msg
- msg.color
- nick
- near
- pay
- ping
- protect
- r
- rules
- realname
- seen
- sell
- sethome
- setxmpp
- signs.create.protection
- signs.create.trade
- signs.break.protection
- signs.break.trade
- signs.use.balance
- signs.use.buy
- signs.use.disposal
- signs.use.enchant
- signs.use.free
- signs.use.gamemode
- signs.use.heal
- signs.use.info
- signs.use.kit
- signs.use.mail
- signs.use.protection
- signs.use.repair
- signs.use.sell
- signs.use.time
- signs.use.trade
- signs.use.warp
- signs.use.weather
- spawn
- suicide
- time
- tpa
- tpaccept
- tpahere
- tpdeny
- warp
- warp.list
- world
- worth
- xmpp
enabledSigns:
- color
- balance
- buy
- sell
- trade
- free
- disposal
- warp
- kit
- mail
- enchant
- gamemode
- heal
- info
- spawnmob
- repair
- time
- weather
# How many times per second can Essentials signs be interacted with per player.
# Values should be between 1-20, 20 being virtually no lag protection.
# Lower numbers will reduce the possibility of lag, but may annoy players.
sign-use-per-second: 4
############################################################
# +------------------------------------------------------+ #
# | EssentialsProtect | #
# +------------------------------------------------------+ #
############################################################
protect:
# Database settings for sign/rail protection
# mysql or sqlite
# We strongly recommend against using mysql here, unless you have a good reason.
# Sqlite seems to be faster in almost all cases, and in some cases mysql can be much slower.
datatype: 'sqlite'
# If you specified MySQL above, you MUST enter the appropriate details here.
# If you specified SQLite above, these will be IGNORED.
username: 'root'
password: 'root'
mysqlDb: 'jdbc:mysql://localhost:3306/minecraft'
# General physics/behavior modifications
prevent:
lava-flow: true
water-flow: false
water-bucket-flow: false
fire-spread: true
lava-fire-spread: true
flint-fire: false
lightning-fire-spread: true
portal-creation: false
tnt-explosion: false
tnt-playerdamage: false
fireball-explosion: false
fireball-fire: false
fireball-playerdamage: false
creeper-explosion: false
creeper-playerdamage: false
creeper-blockdamage: false
enderdragon-blockdamage: true
enderman-pickup: false
villager-death: false
# Monsters won't follow players
# permission essentials.protect.entitytarget.bypass disables this
entitytarget: false
# Prevent the spawning of creatures
spawn:
creeper: true
skeleton: true
spider: true
giant: true
zombie: true
slime: true
ghast: true
pig_zombie: true
enderman: true
cave_spider: true
silverfish: true
blaze: true
magma_cube: true
ender_dragon: true
pig: true
sheep: true
cow: truee
chicken: true
squid: true
wolf: true
mushroom_cow: true
snowman: true
ocelot: true
iron_golem: true
villager: true
# Maximum height the creeper should explode. -1 allows them to explode everywhere.
# Set prevent.creeper-explosion to true, if you want to disable creeper explosions.
creeper:
max-height: -1
# Protect various blocks.
protect:
# Protect all signs
signs: false
# Prevent users from destroying rails
rails: false
# Blocks below rails/signs are also protected if the respective rail/sign is protected.
# This makes it more difficult to circumvent protection, and should be enabled.
# This only has an effect if "rails" or "signs" is also enabled.
block-below: true
# Prevent placing blocks above protected rails, this is to stop a potential griefing
prevent-block-on-rails: false
# Store blocks / signs in memory before writing
memstore: false
# Disable various default physics and behaviors
disable:
# Should fall damage be disabled?
fall: false
# Users with the essentials.protect.pvp permission will still be able to attack each other if this is set to true.
# They will be unable to attack users without that same permission node.
pvp: false
# Should drowning damage be disabled?
# (Split into two behaviors; generally, you want both set to the same value)
drown: false
suffocate: false
# Should damage via lava be disabled? Items that fall into lava will still burn to a crisp.
😉
lavadmg: false
# Should arrow damage be disabled
projectiles: false
# This will disable damage from touching cacti.
contactdmg: false
# Burn, baby, burn! Should fire damage be disabled?
firedmg: false
# Should the damage after hit by a lightning be disabled?
lightning: false
# Disable weather options
weather:
storm: false
thunder: false
lightning: false
