Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated last year
All versions
1.8.0
Release
NBT Editor v1.8.04 years ago 477
Compatibility
Minecraft: Java Edition
1.19–1.19.2
Platform
Fabric
Supported environments
Client-side
Client and server
Required content
Unavailable version
Changes
Main Features:
- Much more support for /open (previously only chests, barrels, and shulker boxes were supported):
- + Trapped chests
- + Armor stands & other spawn eggs, for armor and held items
- + Furnaces, blast furnaces, & smokers
- + Brewing stands
- + Campfires & soul campfires
- + Dispensers & droppers
- + Hoppers
- + Jukeboxes
- + Lecterns
- + Item frames & glow item frames
- Version checker (when the game starts, the mod checks for an update)
- /itemfactory attributes newuuids: re-randomizes the UUIDs on the attributes
- Air editing support & a related bug fix - refer to Issue #16 for more information
Small Features:
- The attributes itemfactory now has an autofill button for: the maximum value, minimum value, infinity, and negative infinity
- The message that prompts /get lostitem now has a "Click to execute" hover event (clicking worked previously, just without the hint)
- The client chest is now loaded asynchronously, to slightly speed up the loading time when there is a lot of data
- [Advanced] All error outputs that used e.printStackTrace() previously now use the logger with a message for context
Bug Fixes:
- Ctrl+Click no longer overrides previous enchantments, like it worked before v1.7.0. (It continued to work correctly for enchanted books specifically.)
- The client chest's locked slots feature is now passed onto inner containers when using Ctrl+Space
- UUIDs are now kept for unchanged attributes in the attribute itemfactory (previously every save randomized every attribute's UUID)
- Removing all the attributes in the itemfactory now also removes the AttributesModifier tag
- After changing the item's type in the nbt menu, previously the first action (like adding a tag) would not work
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:5Osk0m1G:taEMdmRM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5Osk0m1G:taEMdmRM"
}
