Content generated with AI — it may contain mistakes.

ExyliaJourney/HelpUpdated in v1.0.0

Common problems

Fixes for the problems server owners hit most: a journey nobody gets, FIRST_JOIN not firing, no floating text or NPCs, steps that never complete and rewards not paid.

Page 19 of 252 min read

Find your symptom, then follow the fix.

The plugin does not start#

The console names what is missing. ExyliaJourney needs ExyliaLib 1.593.0 or newer; the loader installs it and asks for a restart. See Installation.

A journey does not start for players#

Check these, in order:

  1. The journey has a trigger. A journey made in the editor has none: click Start & access, then Add trigger.
  2. It is switched on (enabled: true). journeys/example.yml ships switched off.
  3. The player is not blocked by its requirements, a cooldown, an earlier completion on a journey that is not repeatable, or another active journey in the same group.
  4. Set debug: true in config.yml and reload. The console says why each start was refused.

To start one by hand: /journeyadmin start <player> <journey>. See Journeys.

FIRST_JOIN did not start for me#

FIRST_JOIN starts only for a player who has never played on the server. Players who joined before ExyliaJourney was installed never get it; give them a JOIN or PERMISSION trigger instead. To test, use Test run, /journeyadmin test <journey>, or a fresh account.

I see no floating text, beacon, glow or NPC#

These need packetevents. Without it players still get every journey, with the step in chat, an action bar line, particles and footprints. Install packetevents and restart. See Installation and the FAQ.

A step never completes#

  • The objective filter is too narrow (a block, item or mob that does not match). Open the step, Objective, and check Filter.
  • Blocks a player placed do not count for BREAK_BLOCK filters, items another player dropped do not count for pickups, and mobs from spawners or spawn eggs do not count for kills.
  • A PLACEHOLDER step needs a placeholder that resolves to a number. Check it with PlaceholderAPI's parse command.
  • To move a stuck player on, /journeyadmin trigger <player> <key> fires a custom key, or /journey skip lets them skip a skippable step.

A player got no rewards#

A run where any step was skipped gives no journey completion rewards, so skipping cannot be used to collect them. /journeyadmin complete <player> <journey> pays them in full.

A player lost a journey#

A step's timeout fails the step and stops the whole journey. Its triggers can start it again from the first step. Remove the time limit, or make sure the journey has a trigger.

A player skipped onboarding by mistake#

A skipped journey never starts again from a trigger. /journeyadmin reset <player> <journey> clears it, or /journeyadmin start <player> <journey> starts it anyway.

A dialogue did not open#

Another dialogue or a cinematic may be open, the trigger may be cooling down or already used, or the player may not meet the file's require. /journeyadmin dialogue list shows the loaded ones. See Dialogues.

Something missing on this page? Tell us on Discord