From 0a78d93f605e4632d67cb3319c229e9c3f9e8fd0 Mon Sep 17 00:00:00 2001 From: Krakenied Date: Sat, 27 May 2023 17:09:56 +0200 Subject: Add support for custom PlayerBlockTracker forks --- bukkit/src/main/resources/resources/bukkit/config.yml | 2 ++ 1 file changed, 2 insertions(+) (limited to 'bukkit/src/main/resources') diff --git a/bukkit/src/main/resources/resources/bukkit/config.yml b/bukkit/src/main/resources/resources/bukkit/config.yml index adef1a1f..ab6e0c18 100644 --- a/bukkit/src/main/resources/resources/bukkit/config.yml +++ b/bukkit/src/main/resources/resources/bukkit/config.yml @@ -208,6 +208,8 @@ options: record-log-history: true # Replace placeholders from PlaceholderAPI in rewards, rewardstrings and start strings quests-use-placeholderapi: false + # PlayerBlockTracker class to be used with the hook + playerblocktracker-class-name: "com.gestankbratwurst.playerblocktracker.PlayerBlockTracker" # 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 -- cgit v1.2.3-70-g09d2