Skip to main content

⌨️ Commands

Every NotQuests command lives under one of two roots:

  • /q — the player command (needs the notquests.use permission, which everyone has by default). Aliases: /q, /notquests, /nquests, /nquest, /notquest, /quest, /quests, /qg.
  • /qa — the admin command for building and managing quests (needs notquests.admin, OP by default). Aliases: /qa, /nquestsadmin, /nquestadmin, /notquestadmin, /qadmin, /questadmin, /qag, /notquestsadmin.
tip

You don't have to memorise any of this — just start typing and the tab-completion will guide you the whole way. This page is here for when you want the big picture.

For every generated command shape, including nested objective/action/condition commands and flag details, see the Generated Command Reference.

In the lists below: <required> is a required argument, [optional] is optional, and (flags) are optional --flags.

Duration arguments accept short and readable formats. For example, 500ms, 1s, 5m, 2h, and 1d all work. A bare number is treated as milliseconds.

🎮 Player commands (/q)​

  • /q - Opens the quest GUI (or shows clickable text, depending on your config).
  • /q take <quest> - Accept/start a quest.
  • /q activeQuests - List your active quests.
  • /q progress <activeQuest> - Show your progress on an active quest.
  • /q preview <quest> - Preview a quest (description, requirements, rewards) before taking it.
  • /q abort - List the quests you can abort.
  • /q abort <activeQuest> - Abort (give up) an active quest.
  • /q questPoints - Show how many Quest Points you have.
  • /q category <category> - Open the quest view for a category.
  • /q continueConversation <optionID> - Pick an answer in an open conversation. (You normally just click the option instead.)
  • /q profiles - Show your current profile and list the others.
  • /q profiles create <name> - Create a new profile (a separate, fresh save of your quest progress).
  • /q profiles change <name> - Switch to another profile.
Profiles

A profile is a self-contained save of a player's quest progress (active/completed quests, Quest Points, tags, cooldowns). Switching profiles is like having multiple save files. Managing profiles needs the notquests.user.profiles permission.

🛠️ Admin commands (/qa)​

Creating & managing quests​

  • /qa create <quest> --category <category> - Create a new quest, optionally in a category.
  • /qa delete <quest> - Delete a quest.
  • /qa clone <sourceQuest> <newQuestName> - Copy an existing quest under a new, unused name.
  • /qa list AllQuests - List every quest you've made.
  • /qa list ObjectiveTypes / RequirementTypes / ActionTypes / TriggerTypes / Placeholders - List the available building blocks.
  • /qa reload - Reload all config and quest files.
  • /qa save - Save everything to disk.
  • /qa version - Show the plugin version.

Cloning keeps the source quest's category, display name, settings, objectives (including sub-objectives), requirements, rewards, triggers and configured NPC links. You can edit the copy without changing the original. Player progress and completion history are not copied. References to saved items, actions and other quests still point to the same things; cloning doesn't duplicate those or place new NPCs or armor stands in the world.

Editing a quest — /qa edit <quest>​

Everything about a single quest lives under /qa edit <quest>.

Basics

  • description set <text> / show / remove - The quest's description (supports MiniMessage).
  • displayName set <text> / show / remove - The quest's display name.
  • guiItem <material> --glow - The item shown for this quest in GUIs.
  • category set <category> / show - Move the quest to a category.

Limits & cooldowns

  • limits accepts <amount> - Max times a player can accept this quest (-1 = unlimited).
  • limits completions <amount> - Max times a player can complete it (-1 = unlimited).
  • limits fails <amount> - Max times a player can fail it (-1 = unlimited).
  • acceptCooldown complete set <duration> / disable - Cooldown before a player can re-accept after completing.
  • takeEnabled <true|false> - Whether players can take the quest via /q take.
  • abortEnabled <true|false> - Whether players can abort it.

Objectives — the steps of the quest. See the Objectives reference.

  • objectives add <type> ... - Add an objective.
  • objectives list - List the objectives.
  • objectives clear - Remove all objectives.
  • objectives edit <id> ... - Edit one objective (see below).

Inside objectives edit <id> you can set a description, displayName, taskDescription, a location (set/enable/disable), a completionNPC, add rewards, and add objective conditions in three slots:

  • conditions unlock add <type> ... - must be met for the objective to unlock.
  • conditions progress add <type> ... - must be met for progress to count.
  • conditions complete add <type> ... - must be met for the objective to finish.

Requirements — conditions to accept the quest. See the Conditions reference.

  • requirements add <type> ... · list · clear · edit <id> delete

Rewards — actions that run when the quest is completed. See the Actions reference.

  • rewards add <type> ... · list · clear · edit <id> remove

Triggers — run actions on quest events (begin/complete/fail/death/etc.). See the Triggers reference.

  • triggers add <action> <event> ...
  • triggers list · clear · remove <id>

Quest givers

  • npcs add <npc> --hideInNPC - Attach the quest to an NPC. Citizens and FancyNPCs selectors are available on Paper; armor stands are available on both platforms. rightClickSelect gives you a selector item.
  • npcs list · npcs clear
  • armorstands add - Get an item, then right-click an armor stand to attach the quest to it.
  • armorstands list · armorstands clear

Conversations — /qa conversations​

See the Conversation System for the full picture.

  • conversations create <name> --demo --category <category> - Create a conversation. --demo fills it with a working example to learn from.
  • conversations list - List conversations.
  • conversations analyze <conversation> --printToConsole - Sanity-check a conversation's structure.
  • conversations start <conversation> - Start a conversation.
  • conversations edit <conversation> ... - Attach NPCs/armor stands and manage speakers/categories. Conversation lines are edited in the .yml file.

Global actions & conditions​

Reusable actions and conditions you can refer to by name from anywhere.

  • /qa actions add <name> <type> ... - Create a named action.
  • /qa actions list · /qa actions edit <name> execute [player] ... · /qa actions edit <name> ...
  • /qa conditions add <name> <type> ... - Create a named condition.
  • /qa conditions list · /qa conditions edit <name> check [player] · /qa conditions edit <name> ...

Categories & Tags​

  • /qa categories create <name> · list · edit <category> ... - Organise quests into (nestable) categories.
  • /qa tags create <type> <name> · list · delete <name> - Custom per-player data you can read/write with conditions, actions and placeholders. See the reputation tutorial.

Saved items — /qa items​

Save an item once, then use its name in quest rewards, item objectives and actions such as GiveItem. The saved name (for example, quest_token) is its ID in commands. Its display name is the name players see on the actual item, not just an internal label.

CommandWhat it does
/qa items create <name> <material> [--category <category>]Saves an item from a material. Use hand instead of the material to save the item you're holding, including its custom data.
/qa items listLists saved items.
/qa items edit <item> give <player> <amount>Gives an online player the saved item, including its display name.
/qa items edit <item> displayName set <text>Sets the actual item's display name. Spaces and MiniMessage formatting work here.
/qa items edit <item> displayName showShows the configured display name.
/qa items edit <item> displayName removeRemoves the display-name override.
/qa items edit <item> removeDeletes the saved item definition. Update any quests or actions that reference it first.

For example:

/qa items create quest_token gold_nugget
/qa items edit quest_token displayName set <gold>Quest Token
/qa items edit quest_token give Steve 4

You can also give that same item with /qa actions execute GiveItem quest_token 4. Both routes use the saved display name. Choose a unique saved name, not a vanilla material name such as stone. The command is /qa items, with items only once.

Managing players​

  • /qa give <player> <quest> - Give a player a quest (skips requirements).
  • /qa completeQuest <player> <activeQuest> / failQuest <player> <activeQuest> - Force-complete or fail a player's active quest.
  • /qa resetAndRemoveQuest <player> <quest> / resetAndFailQuestForAllPlayers <quest> - Reset and remove/fail.
  • /qa progress <player> <activeQuest> · activeQuests <player> · completedQuests <player> - Inspect a player.
  • /qa questpoints <player> add <amount> / remove <amount> / set <amount> / show - Manage a player's Quest Points.

Debug & maintenance​

  • /qa debug - Toggle debug mode (lots of extra info in chat).
  • /qa debug showErrorsAndWarnings --printToConsole - Show collected errors/warnings.
  • /qa debug worldInfo · clearOwnChat · beaconBeam <player> <name> <location> - Misc debug helpers.
  • /qa debug loadDataUnsafe · disablePluginAndSaving <reason> · enablePluginAndSaving <reason> - Advanced/risky (used for things like database migrations). Back up first!
Lost? Use the in-game help

/qa help and /qa help <search> open a searchable, clickable help menu — handy when you can't remember the exact path.