Tags
Creators
Details
Licensed CC-BY-NC-SA-4.0
Published 9 months ago
Updated 2 months ago
All versions
1.1.0
Release
SpyCore 1.1.02 months ago 13
Compatibility
Minecraft: Java Edition
1.21.x
Platforms
Bukkit
Paper
Purpur
Spigot
Required content
Any compatible version
Any compatible version
Changes
Changelog - SpyCore
[1.1.0] - 2026-09-04
Added
- Native Target Operators: Expanded tab completion to suggest
@sand@efor/spy world tp. - Root Command Alias: Added
/spy tp [target] <world>directly matchingplugin.yml'sspy.tppermission node. - Automated Hibernation Scheduler: Activated a recurring 60-second world hibernation checker in the plugin lifecycle so inactive worlds automatically unload.
Fixed
- Player Death Inventory Loss: Fixed critical bug in
onPlayerRespawnwhere a dead player's empty inventory was saved to disk, permanently wiping saved world items. - Target Operator Name Collision: Resolved command ambiguity where
/spy world tp <world>failed if an online player's name matched a world alias. - PVP Projectile Bypass: Fixed projectile damage (arrows, tridents, splash potions) ignoring
pvp: falseinWorldSettingsListener. - Spawn Point Hijacking: Removed erroneous check that reset world spawns whenever a player landed from altitudes Y >= 249.
- Coordinate ClassCastException: Fixed
ClassCastExceptioninPlayerProfilewhen reading whole-number coordinates from YAML files. - Metadata Path Corruption: Replaced fragile dot replacement with structured tokens to prevent dotted world names from being mangled.
- Event Handler Registration: Added explicit
HandlerListdeclarations toSpyWorldCreateEvent,SpyWorldLoadEvent, andSpyWorldUnloadEvent. - Thread-Safe Async Inventory Serialization: Cloned
ItemStack[]arrays synchronously on the main thread before dispatching to async file I/O.
Changed & Performance
- Java 21/25 Build Stability: Eliminated fragile annotation processing dependencies in favor of standard native Java getters and setters.
- Clean Packaging: Configured
maven-shade-pluginwith clean packaging to preventdependency-reduced-pom.xmlclutter, and pruned unused dependencies.
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:Arhqr8BU:d4lgBeIO"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Arhqr8BU:d4lgBeIO"
}

