![Phoenix Crates [Free]](https://cdn.modrinth.com/data/9hyTHJcs/49143c1f472890084ead82fd52e6195d7c8832bc_96.webp)
Phoenix Crates [Free]
Phoenix Crates is one of the most exclusive and unique crate plugin you can find on the market. With a super customized animation system that allows to build your own animations, we also support customized models and customized items.
Tags
Creators
Details
6.8.0
Compatibility
Changes
Enjoying the plugin? A quick review really helps us grow! If you have any issues make sure to contact us before leaving a review.
Changelog:
feat: in-game menu layout editor
feat: migration from CrazyCrates and ExcellentCrates
feat: standalone /virtualkeys and /paykey commands
feat: crate event actions for opening, winning, closing and denied openings
feat: configurable click for opening a crate or its preview
feat: placed crates menu in the editor
feat: key skips cost option in the linked keys menu
feat: resetOpenings, setOpenings, setGlobalWinLimit and setPlayerWinLimit commands
fix: holding a crate key cancelling the whole interaction
fix: placed crates kept after deleting their crate type
fix: resetKeyAll skipping online players, now with a progress bar
fix: CS:GO animation not stopping in the centre
fix: items newer than the item library in crates, keys, GUI animations and migrations
fix: ModelEngine and BetterModel crate clicks
fix: ModelEngine and BetterModel preview menu
fix: ModelEngine and BetterModel model flicker when an opening starts
fix: adventure mode opening the preview on right-click
fix: crate sessions not ending on world change on Folia
fix: reward commands running on the wrong thread on Folia
fix: /crates reload reading files on the main thread
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:9hyTHJcs:k7lW5XIp"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:9hyTHJcs:k7lW5XIp"
}
