Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated 2 days ago
All versions
3.0.0+mc1.21.11-neoforge
Release
The Mighty Architectury 3.0.0 for neoforge 1.21.112 days ago 14
Compatibility
Minecraft: Java Edition
1.21.11
Platform
NeoForge
Supported environments
Client-side
Client and server
Changes
Changed
- Servers running the mod no longer lock out players who don't have it. The mod used to add a wand and two marker blocks, and Fabric turns away players who are missing a server's blocks ("This server requires Fabric API installed on your client!"). It now adds none, so a server can install it just for faster printing.
- The theme-making tools are now vanilla items. Open the exporter toolkit as before (G, edit
a theme, then 1):
- Design Exporter: a named blaze rod. Plain blaze rods don't work.
- Design Marker: a lodestone.
- Layer markers: glazed terracotta. White is Once, lime Clone x1, green Clone x3, yellow Optional, light blue Mask above, blue Mask below. Right-click a side to change it; sneak to go back.
- While you edit a theme, markers are labelled and each lodestone shows where its design goes: an orange box until it has markers, then a green outline of what will be exported. Clicking a lodestone with no markers tells you where to put them.
- Changing a marker needs creative mode or operator, like printing. Toolkits work in creative mode on any server.
- Exporting refuses a scanner palette that contains a marker block.
Removed
- The old wand and marker blocks (
architect_wand,slice_marker,design_anchor). They turn into air in existing worlds, so replace them with the new tools before exporting again. Your exported designs, themes and palettes are not affected.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:FDYDUHRw:vXTQq2Zh"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:FDYDUHRw:vXTQq2Zh"
}

