Let addons see your completed quests (like Turtle's .queststatus)

[Dsolx]

TLDR: add a server command that sends a player's completed quest IDs to their addons. Turtle WoW had one, and the addons people still use here were built around it. It would make pfQuest and every quest guide addon much better on OctoWoW, and the server already has the data.

The problem
If you use pfQuest, a quest guide, or any quest helper, it has no way to know from the server side which quests you already finished. The addons can only learn what it watches you do while it is installed and running.

This hits:

• anyone who installs or switches quest addons on an existing character
• returning players coming back to an old character
• anyone who reinstalls, wipes settings, or plays on a second PC
• alts levelled before the addon was added

What already exists on OctoWoW
On login the server shows:

Death counter: 0 | Quests completed: 6

So the server tracks completed quests per character. It just reports the count and not the list.

The ask
Turtle WoW solved this with .queststatus. It replies with hidden addon messages that addons read and players never see in chat:

Code: Select all

event:   CHAT_MSG_ADDON
prefix:  TWQUEST
payload: completed quest IDs separated by spaces, sent in batches

Why it is worth it
pfQuest and pfQuest-turtle already ship the code that listens for these messages, so matching the old format means existing addons work as-is, with no addon author needing to patch anything. Nothing about the game changes for players who do not use addons, and nothing is shown in chat.

Thanks for reading, and thanks to the team for the work on this server.

[Berdal]

Oh god please yes! I hate that pfQuest is out of sync!

[Tips]

But there is .queststatus command on Octo, and it works exactly the same as on Turtle.

[Dsolx]

But there is .queststatus command on Octo, and it works exactly the same as on Turtle.

Holy shit you're right, thanks. .queststatus does work here, I just tested it and got the full TWQUEST list back. My addon was asking too early in the login sequence, so it never got a reply. Fixed on my end. Didnt saw the .queststatus in available commands either, only queststatuses, thats where my confusion came from. Thanks for the heads up