All versions
1.0.0
Release
Dead's Displays 1.0.0last month 15
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
Dead's Displays v1.0.0
First release — for Minecraft 1.21.1 (NeoForge) and 1.20.1 (Forge)
Added
- Added the Display Stand, a small pedestal that shows off any item in the world
- Works with vanilla items, modded items, weapons, tools, armor, blocks and enchanted or renamed items
- Place it on floors, walls, ceilings or the side of any block
- Right-click the stand to open its menu and drop an item in the slot
- Added a 3D Editor tab with a live preview of the stand and its item
- Move the item freely up to 2 blocks away from the stand on any axis
- Rotate the item on all three axes with full 360 degree control
- Resize the item from 0.1x up to 4x
- Drag the arrows, rings or boxes on the item to move, rotate or resize it, or use the sliders and
+/-buttons for exact values - Hold
Shiftwhile dragging or clicking+/-for fine adjustments - Drag empty space and scroll in the preview to orbit and zoom the camera
- Added Show Holder toggle to hide the pedestal so items float on their own
- Added presets: Centered, Floating, Against Surface, Horizontal, Vertical, Diagonal and Large Artifact
- Added Copy and Paste for poses so matching displays are quick to build
- Added Reset Pose and Reset View buttons
- Only the player who placed a stand can open or edit it, operators can always edit
- Breaking a stand always drops the item inside it
- Stands resist explosions by default
- Added config options for explosion resistance, owner protection and owner-only breaking
- Added a crafting recipe: an iron ingot over three polished deepslate makes two stands
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:aNW1T7GO:nhW6otbX"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aNW1T7GO:nhW6otbX"
}

