mirror of
https://github.com/Xiao-MoMi/Custom-Crops.git
synced 2025-12-28 19:39:20 +00:00
143 lines
6.0 KiB
YAML
143 lines
6.0 KiB
YAML
# Don't change
|
|
config-version: '37'
|
|
# Debug
|
|
debug: false
|
|
# BStats
|
|
metrics: true
|
|
# Check updates
|
|
update-checker: true
|
|
# Force locale, for instance zh_cn
|
|
force-locale: ''
|
|
# World settings
|
|
worlds:
|
|
# Some servers use separate folders to store player worlds, and these world directories
|
|
# are often not located in the server's root directory. This option allows users to read
|
|
# world data from a custom directory. It is only applicable to Bukkit worlds.
|
|
absolute-world-folder-path: ''
|
|
# A list of worlds that would decide where the plugin mechanisms take effect
|
|
# Mode: whitelist/blacklist/regex
|
|
mode: blacklist
|
|
list:
|
|
- blacklist_world # A non-existent world
|
|
settings:
|
|
# Default settings that apply to all worlds
|
|
_DEFAULT_:
|
|
# Whether to enable the plugin's pre-made system
|
|
# Disabling this option will make all mechanisms stop counting ticks unless you have full control over it using the API.
|
|
# If you don't know how to code with CustomCropsAPI, just keep it true, because it is enough to meet the needs of 99% of users.
|
|
enable: true
|
|
# Season mechanisms
|
|
season:
|
|
enable: true
|
|
# Enable automatic seasonal change
|
|
auto-alternation: true
|
|
# Game days of each season
|
|
duration: 28
|
|
# It's different from the vanilla RandomTickSpeed.
|
|
# "Random tick" here refers to the process of randomly selecting n blocks within a 16x16x16 section every second to perform a tick while Minecraft do that every tick.
|
|
# Therefore, the random tick of CustomCrops has little impact on the server, and it is performed on multiple threads.
|
|
random-tick-speed: 20
|
|
# The smallest tick unit in seconds used in scheduled tick mode
|
|
# 300s means that a crop would be certainly ticked once in 300s
|
|
# For crops, under the same conditions, the growth rate of crops is basically the same
|
|
# For sprinklers and pots, they would work periodically.
|
|
min-tick-unit: 300
|
|
# Offline tick settings
|
|
# This option allows crops to grow even if the world is unloaded or the server is closed
|
|
# This may lead to some issues caused by timeliness conditions for instance seasons
|
|
offline-tick:
|
|
enable: false
|
|
# Maximum offline time recorded in seconds
|
|
# Please do not set this option to a value that is too large,
|
|
# as it may cause chunks that have been unloaded for a long time
|
|
# taking long to load
|
|
max-offline-seconds: 1200
|
|
# The max time used in loading this chunk
|
|
# Sometimes a chunk might contain a lot of data and has not been loaded for a long time,
|
|
# thus taking a long time loading and causing unexpected issues
|
|
# This setting allows the plugin to forcefully interrupt the tick process if the time consumed has exceeded a certain value
|
|
max-loading-time: 100 #ms
|
|
# Settings for crops
|
|
crop:
|
|
# [RANDOM_TICK]
|
|
# Random tick mode is similar to the vanilla one where crops grow randomly
|
|
# Due to randomness, crops grown under the same conditions may have significant stage differences
|
|
# [SCHEDULED_TICK]
|
|
# Scheduler mode provides more reliable growth schedule management
|
|
# which allows crops to grow at almost the same speed
|
|
mode: RANDOM_TICK
|
|
# The tick-interval determines how many times a block is ticked before its tick logic is actually executed.
|
|
tick-interval: 1
|
|
# Limit the max amount of crops in one chunk (-1 = no limit)
|
|
max-per-chunk: -1
|
|
# Settings for pots
|
|
pot:
|
|
# RANDOM_TICK / SCHEDULED_TICK
|
|
mode: SCHEDULED_TICK
|
|
tick-interval: 3
|
|
max-per-chunk: -1
|
|
# Settings for sprinklers
|
|
sprinkler:
|
|
# RANDOM_TICK / SCHEDULED_TICK
|
|
mode: SCHEDULED_TICK
|
|
tick-interval: 2
|
|
max-per-chunk: -1
|
|
# You can override the default settings for worlds here
|
|
_WORLDS_:
|
|
world_nether:
|
|
enable: false
|
|
world_the_end:
|
|
enable: false
|
|
# Mechanics settings
|
|
mechanics:
|
|
# You can create more ranks by adding more "/" for instance x/x/x/x/x
|
|
# "x" is weight, represents the proportion of probability
|
|
# 17/2/1 = 85%/10%/5%
|
|
# 85% = 17/(17+2+1) * 100%
|
|
default-quality-ratio: 17/2/1
|
|
# Scarecrow prevents crops from being attacked by crows
|
|
scarecrow:
|
|
enable: true
|
|
id: '{0}scarecrow'
|
|
type: ITEM_FRAME
|
|
range: 7
|
|
# If this option is enabled, the range would no longer take effect
|
|
# This option would make it protect all the crops in the same chunk
|
|
protect-chunk: false
|
|
# Greenhouse glass prevents crops from withering from season changing
|
|
greenhouse:
|
|
enable: true
|
|
# You can use a list of ids here, vanilla blocks are supported too
|
|
id: '{0}greenhouse_glass'
|
|
type: CHORUS
|
|
range: 5
|
|
# Sync seasons
|
|
sync-season:
|
|
enable: false
|
|
reference: world
|
|
# Vanilla farmland settings
|
|
vanilla-farmland:
|
|
# Disable vanilla farmland moisture mechanics
|
|
# This option exists because some users prefer to use the vanilla farmland but the water system conflicts with the vanilla one
|
|
disable-moisture-mechanic: false
|
|
# Prevent entities from trampling the farmland
|
|
prevent-trampling: false
|
|
# Set hologram offset correction for other blocks
|
|
hologram-offset-correction:
|
|
"{0}crop_stage_death": 0
|
|
other-settings:
|
|
# It's recommended to use MiniMessage format. If you insist on using legacy color code "&", enable the support below.
|
|
# Disable this would improve performance
|
|
legacy-color-code-support: true
|
|
# Requires PlaceholderAPI to work
|
|
placeholder-register:
|
|
'{skill-level}': '%levelplugin_farming%'
|
|
# Using items from other plugins
|
|
item-detection-order: []
|
|
# Whether to protect the original lore of the item
|
|
# This uses the scoreboard component to identify the plugin's lore,
|
|
# which may conflict with some plugins that still use SpigotAPI#ItemMeta.
|
|
protect-original-lore: false
|
|
# Whether to check if the block/furniture corresponds with the one in CustomCrops data
|
|
# You can enable this if you are using Oraxen as its API is more reliable
|
|
double-check: false |