promotional bannermobile promotional banner

Majestic Structures

Majestic Structures rebuilds the Overworld's vanilla structures in the Majestic style, starting with the mineshafts: the Order's old workings, dug by the creatures of the Majestic Bestiary. Every replacement can be switched off from the config.
Back to Files

Majestic Structures (0.0.0-beta.4)

File namemajestic_structures-1.21.1-neoforge-21.1.249-0.0.0-beta.4.jar
Uploader
LlaGuiT0LlaGuiT0
Uploaded
Oct 5, 2026
Downloads
7
Size
54.0 KB
Mod Loaders
NeoForge
File ID
9073730
Type
B
Beta
Supported game versions
  • 1.21.1

Curse Maven Snippet

NeoForge

implementation "curse.maven:majestic-structures-1725421:9073730"

Learn more about Curse Maven

What's new

v0.0.0-beta.4 - The spawns nest where they belong

Fixed

  • The world still would not load. 0.0.0-beta.3 fixed the start height, and the same crash came back one layer down: spawn_overrides was not shaped the way the codec reads it. It maps a spawn category to an object that carries the bounding box and the list of spawns, so "monster" has to be an object with bounding_box and spawns in it. Ours had bounding_box and monster as siblings with the entries directly underneath, so the registry saw a category named bounding_box and refused both.
  • The Order's creatures are back in the list once the shape is right: undead, goblins, dire wolves, satyrs, and a gnome or a centaur in the deeper halls.

Notes

  • 0.0.0-beta.3 was published broken and should be ignored. Two separate mistakes were stacked on top of each other in one data file, and the second one only became visible after the first was out of the way. If you downloaded it, take this one instead.
  • The schema came from the game, not from memory. It is copied from minecraft:pillager_outpost in the 1.21.1 client jar. Every other structure in the pack — majestic:observatory, fallen_shrine, arcane_portal — was already nested correctly, so this one file was the only one wrong.

Known issues

  • Still unverified in-game. Two data-shape bugs have been found statically without opening the game once, which is not a good look and is not a reason to assume the rest is sound. Treat the mineshaft as untested until you have walked one, and say which seed if it comes out wrong.
  • The chain is probably shorter than 7–13 pieces. The jigsaw expansion radius cannot go past 128 blocks and bury spends 12 of them, so the 32 chunks the workshop asked for is out of reach whatever the loader. 116 is the ceiling, and at 116 expect fewer pieces.
  • Overlapping other structures is still possible, and a mineshaft under solid rock is still unreachable. Shallower depth (/majestic_structures depth -25) is the answer to the second.
Beta, and an apology. Two releases in a row have shipped a mineshaft that would not load. If it still fails on this one, the log line that names the file and the codec error is all we need — send that.