Tags
Creators
Details
Licensed CC-BY-NC-SA-3.0
Published 4 years ago
Updated last month
All versions
4.1-479
Release
4.1-4793 months ago 222.2K
Uploaded by
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Any compatible version
Changes
Quark 4.1-479 For Neoforge 1.21.1
Fixed the trowel thanks to LeoBeliik, and also snuck in an experimental module.
Fixes
- Fixed #5513 (and all related issues): Trowel Crash: Item must not be minecraft:air
- Fixed #5540: Redstone Randomizer Makes Incorrect Place and Break sounds
- Fixed #5541: Automatic Tool Restock can swap the trowel when it shouldn't
- Fixed #5545: Ladders missing #c:ladders item and block tag
- Fixed #5547: Jasper, Limestone, Shale, Myalite, Permafrost, and their polished varients, along with polished calcite, have incorrect stone tag
Changes
- Added a Conditional Tags datapack for Variant Ladders
- Polished stone blocks are no longer under the #c:stones item/block tags
Additions
- Added Vanilla Stone Clusters module, disabled by default, under the Experimental category. This is an attempt to restore part of the pre-1.18 version of Quark's Big Stone Clusters, where Granite, Diorite, and Andesite only spawn in biome-dependent clusters.
- If this module is enabled, a datapack (quark_vdo_vanilla_stone_clusters) will be loaded that sets the
ore_graniteetc. ConfiguredFeatures to size 0. - This module uses the BigStoneClusters module's blocksToReplace config.
- This is under Experimental because I don't know if the datapack will cause issues, and the default biomes probably need to be changed, and if enabled, triggers the "Experimental Settings" screen when loading a world and I don't know why!
- Despite this module's name, Calcite is still generated from the BigStoneClusters module.
- Please try it out and let me (Partonetrain) know what you think of this on the Forum or on Discord!
- If this module is enabled, a datapack (quark_vdo_vanilla_stone_clusters) will be loaded that sets the
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:qnQsVE2z:dGSYpGOo"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qnQsVE2z:dGSYpGOo"
}

