1.7
Compatibility
Changes
Added Impactor compatability (https://modrinth.com/mod/impactor)
Adding this made me redo how we do the rent logic as impactor can use decimal points, this may break a few things but through my testing it has not just yet, I added a check when server starts to check the format so that should catch any issues and fix them before causing any issues.
Also fixed the create command always showing (spur) by adding a check what mod/currency we're using instead of hardcoding spurs, not even sure why I still had that, sorry
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:DPSQpRIv:CMZ6PA6w"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:DPSQpRIv:CMZ6PA6w"
}

