Placeholder
What is your Quests version / build number (do not say "latest")?
version: 5.0.0-rc.4-b446
Describe the problem and how to replicate it.
If the player currently has unfinished quests, the Placeholder will become invalid when they log in again
%quests_player_compass_quest_name% %Quests_player_compass_quest_objectives%
Any console errors to share?
no
If applicable, can you provide an example quest from quests.yml?
quests:
default1:
name: Iron Miner
ask-message: <yellow>Mine <pink>2<yellow> blocks of <pink>Iron Ore<yellow>.
finish-message: <yellow>Well done. Here is your reward.
redo-delay: 1800
requirements:
items:
- ==: org.bukkit.inventory.ItemStack
v: 3465
type: STONE_PICKAXE
remove-items:
- false
fail-requirement-message: <red>You must have a <pink>Stone Pickaxe<red> first.
stages:
ordered:
'1':
break-block-names:
- IRON_ORE
break-block-amounts:
- 2
break-block-durability:
- 0
rewards:
money: 1000
quest-points: 1
default2:
name: Mob Hunter
ask-message: <yellow>Kill an assortment of Mobs.
finish-message: <yellow>Excellent. Here is a <pink>Diamond Sword<yellow>.
stages:
ordered:
'1':
death-event: DeathFail
mobs-to-kill:
- Pig
mob-amounts:
- 3
finish-event: NiceFinish
'2':
death-event: DeathFail
mobs-to-kill:
- Zombie
mob-amounts:
- 2
finish-event: NiceFinish
'3':
death-event: DeathFail
mobs-to-kill:
- Skeleton
mob-amounts:
- 1
rewards:
items:
- ==: org.bukkit.inventory.ItemStack
v: 3465
type: DIAMOND_SWORD
exp: 100
quest-points: 1
default3:
name: Catch Fish
ask-message: <yellow>Catch some fish!
finish-message: <yellow>Good job. Here is some <green>experience<yellow>.
stages:
ordered:
'1':
start-event: GiveRod
death-event: DeathFail
fish-to-catch: 2
rewards:
exp: 250
I was not able to produce any issues by accepting 3 quests and relogging. Please provide the example quests you're testing with, and clarify what you mean by "invalid".
https://youtu.be/H8W9BZFmuXw
I followed the steps in your video exactly, but still did not experience any problems. The placeholder says "Mob Hunter" upon logging back in.
Could this be an issue with your scoreboard plugin? I've been using /papi parse PikaMug %quests_player_compass_quest_name%
我完全按照您视频中的步骤操作,但仍然没有遇到任何问题。占位符在重新登录时显示“Mob Hunter”。
这可能是您的记分牌插件的问题吗?我一直在使用
/papi parse PikaMug %quests_player_compass_quest_name%
Uninstalled the scoreboard plugin Is it because I use MySQL? paper 1.20.1 log:
[10:32:37 ERROR]: [Quests] Failed to register events for class org.browsit.mythicmobsquests.MythicMobsItemDeliverObjective because lol/pyr/znpcsplus/api/event/NpcInteractEvent does not exist.
[10:39:53] [Server thread/WARN]: [Quests] Unable to consider custom objectives because quest for default4 was null
Complete log https://mclo.gs/cHgFihD
https://youtu.be/9GQ4LWOeYTE
It's amazing
[10:39:53] [Server thread/WARN]: [Quests] Unable to consider custom objectives because quest for default4 was null
It seems there is an issue with the default4 quest. Everything else is fine.
The only idea I have is perhaps another plugin is interfering with the player join event. You might try temporarily removing all non-essential plugins, to see if that helps.
Tested while retaining only a few required plugins, still unable to display properly
I'd remove ProtocolLib as well, but I'll try to replicate that environment soon.
我也会删除 ProtocolLib,但我会尽快尝试复制该环境。
What?, I don't understand, there may be a discrepancy in the translation(online translation)
I suggest you try removing ProtocolLib as well. If that does not help, I will investigate further once I have time.
I suggest you try removing ProtocolLib as well. If that does not help, I will investigate further once I have time.
I deleted the Protocollib plug -in, but the problem still exists
I tried to produce the same error but I failed. (I tried the same version of the quest and placeholders plugins you used. and I changed my language file.)
Maybe this may be due to the version of the paper or something you did wrong in the configuration.
Thanks for giving it a try @barannnnnns
I also just made another attempt, but still can't replicate the problem on the latest Quests build. It could still be an issue, but without a way to recreate the problem, there's no reason to keep this open.