Links
Tags
Creators
Details
1.0.2
Compatibility
Changes
This release introduces a new feature and fixes a major bug that 1.0.0 & 1.0.1 had.
Features introduced:
- You can now set the slot for an item and the item will appear in the slot you set in the configuration. Fixes:
- You can now define the same item twice, previously, you couldn't.
⚠️ This update includes breaking changes to the configuration file and you will have to manually update your configuration, the changes are listed below:
Here is an example of what the configuration looks like now:
miner-cart: # Identifier used internally by the plugin.
name: "&9Miner's Cart" # Displayed in the Minecart's Chest GUI as the title.
# List of items that will be included in this preset.
items:
0: # Slot the item should be added in. Slots begin from 0.
material: "IRON_PICKAXE" # The Item Name.
display-name: "&fMiner's Pickaxe" # The Name of the item displayed to players.
# Lore of the Item displayed to players.
lore:
- "&7From the deepest depths of the caves."
# Item Enchantments
enchantments:
EFFICIENCY: # Enchantment Name.
level: 4 # Enchantment Level.
1:
material: "STONE"
display-name: "&dSpecial Stone"
lore:
- "&7I don't know why!"
amount: 64
2:
material: "STONE_BRICKS"
amount: 64
3:
material: "COOKED_PORKCHOP"
amount: 16
4:
material: "COBBLESTONE"
As you may notice from looking at the configuration, here's what's changed:
- Item Names are now defined under the
materialkey. - Where once item names were defined, now the slot is defined.
Please make sure to update your configuration, else, it will not work!
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:eIiCNJeJ:2r7obSzb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:eIiCNJeJ:2r7obSzb"
}

