Majestic Core
The building stone of the Majestic ecosystem
Majestic Core ships the Order’s own masonry — and nothing else. It exists so that structure mods can build out of the same stone without depending on Majestic itself, which would drag in a boss, a book system and four worldgen structures they have no use for.
Twenty-five blocks, in the same shape vanilla splits its own stone into:
| Family | Blocks |
|---|---|
| The original three | arcane_brick, rune_block, carved_keystone |
| Derivatives | smooth_, polished_, cracked_, chiseled_, mossy_, veined_arcane_brick, arcane_rubble, arcane_rubble_wall |
| The drowned stone | sunken_arcane_brick, polished_sunken_arcane_brick, and its slab and stairs |
| Shapes | arcane_brick_slab, arcane_brick_stairs, arcane_brick_wall, arcane_beam |
| Cutout decoration | arcane_railing, carved_gate, arcane_palisade |
| Light | rune_lantern (light 11), rune_sconce (light 7, wall only) |
It ships no worldgen, no mobs and no progression. Mods build on its blocks.
Using it
Declare the dependency and the blocks are available:
[[dependencies.majestic]]
modId="majestic_core"
type="required"
versionRange="[0.0.0-beta.2,)"
ordering="AFTER"
side="BOTH"
Two questions, two methods:
isOrderStone(BlockState)— the original three only. Majestic’s Portal is built against this and the set is frozen there on purposeisOrderMasonry(BlockState)— all twenty-five. This is the one a consumer building a structure wants
Requirements
- Minecraft 1.21.1
- NeoForge 21.1.249
- Java 21
Status
Early. The twenty-five blocks are registered and the project builds. Majestic still registers its own copies of the first three; nothing has been moved out of it yet, and ORDER_STONE was left alone on purpose so the Portal is not disturbed.
Credits
- Part of the Majestic ecosystem by Stalking Dragons
- License: MIT
Majestic Core ships the Order’s own masonry — and nothing else. It exists so that structure mods can build out of the same stone without depending on Majestic itself, which would drag in a boss, a book system and four worldgen structures they have no use for.
Twenty-five blocks, in the same shape vanilla splits its own stone into:
| Family | Blocks |
|---|---|
| The original three | arcane_brick, rune_block, carved_keystone |
| Derivatives | smooth_, polished_, cracked_, chiseled_, mossy_, veined_arcane_brick, arcane_rubble, arcane_rubble_wall |
| The drowned stone | sunken_arcane_brick, polished_sunken_arcane_brick, and its slab and stairs |
| Shapes | arcane_brick_slab, arcane_brick_stairs, arcane_brick_wall, arcane_beam |
| Cutout decoration | arcane_railing, carved_gate, arcane_palisade |
| Light | rune_lantern (light 11), rune_sconce (light 7, wall only) |
It ships no worldgen, no mobs and no progression. Mods build on its blocks.
Using it
Declare the dependency and the blocks are available:
[[dependencies.majestic]]
modId="majestic_core"
type="required"
versionRange="[0.0.0-beta.2,)"
ordering="AFTER"
side="BOTH"
Two questions, two methods:
isOrderStone(BlockState)— the original three only. Majestic’s Portal is built against this and the set is frozen there on purposeisOrderMasonry(BlockState)— all twenty-five. This is the one a consumer building a structure wants
Requirements
- Minecraft 1.21.1
- NeoForge 21.1.249
- Java 21
Status
Early. The twenty-five blocks are registered and the project builds. Majestic still registers its own copies of the first three; nothing has been moved out of it yet, and ORDER_STONE was left alone on purpose so the Portal is not disturbed.
Credits
- Part of the Majestic ecosystem by Stalking Dragons
- License: MIT
Majestic Core ships the Order’s own masonry — and nothing else. It exists so that structure mods can build out of the same stone without depending on Majestic itself, which would drag in a boss, a book system and four worldgen structures they have no use for.
Twenty-five blocks, in the same shape vanilla splits its own stone into:
| Family | Blocks |
|---|---|
| The original three | arcane_brick, rune_block, carved_keystone |
| Derivatives | smooth_, polished_, cracked_, chiseled_, mossy_, veined_arcane_brick, arcane_rubble, arcane_rubble_wall |
| The drowned stone | sunken_arcane_brick, polished_sunken_arcane_brick, and its slab and stairs |
| Shapes | arcane_brick_slab, arcane_brick_stairs, arcane_brick_wall, arcane_beam |
| Cutout decoration | arcane_railing, carved_gate, arcane_palisade |
| Light | rune_lantern (light 11), rune_sconce (light 7, wall only) |
It ships no worldgen, no mobs and no progression. Mods build on its blocks.
Using it
Declare the dependency and the blocks are available:
[[dependencies.majestic]]
modId="majestic_core"
type="required"
versionRange="[0.0.0-beta.2,)"
ordering="AFTER"
side="BOTH"
Two questions, two methods:
isOrderStone(BlockState)— the original three only. Majestic’s Portal is built against this and the set is frozen there on purposeisOrderMasonry(BlockState)— all twenty-five. This is the one a consumer building a structure wants
Requirements
- Minecraft 1.21.1
- NeoForge 21.1.249
- Java 21
Status
Early. The twenty-five blocks are registered and the project builds. Majestic still registers its own copies of the first three; nothing has been moved out of it yet, and ORDER_STONE was left alone on purpose so the Portal is not disturbed.
Credits
- Part of the Majestic ecosystem by Stalking Dragons
- License: MIT
Majestic Core ships the Order’s own masonry — and nothing else. It exists so that structure mods can build out of the same stone without depending on Majestic itself, which would drag in a boss, a book system and four worldgen structures they have no use for.
Twenty-five blocks, in the same shape vanilla splits its own stone into:
| Family | Blocks |
|---|---|
| The original three | arcane_brick, rune_block, carved_keystone |
| Derivatives | smooth_, polished_, cracked_, chiseled_, mossy_, veined_arcane_brick, arcane_rubble, arcane_rubble_wall |
| The drowned stone | sunken_arcane_brick, polished_sunken_arcane_brick, and its slab and stairs |
| Shapes | arcane_brick_slab, arcane_brick_stairs, arcane_brick_wall, arcane_beam |
| Cutout decoration | arcane_railing, carved_gate, arcane_palisade |
| Light | rune_lantern (light 11), rune_sconce (light 7, wall only) |
It ships no worldgen, no mobs and no progression. Mods build on its blocks.
Using it
Declare the dependency and the blocks are available:
[[dependencies.majestic]]
modId="majestic_core"
type="required"
versionRange="[0.0.0-beta.2,)"
ordering="AFTER"
side="BOTH"
Two questions, two methods:
isOrderStone(BlockState)— the original three only. Majestic’s Portal is built against this and the set is frozen there on purposeisOrderMasonry(BlockState)— all twenty-five. This is the one a consumer building a structure wants
Requirements
- Minecraft 1.21.1
- NeoForge 21.1.249
- Java 21
Status
Early. The twenty-five blocks are registered and the project builds. Majestic still registers its own copies of the first three; nothing has been moved out of it yet, and ORDER_STONE was left alone on purpose so the Portal is not disturbed.
Credits
- Part of the Majestic ecosystem by Stalking Dragons
- License: MIT
Majestic Core ships the Order’s own masonry — and nothing else. It exists so that structure mods can build out of the same stone without depending on Majestic itself, which would drag in a boss, a book system and four worldgen structures they have no use for.
Twenty-five blocks, in the same shape vanilla splits its own stone into:
| Family | Blocks |
|---|---|
| The original three | arcane_brick, rune_block, carved_keystone |
| Derivatives | smooth_, polished_, cracked_, chiseled_, mossy_, veined_arcane_brick, arcane_rubble, arcane_rubble_wall |
| The drowned stone | sunken_arcane_brick, polished_sunken_arcane_brick, and its slab and stairs |
| Shapes | arcane_brick_slab, arcane_brick_stairs, arcane_brick_wall, arcane_beam |
| Cutout decoration | arcane_railing, carved_gate, arcane_palisade |
| Light | rune_lantern (light 11), rune_sconce (light 7, wall only) |
It ships no worldgen, no mobs and no progression. Mods build on its blocks.
Using it
Declare the dependency and the blocks are available:
[[dependencies.majestic]]
modId="majestic_core"
type="required"
versionRange="[0.0.0-beta.2,)"
ordering="AFTER"
side="BOTH"
Two questions, two methods:
isOrderStone(BlockState)— the original three only. Majestic’s Portal is built against this and the set is frozen there on purposeisOrderMasonry(BlockState)— all twenty-five. This is the one a consumer building a structure wants
Requirements
- Minecraft 1.21.1
- NeoForge 21.1.249
- Java 21
Status
Early. The twenty-five blocks are registered and the project builds. Majestic still registers its own copies of the first three; nothing has been moved out of it yet, and ORDER_STONE was left alone on purpose so the Portal is not disturbed.
Credits
- Part of the Majestic ecosystem by Stalking Dragons
- License: MIT