Links
Tags
Creators
Details
Licensed MIT
Published 9 months ago
Updated 2 months ago
All versions
1.21.1pre-v1.0.2
Beta
VillageCraft 3 Essentials 1.21.1pre-v1.0.26 months ago 25
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Changes
VillageCraft 3 Essentials 1.21.1pre-v1.0.2
Additions
- Added Farmer's Delight Compat
- Added Aquaculture 2 Compat
- Added Better Archaeology Compat
- Added Yung's Biomes Compat
- Added Create Compat
- Added configurable countdown to automatically release players for /{town} jail commands
- Added configurable cooldown to /{town} jail commands
- Added configurable cooldown to /{town} kick commands
- Added wallet (16 extra currency slots in survival inventory)
- Added wallet button in main survival inventory
- Added configurable percentage of dropped wallet items on death
- Added server console logging for the following commands;
- /{town} jail
- /{town} kick
- /{town} pardon
- /{town} setjail
- /{town} setspawn
- Added jukebox recipe using currency gems
- Added enchanting table recipe using currency gems
- Added enchanting table animated currency texture
- Added missing tags to items and blocks
- Added punctured diamond, pulverised ruby, and shattered amber which drop when their respective ores are broken by a non-player
Fixes
- Fixed randomized diamond block, ore and deepslate ore block drops between diamond, ruby and amber variants
- Fixed recipe book unlocks not matching vanilla or modded equivalents
- Fixed inconsistent config file layout
Changes
- Rebalanced diamond, ruby and amber ore generation
Optional dependencies
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
Any compatible version
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:KotADrLx:LumvC2mM"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:KotADrLx:LumvC2mM"
}

