aboutsummaryrefslogtreecommitdiffstats
path: root/bukkit/src/main/resources
diff options
context:
space:
mode:
authorKrakenied <Krakenied1@gmail.com>2024-02-22 18:58:46 +0100
committerLeonardo Bishop <13875753+LMBishop@users.noreply.github.com>2024-03-09 16:15:28 +0000
commit2896ac51941202d5c652cab224462667458e9ed3 (patch)
tree3a122dcdf173304168375d2d667ec133fdfbadbb /bukkit/src/main/resources
parentf62133d5c2d8d65e7bf88208640edec88153e1c8 (diff)
Improve CoreProtect check behaviour even more
Add CoreProtect block lookup delay option
Diffstat (limited to 'bukkit/src/main/resources')
-rw-r--r--bukkit/src/main/resources/resources/bukkit/config.yml4
1 files changed, 4 insertions, 0 deletions
diff --git a/bukkit/src/main/resources/resources/bukkit/config.yml b/bukkit/src/main/resources/resources/bukkit/config.yml
index c4d7df4b..4b26dfc0 100644
--- a/bukkit/src/main/resources/resources/bukkit/config.yml
+++ b/bukkit/src/main/resources/resources/bukkit/config.yml
@@ -124,6 +124,10 @@ options:
# How frequently placeholderapi_evaluate task placeholders will be refreshed (def=30 - 1.5s)
# (multiply SECONDS by 20 to get the number of ticks)
placeholderapi-global-refresh-ticks: 30
+ # By how much (in millis) CoreProtect database async block lookups will be
+ # delayed. It may be helpful in case CoreProtect block lookups work sometimes
+ # weird and doesn't account for some last instant/spammed block changes
+ coreprotect-block-lookup-delay: -1
# Verify quests exist when a player's data is loaded - inconsistencies may arise when
# players progress on specific quests and those quests are later removed. The problem is that their progress
# is still kept in the quest progress file, which may lead to issues such as players reaching a quest started