Tags
Creators
Details
4.0
Compatibility
Changes
4.0
MPM+
☑️ Mod Rewrite > A large portion of the mod has been rewritten to handle packets differently between the Server and Client. Less skin flickering. Better skin caching! More accurate animation handling, FOV positioning.
☑️ Data Handling > Data is now fully server side. Presets are local, no longer in one individual file. This prevents Preset Deletion. Configs can be made to prevent presets from being loaded and saved from the server too.
☑️ Permission Overhaul > An entirely built from the roundup Permission System for better syncing, and default configs for the server side. Better command management!
☑️ Size Command > Added a /setsize Command for modifying the visual size of players. Currently a little buggy, but its similar to CustomNPC+ Sizing.
☑️ Backported Animations > 3 New Animations have been added! Death, Yes, and No!
☑️ Other
- Removed useless refresh variables for more efficient client side handling
- Used Player Names for sending Packet Information and UUID for Saving to the Server Side
- Revamped Save Directory formatting (You may need to move your existing data / presets)
⚙️ Fixes
- Fix Imgur Links redirecting and returning steve / blank skins
- Fix Sitting Animation not syncing when teleporting
- Fix skin flickering when constant teleportation (now returns cached image)
- Fix wrong texture showing during error, Steve64 and Alex Textures Added
- Capes no longer flicker
- Permission Racing, permissions now load instantly to the client when logging in
- Fixed Floating Sitting (Error known with Galactic Craft persists)
- Fixed Bow Animation desyncing Headwear
- Cache now properly clears upon reconnecting.
Optional 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:F9Tquilr:LFbm6r2c"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:F9Tquilr:LFbm6r2c"
}

