Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
MythicDungeons MythicDungeons
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 87
    • Issues 87
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • MythicCraft
  • MythicDungeonsMythicDungeons
  • Issues
  • #66

Closed
Open
Created Jul 23, 2022 by Dragon@DragonEye

[Bug] DXL Importer fails when using a custom world container

Greetings, I found out that attempting to import DXL worlds with /dxlimport fails if you have a custom world container set in your startup flags. It fails stating that the map you are trying to import does not exist. (Setting a custom world container will store your worlds in a folder instead of in the root directory of the server for better organization.)

Steps to reproduce:

  1. Add --world-container worlds to your server startup flags, OR add the line world-container: worlds to bukkit.yml
  2. Start your server and attempt to /dxlimport a DXL map.

Server Information:

  • Paper 1.19 (Build 66)
  • MythicDungeons 1.0.3 (Build 24)
Edited Jul 23, 2022 by Dragon
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking