Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated last year
All versions
1.9.0
Release
NBT Editor v1.9.04 years ago 678
Compatibility
Minecraft: Java Edition
1.19–1.19.2
1.18.x
Platform
Fabric
Supported environments
Client-side
Client and server
Required content
Unavailable version
Changes
Main Features:
- Now supports 1.18
- /nbt export <give|get|cmdblock>, which allows you copy a command or get a command block to receive the item you're currently holding
- The expand button in the editor now opens the value of the current path when no key is selected, allowing you to access the entire root tag at once if the path is empty
- There is a new text format, which is used in all the text related commands (refer to /get help textformat). This can be disabled in the config, which switches to the old JSON system
- /itemfactory name <name>, which names the item you're holding (and supports the text format)
- /itemfactory unstackable, which gives a random UUID to the item you're holding
- Shortcut commands, which can be enabled in the config (/nbt config). This allows you to, for example, run /lore instead of /itemfactory lore
Small Features:
- The config menu now uses the standard menu format (the same format the attributes and enchantment editor uses)
- The config menu has more descriptive tooltips
- The "Key Fix" config option has been renamed to "Mac Border Patch," and is now colored red on Mac computers
- New Mac users have the Mac Border Patch enabled by default
- There is now a config option to disable checking for updates
- /signature is now an itemfactory (use /itemfactory signature to access it)
Bug Fixes:
- The Mac Border Patch config option is now checked in the expand button's menu, fixing rendering
- The rename item feature inside the NBT editor now supports navigating with arrow keys
- /itemfactory lore's command suggestions now start with /itemfactory lore instead of /lore
- When opening strings in the NBT editor, true and false is now converted to "true" and "false," rather than 1b and 0b, which caused issues with text
Technical & major code changes:
- The language file's keys are now more consistent
- ConfigScreen's config options have been renamed with the language file
- Each command in /get <cmd> now has its own class in a package
- The command system was redone to allow for shortcuts
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:oKqAWbFD"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5Osk0m1G:oKqAWbFD"
}
