Tags
Creators
Details
1.3.0
Compatibility
Changes
🚀 Key Highlights & Engine Upgrade
- Expanded Minecraft Version Support: Major internal refactoring now ensures stable and seamless support across all Minecraft versions from 1.14 up to 1.21.X!
- Enhanced Java 11 Compatibility: Optimized runtime execution and updated underlying library dependencies.
- ProGuard Code Protection: Integrated aggressive bytecode obfuscation and optimization rules, reducing total JAR size and increasing overall plugin performance.
- New Update Checker: Added a smart semantic version checker via Modrinth API to automatically inform server admins when a new release is available.
🛡️ Smartphone Features & Protection
- Drop & Storage Protection: Active event listeners now prevent players from dropping smartphones or moving them into storage containers (chests, hoppers, shulkers).
- Phone Removal System:
- Added
/phone remove [player]functionality allowing server staff to safely revoke smartphone items. - Integrated dedicated permission checks for phone removal commands.
🎨 Customization & Localization
- UI & Menu Overhaul: Updated layout configurations for
phone-menu.yml,contacts-menu.yml, andcontact-detail-menu.yml. - Improved Translations: Extended logging messages, refreshed configuration descriptions, and refined default text formats.
- Updated EULA & License: Config files now include comprehensive instructions and detailed licensing terms.
🛠️ Config Update Notice for Admins
Important: If you are updating from an earlier version, we recommend backing up your current
config.ymland GUI configuration files to let the plugin generate the new localized structures on startup.
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:aboJlNYd:6Vvv0l42"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aboJlNYd:6Vvv0l42"
}

