EpicQuestHub

Epic Quest Hub — Changelog

Minecraft 1.21.1 · NeoForge

1.1.1

• Fixed: Removed the vanilla void stone/cobble spawn platform that appeared at the world origin alongside your hub structure.
• Fixed: New worlds now use a custom pure-void flat generator without decoration features, so the VoidStartPlatformFeature is never placed.
• Fixed: Hub structure pasting now runs after the server has finished generating spawn chunks, so your schematic is no longer overwritten by the stone platform.

1.1.0

• Changed: The mod is now fully configurable — you provide your own hub structure instead of a bundled schematic.
• Added: Support for WorldEdit .schem files (Sponge v1/v2/v3) and Minecraft structure block .nbt exports.
• Added: Configurable paste position (pasteX, pasteY, pasteZ) and spawn position (spawnX, spawnY, spawnZ, spawnAngle).
• Added: structureFile config option — point to any .schem or .nbt under config/epicquest_hub/.
• Changed: Protection setting renamed from protectSchematic to protectStructure.

1.0.1

• Fixed: Players no longer spawn randomly on towers or other high blocks near the hub.
• Added: Exact spawn enforcement on login, respawn, and world spawn creation.
• Added: Spawn radius game rule set to 0 for precise spawning.
• Added: Structure protection — blocks inside the pasted hub cannot be broken, placed, or destroyed by explosions (configurable).
• Fixed: Default paste height adjusted for void worlds.

1.0.0

• Initial release.
• Added: Automatically creates a void overworld when starting a new world.
• Added: Pastes a hub structure at world creation and sets the world spawn.
• Added: Sponge schematic loading and placement on first server start.

Setup (1.1.0+)

1. Place your .schem or .nbt file in config/epicquest_hub/.
2. Edit config/epicquest_hub-common.toml with your structure path, paste coordinates, and spawn coordinates.
3. Create a new world — the hub is placed automatically on first load.