
Mixin Blacklist
Disable mixins in other mods through a config
About this Mod
Mixin Blacklist allows disablling other mods' mixins through a config file. This is intended to be used in modpacks when a mod's mixin is causing issues and must be disabled but the mod license prohibits distributing a modified jar or you just want to avoid embedding a jar in the mrpack.
If Mixin Blacklist is used, certain mod behaviors may not work. Please do not report such issues to the original mod authors, the modpack author is responsible for this.
Configuration
On first run a config file will be created at config/mixinblacklist.json
"common": Mixins to disable on both client and server"mixinClassNames": A list of fully qualified mixin class names to disable, e.g.archives.tater.dyedvoid.mixin.ItemEntityMixin"targetClassNames": A list of fully qualified mixin target class names to disable all mixins for, e.g.net.minecraft.item.GlassBottleItem.
"client": Mixins to disable on the client only"mixinClassNames": A list of fully qualified mixin class names to disable, e.g.archives.tater.dyedvoid.mixin.ItemRendererMixin"targetClassNames": A list of fully qualified mixin target class names to disable all mixins for, e.g.net.minecraft.item.ItemRenderer.
Target class names must match the current mappings used. Outside of a dev environment, (Neo)Forge uses Mojmap and Fabric uses Intermediary. You can use Linkie to convert between mappings. In general, you shouldn't need to use Target Class Names in most cases.
Example Config
{
"client": {
"mixinClassNames": [
"archives.tater.dyedvoid.client.mixin.ItemRendererMixin"
],
"targetClassNames": []
},
"common": {
"mixinClassNames": [
"archives.tater.eatbottle.mixin.ItemsMixin",
"archives.tater.dyedvoid.mixin.ItemEntityMixin"
],
"targetClassNames": [
"net.minecraft.item.GlassBottleItem"
]
}
}
Support
The mod should work on any version as long as you are using Java 17+ as well as on Sinytra connector, even if not currently marked as supported. Please open issues if it does not work in some environments.
Available Versions
How to Install Mixin Blacklist on Your Server
Order Server
Order a Minecraft Java server with at least 3 GB RAM (4 GB recommended).
Set fabric Loader
In the panel under "Egg", select the fabric loader and matching Minecraft version (26.2).
Install Mod
Open the mod browser in the dashboard and search for "Mixin Blacklist". Click "Install" – done! Alternatively, upload the .jar via SFTP to the /mods folder.
Compatibility
Mod Loaders
Minecraft Versions
26.2, 26.1.2, 26.1.1 (+44 more)
Server-side
~ OptionalRecommended RAM
4 GB(min. 3 GB)Frequently Asked Questions
Mixin Blacklist server crashes on startup – what to do?
Most common cause: wrong fabric version or insufficient RAM. Check the server log (latest.log) for "OutOfMemoryError" or "Mixin" errors. With Mado Hosting: ensure at least 3 GB RAM is allocated and the loader matches the mod version (26.2). You can switch loaders with one click in the panel.
Is Mixin Blacklist compatible with fabric and quilt?
Mixin Blacklist officially supports fabric, quilt for Minecraft 26.2, 26.1.2, 26.1.1. The Mado dashboard automatically detects incompatible loader combinations.
Server lagging with Mixin Blacklist – how to optimize performance?
Recommended RAM: 4 GB (per 8 players). Use /spark profiler to check if Mixin Blacklist consumes the most tick time. Common fixes: reduce server view-distance to 8-10, install "performant" or "starlight" as supplementary mods on Forge. With Mado Hosting, your server runs on NVMe SSDs with dedicated CPU cores for minimal latency.
Similar Mods
Rent Modded Server
Install Mixin Blacklist with just one click on your server.