From 48ee7a64be995c316cc56abb226347b778ea8e06 Mon Sep 17 00:00:00 2001 From: Krakenied Date: Mon, 22 Jan 2024 11:31:21 +0100 Subject: Add async and refresh-ticks options to PAPI task type --- bukkit/src/main/resources/resources/bukkit/config.yml | 3 +++ 1 file changed, 3 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 32733079..c4d7df4b 100644 --- a/bukkit/src/main/resources/resources/bukkit/config.yml +++ b/bukkit/src/main/resources/resources/bukkit/config.yml @@ -121,6 +121,9 @@ options: use-progress-as-fallback: true # PlayerBlockTracker class to be used with the hook playerblocktracker-class-name: "com.gestankbratwurst.playerblocktracker.PlayerBlockTracker" + # 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 # 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