Feature Request: PlaceholderAPI Support for Task Progress on Non-Tracked Quests

[BugJuiceTV]

Description of Feature

What I'm Requesting I'd love to see support for new placeholders that allow us to display task progress for any started quest, not just the currently tracked one.

Example placeholders that would be incredibly useful: %quests_started_1_name% %quests_started_1_task:1_progress% %quests_started_1_task:2_progress%

%quests_started_2_name% %quests_started_2_task:1_progress% ...

%quests_<quest_name>_task:1_progress%

These would allow servers to build dynamic holograms, scoreboards, or menus showing real-time progress for all active quests, which is especially useful for players who work on multiple quests at once.

Currently, only %quests_tracked_task:x_progress% works, meaning only one quest's progress can be shown, and only if it's tracked. This limits flexibility for holograms, GUIs, and other visual tracking tools.

Reason for Addition

Adding this would:

Greatly improve UX for players juggling multiple quests.

Allow servers to show comprehensive quest dashboards via holograms or scoreboards.

Let players keep track of all active quests without switching tracked quests manually.

Thank you for the amazing plugin, and I appreciate your consideration!

Alternative Solutions

These would allow servers to build dynamic holograms, scoreboards, or menus showing real-time progress for all active quests, which is especially useful for players who work on multiple quests at once.

Agreements

• [x] I am running the latest version of Quests
• [x] I am certain this request is unique and a similar issue is not currently open

Other

/holo line set questste 1 1 &6Started Quests:&e %quests_started_list% /holo line set questste 2 1 /holo line set questste 3 1 &6Tracked Quest:&e %quests_tracked% /holo line set questste 4 1 &7%quests_tracked% - Task 1 Progress:&f %quests_tracked_task:1_progress% /holo line set questste 5 1 &7%quests_tracked% - Task 2 Progress:&f %quests_tracked_task:2_progress%

[Krakenied]

It wouldn't be especially useful as the amount of started quests between players can differ. And at this point managing the amount of progress displays becomes impossible without any dedicated solutions (like custom server-specific integration).

or menus showing real-time progress for all active quests

There is /q started command.

Probably other use cases like mentioned:

build dynamic holograms, scoreboards

are too complex to setup using just placeholders (without the plugins APIs).

[BugJuiceTV]

I understand,

for the progression placehodlers,

you have to paste

placeholders: description: "&7Breeding &f5 animals &7of any type." progress: " &8- &f{breeding:progress}&7/5 animals"

into each quest and customize them to each quest, is there a way to do it more efficiently? or all at once?

[BugJuiceTV]

And is there any way I can add a quest started button to the quest categories page

[Krakenied]

into each quest and customize them to each quest, is there a way to do it more efficiently? or all at once?

Not yet but it's tracked under https://github.com/LMBishop/Quests/issues/788 and will be introduced by https://github.com/LMBishop/Quests/pull/785 when completed

And is there any way I can add a quest started button to the quest categories page

Not sure where would you like to go back from menu of categories.

[BugJuiceTV]

@Krakenied The reason why you would want to go "back from the menu of categories" would be either to close the menu, which is not a feature currently. I suggest you may want to add a "gui.back-button", but for escaping the menu with a button, it's clean and gives options for people, making it unique.

My original "And is there any way I can add a quest started button to the quest categories page?" I was meant to ask basically how to make a button to go to the start categories, but I didn't really say it right. something like this, but now it's, how can I make a button that closes the categories menu?

commands: - "sudo {player} quests started"

I'd like to basically have this, but this isn't secure because it's using console to force the player to do commands

as well as something like

commands: - "quests close {player}"