All versions
0.2.0+1.21
Release
Player Clone 0.2.0+1.214 months ago 526
Compatibility
Minecraft: Java Edition
1.21
Platform
Forge
Supported environments
Client and server
Changes
🛠️ Changelog - PlayerClone (System & Model Update)
✨ New Features & Improvements
- Automatic Model Detection (Slim/Wide): Fixed the issue where all clones were forced to the "Wide" (Steve) model. The mod now automatically detects if a skin uses the Slim (Alex) or Wide model and applies it to the clone in real-time.
- Complete Skin & Model Sync: Implemented
SkinDatato bundle both the skin texture and the model type, ensuring clones look exactly like the target player. - Modular Command Engine (Brigadier): Full re-engineering of the command system. It now functions as a native Minecraft command:
- Full support for
/execute(relative positions, selectors, command blocks). - Smart Tab-completion for categories and coordinates.
- Full support for
- Dual-Mode Syntax: The command tree now intelligently handles both single and multiple spawns:
Single:/playerclone <username> [category] [pos]Multiple:/playerclone <username> <amount> [category] [pos]
- Multi-Language Support (i18n): * Updated all help menus and messages for English and Spanish (ES, MX, VE) to match the new syntax.
- Added official French (fr_fr) support.
🔧 Technical Fixes
- Server-Side Skin Downloads: Fixed a critical bug that prevented skins from downloading correctly on dedicated servers.
- Cache Persistence: The server skin cache now saves the model type (Slim/Wide) alongside the texture to prevent unnecessary reloads.
- UUID Independence: Removed hard UUID dependencies for skins, improving compatibility across different account types.
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:I4ic4JJf:fAHQzjHK"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:I4ic4JJf:fAHQzjHK"
}

