TribeCraft Wiki · Release 2026.09.5
Wiki Release: 2026.09.5 · UltimateClans: 9.1.4 · Documentation branch: 9 · ClanQuest

ClanQuest practical usage guide#

ClanQuest adds clan quest/progression system with many gameplay objective listeners, GUI, persistence, daily/quest data and integrations with other events/plugins. This guide focuses on the actual administrator and player workflow: what to set up first, how to test it in-game, and what to check before enabling it for everyone.

How the feature works#

In normal use, the feature follows this flow: Define quest IDs and objectives in quests.yml; keep IDs unique and human-readable. Configure which quests can be started, their requirements, rewards, limits and progression values. Use the player/admin quest GUI/commands to start a test quest.

  1. Define quest IDs and objectives in quests.yml; keep IDs unique and human-readable.
  2. Configure which quests can be started, their requirements, rewards, limits and progression values.
  3. Use the player/admin quest GUI/commands to start a test quest.
  4. Perform the exact action type being tested (break, place, kill, fish, craft, enchant, explore, breed, collect, trade, etc.) and verify progress.
  5. Test abandon/finish behavior and persistence across reconnect/restart.

Administrator setup checklist#

  • The source includes many distinct listeners, so an objective only progresses from the matching event type. Do not substitute similar actions when testing.
  • Integrations include specialized listeners for Koth, Outpost, CMI, Mythic and other supported contexts; only configure those objective types when the dependency/integration is actually present.
  • Keep daily/player quest storage intact during updates; back up before reshaping quest IDs.

Commands and GUI access#

Use the command examples in the workflow above and open the Commands page in the sidebar for the complete configured command tree. Command labels can be changed in commands.yml, so the Wiki keeps the player-facing examples separate from the raw message templates.

Configuration areas#

  • Configdate_format, timezone, sync_if_enabled, translate, Quest, Icon, Permissions, logger, league
  • Storagetype, mysql, user, pass, databases

Changing settings safely#

  1. Back up the component configuration and persistent data before changing a live server.
  2. Change one feature area at a time.
  3. Reload only if the component documents reload as safe; otherwise restart the server.
  4. Test with a non-OP account that has exactly the intended clan role/permission.
  5. Watch the console from the first relevant warning/error, not only the final stack trace.
  6. On multiserver networks, repeat the check on every node and confirm shared storage/sync settings match.