Tags
Creators
Details
Licensed CC-BY-NC-SA-3.0
Published 4 years ago
All versions
4.1-476
Release
4.1-4764 months ago 104.1K
Compatibility
Minecraft: Java Edition
1.21.1
Platform
NeoForge
Supported environments
Client and server
Required content
Changes
Quark 4.1-476 For Neoforge 1.21.1
More bugfixes! Yippee! There's still some things not working quite right, but I hope this release fixes all the major/fatal issues for now.
Fixes
- Fixed #5456: Crash on client startup / screen init: BackButtonKeybindModule NPE (this.backKey is null) on NeoForge 1.21.1 (Thanks auri-f5bde6)
- Fixed #5483: Singleplayer performance issue with expensive worldgen and EnhancedLaddersModule
- Fixed #5484: [1.21.1] Other mods' built in override recipe for stone tools doesn't work and only Quark's version load even if you set the mod to load after Quark
- Added a potential fix for #5492: Latest versions of Quark+Create (ClassCastException) issue Neoforge 1.21.1
- Fixed #5494: quark runes don't spawn in the loot tables
- Fixed Runic Etching Smithing Template duplication recipe using corundum when corundum is disabled (an alternative recipe using Amethyst Blocks now exists)
Changes
- Quark VDO has been split into different datapacks for each relevant feature. Each datapack now uses datapack filters to disable relevant vanilla recipes instead of overriding the entire file. This should fix problems with Quark always overriding certain data files no matter what.
- The Quark Programmer Art resource pack is no longer deployed to the instance's resourcepacks folder if the option is enabled. Instead, it is directly added to the resource pack selection screen under "Available", similar to other mods' optional resource packs. You can safely delete Quark Programmer Art.zip from your resourcepacks folder if it was previously deployed.
Additions
- Added a General config option to disable ALL Quark VDO datapacks. Only do this if you know what you're doing!
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:4yh9kJFj"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:qnQsVE2z:4yh9kJFj"
}


