All versions
1.1.0
Release
Item Restriction 1.1.0 (Spigot 1.21.x)5 months ago 40
Compatibility
Minecraft: Java Edition
1.21.x
Platform
Spigot
Changes
1.1.0
New
- Multi-version support: separate builds for Paper 1.20.x, Paper 1.21.x, Paper 26.1.x, Spigot 1.20.x, and Spigot 1.21.x
- Spigot compatibility: all features now work on Spigot servers without Paper-specific APIs
Fixed
NoSuchMethodErrorcrash on startup caused by deprecatedBukkitSchedulerAPI removed in Paper 1.21.xIllegalPluginAccessExceptionduring shutdown (tasks were being registered while the plugin was already disabled)- GUI click events were incorrectly routed, causing clicks in the player's own inventory to trigger GUI logic
- Death drop list mutation was unsafe on some Paper builds
- TNT Minecart chunk limit notification could fire for the wrong players
Improved
- All scheduler calls migrated to the correct API per platform (Paper 1.21.x uses
AsyncScheduler+GlobalRegionScheduler; older builds useBukkitScheduler) - Background save task is cleanly cancelled on shutdown with a final flush of any pending changes
items.ymldisk writes batched every 30 s instead of writing on every GUI click- Inventory scan throttled to once per tick per player
- Enchantment lookups cached to avoid iterating all enchantments on every inventory check
Potion API compatibility
- Paper/Spigot 1.20.x builds use the legacy
getBasePotionData()API - Paper/Spigot 1.21.x builds use the modern
getBasePotionType()API
Download the correct file for your server:
| File | Server |
|---|---|
paper-1.20.x |
Paper 1.20.1 – 1.20.6 |
paper-1.21.x |
Paper 1.21 – 1.21.3 |
paper-26.1.x |
Paper 26.1.x / 1.21.11 |
spigot-1.20.x |
Spigot 1.20.x |
spigot-1.21.x |
Spigot 1.21.x |
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:RWhQsFYB:eArG24hf"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:RWhQsFYB:eArG24hf"
}
