Links
Tags
Creators
Details
1.0.0
Compatibility
Changes
๐ DivinityEconomy Arrives on Modrinth: A Matured and Robust Minecraft Economy Plugin ๐
We are proud to announce the release of DivinityEconomy on Modrinth, a groundbreaking Minecraft economy plugin that has been in active private use and development for over 2 years. With its well-tested features and compatibility with Minecraft versions 1.19.x, DivinityEconomy promises to deliver an unmatched in-game economy experience.
๐ค Vault Integration and Compatibility ๐ค
Although DivinityEconomy can function independently, it has a soft dependency on the popular Vault plugin. Vault is not required for DivinityEconomy to work, but it is highly encouraged as it allows for seamless and cohesive usage between various economy plugins. By integrating with Vault, DivinityEconomy extends its compatibility and ensures a smooth experience for server owners and players alike.
Get Vault
๐ก Optional Placeholder API Support ๐ก
DivinityEconomy offers optional support for the Placeholder API. If server owners choose to enable this feature, they must have Placeholder API installed alongside DivinityEconomy. By supporting Placeholder API, DivinityEconomy further enhances its customization options and versatility, allowing server owners to create even more engaging and immersive economic experiences.
Get PlaceholderAPI
With its robust and matured features, DivinityEconomy stands out as a top-tier Minecraft economy plugin. As the plugin makes its official debut on Modrinth, Minecraft server owners and players can now enjoy an unparalleled in-game economy experience backed by years of development and refinement. Don't miss out on the opportunity to elevate your Minecraft server with DivinityEconomy.
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:O7AXNsl4"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:pYiIJ4xC:O7AXNsl4"
}

