FAQ & Troubleshooting

No. LuckPerms is optional. Without it, all players are treated as the default group. Just configure everything under default in your drop and quest configs.

No. PlaceholderAPI is optional. Without it, all plugin features work normally — you just cannot use %mythicdrop_...% placeholders in scoreboards or GUIs.

No! Run /mythicdrop reload after editing any config file. No restart needed.

In plugins/MythicDropRefactored/quest_data.yml. This is created automatically and updated as players progress. It persists across server restarts.

Check these things in order:

1. Mob name: The section name in config.yml must exactly match the MythicMobs internal mob name (case-sensitive). Example: SkeletonKing is not the same as skeletonking
2. reward-processing: Make sure at least one of these is true:
   yaml

   Copy

   reward-processing:
     most-damage: false
     last-hit: true    # At least one should be true

3. Top-damage system: If the mob is in top3damage.yml or similar, it will not use config.yml drops unless use-standard-rewards: true is set.
4. Enable debug mode: Set activate-debug: true in debug.yml and reload. Check your console for detailed output.

1. LuckPerms is installed and working (/lp info to verify)
2. The player actually has the VIP group (/lp user <name> info)
3. The group name in your config exactly matches the LuckPerms group name (case-sensitive)
4. The player was online when the mob died (offline lookups fall back to "default")

Test the command manually in your server console first (replace %player% with a real name). If it works manually but not from the plugin, check:

• The command does not start with /
• %player% is typed exactly as shown (not %Player% or {player})
• The player is online when the reward runs

1. Mob name: The mob-name in quests.yml must exactly match the MythicMobs mob name
2. Quest completed: Completed quests do not track further progress
3. Debug mode: Enable activate-debug: true in debug.yml to see detailed quest tracking logs

The slot field controls the position. Slots go from 0 (top-left) to 44 (bottom-right of row 5). Make sure no two quests share the same slot number, and that all slots are between 0 and 44.

1. Make sure quests.yml has at least one quest configured
2. Run /mythicdrop reload after saving changes
3. Check the console for YAML syntax errors (indentation mistakes are common)

1. The mob name in /marena setspawn must exactly match the MythicMobs name
2. MythicMobs is installed and working (test with /mm mobs spawn <mobname>)
3. Make sure you are standing in a valid location (not inside a block)

1. The respawn value is in seconds (e.g., 60 = 1 minute)
2. Make sure respawn is greater than 0
3. Check the console for errors related to ArenaManager