Tags
Creators
Details
All versions
1.8-datapack
Release
1.88 months ago 60
Compatibility
Minecraft: Java Edition
1.21.11
Platform
Data Pack
Changes
⚙️Technical
- Now supports Axis
- You can now summon items with all of their attributes, including custom models, enchantments, etc.
- Now you can summon both parts of the multi-block, for example: rose bush, door.
- Added blockstate support to block displays (~109 unique blockstates. If you find a broken or missing blockstate, please report it on the Discord server!)
- Changes with the Chat menu:
- It's now more compact to fit more information on the screen at once.
- Hidden during in-game block editing so as not to obscure the view.
- If no display is selected, only the buttons to summon the display are shown.
- If a display without blockstates is selected, shows all editing parameters except blockstates.
- If a display with blockstate is selected, shows the full editing set.
- Lots of optimizations.
- The display lighting system now uses macros instead of a bunch of hardcode.
- Updated and new sound and visual effects.
- Sound effects have been moved from hardcode to a separate category.
- For some reason, the billboard position reset worked through a different system from all the others; now they all work the same.
- Chat menu visuals have been updated.
- Updated display scaling visuals.
- Added proper descriptions for all buttons in the chat menu.
🛠️Fixes
- The display brightness level was not updated immediately, but upon the next action.
- When changing the lighting level or display glow color, the chat menu wasn't displayed fully or wasn't displayed at all.
- Fixed a bug where invisible interaction entities could remain for some time after deleting a display, or removing interactive points for selecting adjacent displays.
🙏Special thanks to
- vdvman1
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:AtYod41W:mpWEJcNl"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:AtYod41W:mpWEJcNl"
}

