Links
Tags
Creators
Details
3.6.0-beta1
Compatibility
Changes
๐ DivinityEconomy 3.6.0 - Beta 1 (1.21.10) ๐
โ Updates โ
-
Updated to Minecraft 1.21.10
DivinityEconomy has been updated to be fully compatible with Minecraft version 1.21.10, ensuring seamless performance and integration with the latest game features and mechanics.
๐ชฒ Bug Fixes ๐ชฒ
-
Fixed Economy Calculation Bug
Resolved an issue where certain economy calculations were producing incorrect results under specific conditions.
-
Static means Static
Fixed an issue whereby disabling dynamic prices could still produce dynamic results.
-
Fixed Shutdown Errors
Addressed errors that occurred during server shutdown, ensuring a smoother and error-free shutdown process.
๐พ Vault Dependency ๐พ
DivinityEconomy is reliant on the renowned plugin Vault. Vault is a necessity for DivinityEconomy's functionality, enabling seamless integration amongst various economy plugins ๐
Acquire Vault Here ๐ฅ
๐ Optional Placeholder API Support ๐
DivinityEconomy offers optional support for the Placeholder API. If server owners elect to enable this feature, they must install Placeholder API alongside DivinityEconomy. By supporting Placeholder API, DivinityEconomy extends its customisation possibilities and versatility, allowing server owners to develop even more captivating and immersive economic experiences ๐ญ
Acquire PlaceholderAPI Here ๐ฅ
With its robust and matured features, DivinityEconomy establishes itself as a premium Minecraft economy plugin ๐ฐ As the plugin makes its official debut on Modrinth, Minecraft server owners and players can now relish in an unparalleled in-game economy experience, underpinned by years of development and refinement. Don't miss the opportunity to augment your Minecraft server with DivinityEconomy ๐
View On GitHub
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:pYiIJ4xC:iRUlFprb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pYiIJ4xC:iRUlFprb"
}

