Tags
Creators
Details
1.8
Compatibility
Changes
WARNING As this update contains quite a lot of changes, it is extremely recommended to MAKE A BACKUP of your current RealMines folder. Everything should convert smoothly but, if something goes wrong, please make sure to get support from the Discord server.
Two new features! Block-Sets and changed config structure.
As of version 1.8, there's a new config structure for RealMines. Inside the plugin folder there's now individual configuration files for each mine, with some changed config structure.
This was done to make support for the new feature: block-sets!
You can configure various block-sets for each mine. A block-set is a set of blocks pre-defined by an admin.
For example, say you define two block-sets: BS1 (Stone 50% and Dirt 50%) and BS2 (Glass 35% and Sand 65%) When the mine resets, you can configure it to go to the next block-set available or pick one at random.
This update also includes:
- Added list of break actions at bottom of mine's items.
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:fFHGsSxV:9pXg54ce"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:fFHGsSxV:9pXg54ce"
}

