Tags
Creators
Details
1.0.8+1.21.1
Compatibility
Required content
Changes
This update resolves issues with add-ons registering the same Block Entity by implementing a queue system in Platform's Feature Manager. Add-on developers can register their blocks with Villager Coin and the Feature Manager from Platform will register them with their Block Entity at the end of feature initialization.
Added
- Added
maximumCoinBankCurrencyValueoption to allow controlling the maximum currency value of Coin Banks. This option is set to the maximum Integer value by default. - Added
addCoinsToModdedStructureLootTablesoption to allow forcing coins into loot tables for non-vanilla structures. If a structure's loot table is modified by a data pack this mod will not make any modifications. - Added
addCoinsToModdedMobDropsoption to allow forcing coins into loot tables for non-vanilla mobs. - Added additional keyword configuration files for inclusion, and exclusion, of coins in modded loot tables and mob drops.
Changed
- Moved coin registrations for mob drops to Entity Type tags. This allows datapacks to add coins to entities.
- Changed supported Platform version to 1.3.0. This adds queues to the Feature Manager.
Fixed
- Add-ons now properly load shared block entities as intended. Coin Banks and Coin Stacks are now added to lists at registration and included in the Block Entity registration at the end of Platform's Feature Manager's loading queue.
- ItemStacks in Merchant Trades now properly maintain their components.
- Coins now drop appropriate amounts depending on the type of mob.
- Fixed an issue with Looting 3 swords causing an excessive amount of items to drop.
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:jEjEEHLL:Sw9N0FWH"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:jEjEEHLL:Sw9N0FWH"
}

