Tags
Creators
Details
1.2.7
Compatibility
Changes
Technical Performance improvement.
-
Service Provider Optimization. Improved API lifecycle and dependencies, allowing the same supplier to be used throughout the plugin's lifecycle. 37 % improvement according to the tests, with a simulation of 100 threads and 1000 requests declared in the tests.
-
Proxy pattern implemented in suppliers api to optimized life cicle objects.
-
GUI Performance Optimization: Asynchronous data loading. Notable improvement in TPS stuttering.
What's Changed
- merge from base. by @federkone in https://github.com/BlockDynasty/BlockDynastyEconomy/pull/39
Full Changelog: https://github.com/BlockDynasty/BlockDynastyEconomy/compare/v1.2.6...v1.2.7
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:Hvy9yxIz:JYxdudhV"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:Hvy9yxIz:JYxdudhV"
}

