Troubleshooting

The plugin does not enable

Check these first:

1

Verify the server version

The server is Paper or Purpur on Minecraft 1.21.11 or 26.2.

2

Verify the Java version

The process is using Java 21.

3

Check for duplicate JARs

There is only one DrakoDungeons JAR in plugins/.

4

Avoid reload managers

No reload manager was used after replacing the JAR.

5

Review the first console error

The first DrakoDungeons error in the console identifies a configuration path or dependency problem.

Run /dga validate when the command is available. If startup fails before commands register, correct the console error and restart.

No zones are shown

A clean install intentionally contains zero zones. Create one in game:

/dga setup createzone mines "Mines"

If zone files exist, confirm that settings/gameplay.yml: progression.starting-zone names a valid zone and that zone orders and stage numbers are consecutive.

A reload fails

• Read the full path in the error.

• Check indentation and duplicate YAML keys.

• Confirm that referenced currencies, zones, areas, mobs, enchants, and materials exist.

• Confirm that menu capacity matches the related content catalogue.

• Run /dga validate again before retrying reload.

If the message says publication or live refresh was incomplete, perform a full server restart before admitting players.

Players cannot enter

Confirm that:

• the world is loaded;

• the zone and stage are unlocked;

• the stage has at least one valid area and mob;

• the area has an entry and mob point;

• the player is alive and not in spectator mode;

• AFK areas have the drakodungeons.afk permission;

• an optional selection-reroll cooldown is not active.

Use /dungeons status, /dga debug, and /dga setup list to inspect state.

Private mobs cannot be clicked

Check packets.interaction-hitbox-width, interaction-hitbox-height, input interaction budgets, target range, area bounds, and the spawn's optional hitbox overrides. Test without another plugin intercepting entity interaction packets.

Packet blocks do not appear

Run:

/dga blocks status
/dga validate
/dga blocks rebuild

The area needs explicit bounds, each source material must exist in the physical cuboid, and replacements must have compatible server behavior. If the physical build changed, stop the server and remove cache/packet-blocks/, then restart or rebuild.

Menus fail validation

Do not remove required item IDs. Confirm the menu size, 1-based slots, valid materials, non-conflicting slot ranges, required state templates, and cross-file capacity rules.

Profiles do not save

Use /dga save and inspect the console. Check disk space, filesystem permissions, antivirus locks, and whether another process is holding dungeons.db. Never copy over the live database.

Clean development recovery

When the data is disposable and an incompatible development schema is the problem:

1

Stop the server

2

Back up anything needed

3

Remove the plugin directory

Remove the complete plugins/DrakoDungeons/ directory.

4

Start again

Partial deletion can leave a configuration that correctly fails validation.