Operating and Troubleshooting

Day-to-Day Operations

Use /ad admin reload after config edits.
Re-run /ad admin dungeon validate <id> before enabling after any setup change.
Use /ad admin dungeon edit <id> for preview and quick sanity checks.
If you close setup GUI by mistake, use /ad admin back to restore last closed admin/setup screen once.
Keep imports/ folder organized so stage file names in config still match real files.
If you change main-config.yml round structure, revisit all stage spawn expectations.

Problem	What to check first
Missing dependency warning	Confirm FastAsyncWorldEdit, MythicMobs, MMOItems, and MythicLib are all loaded. PlaceholderAPI is optional only.
Schematic missing	Check file exists in `plugins/AramDungeons/imports/` and stage uses exact filename.
Missing stage anchor	Save stage anchor before saving combat/supply/checkpoint/NPC/spawn positions.
Missing FAWE selection	Make WorldEdit selection first, then run `/ad admin region copy ...`.
Invalid dungeon	Run `/ad admin dungeon validate <id>` and fix missing field listed in output.
Item creation failure	Verify MMOItems `type` and `id` in `equipment-config.yml` exist and can be created on this server.
Run fails to paste	Confirm `instance-world` exists and schematic file format is readable by WorldEdit/FAWE.
Preview shows nothing	Check anchors and saved points exist. Preview only marks stored points.

When validation output includes entries like these, use them literally:

stage-1:schematic-file-exists means import file missing.
stage-1:supply-npc:exp means EXP NPC not saved.
stage-1:spawn-outside-combat:1:group means spawn lies outside combat region.
stage-1:supply-npc-outside-region:stats means NPC point is outside copied supply bounds.
stage-1:mythicmob:SkeletalMinion means MythicMobs id was not found.

Validate.
Preview anchors, teleports, and spawns.
Enable.
Run /ad admin test <id>.
Confirm stage paste, combat spawns, supply NPCs, boss spawn, and cleanup all behave as expected.