1.4
Compatibility
Changes
Redid all commands from the ground up to be more intuitive and useful.
Setup & Table Linking
/qe link [profile] – Link the table you are looking at to a profile (e.g., default or vip).
/qe unlink – Makes the table you are looking at use the standard default settings again.
/qe reload – Refreshes the configuration file.
Managing Enchantments
/qe add [enchant] [level] to [item] [profile]
Example: /qe add sharpness 5 to diamond_sword
Grouped Example: /qe add [sharpness,unbreaking] [5,3] to diamond_sword (These will always roll together).
/qe remove [enchant] to [item] [profile]
Removes a specific enchantment from an item's possible pool.
/qe exclude [enchant] to [item] [profile]
Blacklists a vanilla enchantment so it never appears on that item.
Viewing Info /qe list profile [name] – See all enchants set up for a specific profile.
/qe list item [item] – See every profile that has special settings for that item.
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:aVh3GMqq:sEI8vNhB"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aVh3GMqq:sEI8vNhB"
}

