Tags
Creators
Details
Licensed MIT
Published 4 years ago
Updated last year
All versions
1.13.0
Release
NBT Editor v1.13.03 years ago 9,614
Uploaded by
Compatibility
Minecraft: Java Edition
1.20–1.20.4
1.19.x
1.18.x
1.17.x
Platform
Fabric
Supported environments
Client-side
Client and server
Required content
Any compatible version
Changes
Main Features:
- NBT Autocomplete integration - when that mod is also installed, you will now get NBT suggestions, including tag names (use alt to navigate the dropdown in multi-line fields)
- Color selector for custom colors, instead of just a hex input
- Customizable command aliases (in /nbt config), with built in "extreme aliases" - one or two character aliases
- Item size tooltip - shows the bytes/kb/mb/gb of an item (must be enabled in /nbt config)
- Unbreakable itemfactory (/itemfactory unbreakable, /if ub)
- Container support for chiseled bookshelves, suspicious sand & gravel, and decorated pots
- Glowing signs color dropdown
- Client chest pages can now be named
- /clientchest now can take the page number or a page name as an argument
- Page Up and Page Down keys now can be used to navigate the client chest, with Shift for jumping (use /nbt config to inverse the keys)
- Made scrollbars better and added them to the multi-line text fields
- Cancel option for the shortcuts and aliases config
- The max scroll speed is now 10, and defaults to 5 (instead of a max of 2 with 1 default)
- Xantrisse has been keeping pl_pl up to date!
Bug Fixes:
Optional dependencies
Any compatible version
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| nbteditor-1.13.0-dev.jar | Unknown | 869.28 KiB |
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:LHooCATc"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:5Osk0m1G:LHooCATc"
}
