1.7
Compatibility
Changes
โจ New Features Slot-Based Permissions: Added support for per-slot permissions (rayzwardrobe.use.slotX). Admin View GUI: Admins can now view other players' wardrobes using /wardrobe view <player> [page]. Armor Return on Equip: When equipping a set, the currently worn armor is now saved back to the slot (swapping behavior). Back Button in Admin View: Added a back button to return to the admin's own wardrobe. Locked Slot Visuals: Slots without permission now show as locked (barrier icons) in the GUI.
๐ง Improvements Refactored Command Handling: Merged /rwcredits and /wardrobethemes into /wardrobe credits and /wardrobe themes. Enhanced GUI Logic: Improved permission checks and GUI rendering for locked slots. Better Equip Logic: Equipping a set now saves the currently worn armor back to the slot (if any). Admin GUI Read-Only: Admin view GUI is now non-interactive (view-only).
๐ Bug Fixes Fixed potential NPEs in permission checks. Improved inventory close handling to prevent memory leaks. Fixed edge cases in armor set saving and loading.
๐ ๏ธ Technical Changes Added adminViewTargets map to track admin viewing sessions. Added equals and hashCode methods to ArmorSet for better data integrity. Improved logging and error messages for better debugging.
๐ Permission Nodes Added rayzwardrobe.use.slot.* โ Access to all slots. rayzwardrobe.use.slotX โ Access to a specific slot (X = slot number). rayzwardrobe.admin.view โ Permission to use /wardrobe view.
๐ Commands Updated /wardrobe โ Now supports subcommands: credits, themes, view. /rwreload โ remains unchanged.
๐งน Removed Standalone commands /rwcredits and /wardrobethemes (merged into /wardrobe).
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:o3eYj7IM:riZPZOhe"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:o3eYj7IM:riZPZOhe"
}

