All versions
1.2.0
Alpha
Equipment Inscriber 1.2.0last month 18
Compatibility
Minecraft: Java Edition
1.20.1
Platform
Forge
Supported environments
Client and server
Changes
# Equipment Inscriber - Changelog
## v1.2.0 - 2026-08-31
### ✨ New Features
- **Recording Template System**: Brand new template mechanism to extract and store NBT data from equipment
- **NBT Extraction & Application**: Extract NBT from equipment using blank templates, or apply stored NBT to other equipment
- **Template Renaming**: Templates display as "Recording Template: xxx" after storing NBT for easy identification
- **NBT Preview**: Hover over templates to view stored NBT info, hold Shift to see all data
- **Multi-language Support**: Full Chinese and English localization
### 🔧 Improvements
- **NBT Filtering**: Configurable excluded NBT keys (Damage excluded by default)
- **Performance**: Cached tag generation results for faster startup
- **Server Support**: Fully compatible with dedicated server environments
- **UI Enhancement**: Cleaner and more intuitive GUI
### 🐛 Bug Fixes
- Fixed issue where Shift-clicking output slot caused item to disappear
- Fixed language file loading timing issue
- Fixed ConcurrentModificationException during NBT extraction
### 📝 Configuration
```toml
[general]
# NBT keys to exclude when extracting
excluded_nbt_keys = ["Damage"]
**⚠️ Known Issues:**
- **Tetra**: Extracting NBT may cause the original item to disappear (items are fully NBT-based, no base item exists).
- **Tinkers' Construct**: Extracting NBT may turn the original item into a composite of fixed material-based items.
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:7TBjYvTQ:wdRH4XgK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:7TBjYvTQ:wdRH4XgK"
}

