Add-ons/Player Quest System Engine (PQS)/Configuration and troubleshooting

Lua add-on documentation: Player Quest System Engine (PQS) overview · Add-on hub · Contribute or update documentation

Configuration and troubleshooting

PQS saves engine preferences and per-quest progress locally. Version 1.10.0 requires Lua API 15 and SES, requests no Internet permission, and contains no quest content by itself.^[1]

Alert settings

PQS can disable the tray alert sound or change its volume. The visual tray state still indicates unread or changed journal, conversation, and virtual-item information. Viewing the relevant window acknowledges its current state; future significant changes can light it again.

No quests appear

Install and enable SES, PQS, and at least one quest-library add-on.
Wait for PQS's Ready message, which reports the number of loaded quests.
Open the Quests browser and confirm that the desired quest is enabled.
Use /lua check for dependency or package errors.
If a library was enabled after PQS, reload once; SES replay should normally deliver its announcement without this, but the check helps isolate a broken library bootstrap.

PQS itself reporting zero quests can be correct when no library is installed.

Progress does not update

Confirm that the objective belongs to the active journal step and that the library supports the current client language. Location goals use saved coordinates and scene identity; inventory, buff, combat, and chat goals depend on the corresponding supported observable event. Include the library name and quest ID when reporting a failure.

Authors can use !pqsdebug on temporarily to trace criteria and actions, and !pqsdebug off afterward. !pqssws controls separate window-system diagnostics. Other !pqs* mutation commands present in the source are testing tools and can alter progress; they are not a player recovery procedure.^[1]

Migration and backups

Older versions stored progress under pqs/saves/<quest>.save.json and preferences in pqs/user.ini. The package imports found values into saved variables and renames the old files with .imported. Keep those files until progress and sound settings have been verified.

Reset only the affected quest through the browser. A reset discards its local progress. Removing and reinstalling the catalog package normally leaves saved variables in place,^[2] so reinstalling is not a guaranteed reset and should not be presented as one.

Reporting a problem

Provide PQS version 1.10.0, SES version, quest-library name/version, quest ID and current step, client language, exact error, and a minimal reproduction in the support thread. State whether a clean reset reproduces the issue before attaching any saved data.

References

↑ ^1.0 ^1.1 Community Addons: approved PQS 1.10.0 package, reviewed October 13, 2026.
↑ Catnip Games: Lua add-on authoring guide, retrieved October 13, 2026.