1.3.6
Compatibility
Changes
First public release.
Pack Doctor turns "this mod's integration is slow or broken" into a config line, instead of making you delete the mod or edit classes out of its jar.
JEI
- Blacklist JEI plugins by full plugin UID (
irons_spellbooks:jei_plugin) or by bare mod id (irons_spellbooks, blocking every plugin that mod registers). JEI keeps working; only that mod's recipes stop appearing in the browser. logJeiPluginsprints every plugin UID at startup so you know what you can blacklist.autoBlacklistOverSecondstimes each plugin, writes a worst-first summary toconfig/packdoctor-timings.txt, and automatically skips any plugin that took longer than the threshold on the previous launch.0disables it.
Vanilla recipe book
disableRecipeBookskips building the recipe book's categories entirely.recipeBlacklistdrops just one mod's recipes from the recipe book and leaves the rest working - use this when only one mod misbehaves. JEI is unaffected either way.
Force-given join items
blockedJoinItemsremoves guidebooks and other items that mods hand you on first join with no config toggle. Acceptsmod:itemormod:*. Every removal is logged with the item, stack size and the rule that matched it.- Sweeps repeatedly rather than once, because Origins-style character selection and class mods can deliver items minutes after login.
- This permanently deletes items from player inventories.
mod:*includes gear the player crafted and armour they are wearing. Read the description before enabling it.
UI
hideSidebarButtonshides FTB Library's sidebar buttons over the inventory screen. FTB Library ships no toggle for them.
Compatibility
- JEI is an optional dependency. Without it, the JEI mixins never apply.
- Every mixin uses
defaultRequire: 0, so if a future JEI or Minecraft version moves a target the mod degrades to doing nothing rather than crashing. displayTest="IGNORE_ALL_VERSION"- not required on both sides. A client can use the JEI blacklist against a vanilla-Forge server, and a server can use the item blocker without requiring anything of its clients.
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:3H7uFJ6N:KGdoQjt3"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:3H7uFJ6N:KGdoQjt3"
}

