Tags
Creators
Details
4.16.15
Compatibility
Changes
Custom Item Stack Changes
This update introduces the new StackReference and StackIdentifier classes, that provide a lot of features to reference external Items (from like Oraxen, MMOItems, etc.) and replace the old very limited APIReference.
CustomItem ⇾ StackReference
From this update onward CustomItems are no longer used to reference external Items, instead that is the task of the StackReference.
The only purpose of the CustomItem is to represent the well... CustomItem created via WolfyUtils. They do use a StackReference to wrap external stacks, but are no longer used as a plain reference.
APIReference ⇾ StackIdentifier
APIReferences are now replaced by StackIdentifiers, and no longer keep track of the amount and weight, because those properties are now part of the StackReference.
StackIdentifiers only contain the info required to identify the external item stack, like an ID or name.
So in return, plugins requiring references to external stacks no longer have to use CustomItems everywhere and no longer need to accept the overhead that comes with it. Instead, it only requires the StackReference, which contains a lot less data, and has a lot less overhead.
Changes
- #66 - New StackReference System to replace old APIReferences
- #72 — Replace NMS GUI Generation with GUIInventoryHolder
- Fixes GUIs not opening on Paper servers
- #74 - Update paper-plugin.yml & Add missing plugin dependencies
- Fixes ExecutableBlocks and ExecutableItems NoClassDefFoundError
- #68 - Support for 1.20.3
2110329f- Change nmsutil 1_20_R3 to use 1.20.4 mappings This should still work with 1.20.3, because of the very minor changes, but realistically there is no reason to still use 1.20.3!9434dee— Only handle ArmorEquipEvent when CustomItems are involved121cf29— Add debug agent to docker container771fb79— Fix Smithing Recipes in 1.20.29af73f77— Fix NPE in MythicMobsStackIdentifier for stacks without NBT tag2fb08e7d- Remove 1_16_R3 nmsutils (1.16.5 is no longer supported!)aa6a119b- Bump nbtapi-api & nbtapi-data to 2.12.2
Full Changelog: v4.16.14.1...v4.16.15
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:l1d4bZ1h:xCGKlFAd"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:l1d4bZ1h:xCGKlFAd"
}

