Incompatibilities
This page will try to list and categorize based on impact all the incompatibilities the current version of Mine Mine no Mi has with other mods. Keep in mind these incompatibilities are mostly reported by players as we're unable to test compatiblity with every mod or modpack out there.
Unless otherwise stated in the details section the incompatibility was manually tested by a developer before being added.
While workarounds might exist this page will only note them based on how reliable, as such workarounds like "just don't use both mods" will not be noted.
The impact is noted as such:
- Minor, issues that do not affect the gameplay or its performance, usually graphical
- Major, issues that can affect gameplay or performance, no matter how rare or edge case it might be
- Critical, crashes on startup, world generation or very frequently during gameplay, crashes that rarely happen or require complex setups to perform will be downgrated to Major
- Fixed(?), fixed in theory, however large scale testing will be required to make sure its actually fixed
| Mod | Impact | Details | Workaround |
|---|---|---|---|
| Magma | Major | This is a server not a mod While using a Magma server mod commands will not be recognized and will not work | Somewhat |
| tombstone | Fixed(?) / Major | Note: It might still not fully work with certain config options such as One Fruit per World, thus the Major label, if no crash is going to be reported it will still remain as a Major one until that is fixed. | - |
| Structurize/Mine Colonies | Major | Crashes at specific points, this is a library mod used by Mine Colonies | - |
| offhandcombat | Major | Randomly crashes while in game, most likely due to NPCs | - |
| protocollib | Major | This is a plugin not a mod. Crashes with the custom mod explosions, might not happen 100% of the time as it might be based on what other plugins using protocollib are used in that server. | - |
| Ma Essentials | Major | While the "One Fruit per World" config option is set to EXTENDED using /invsee on a player with a fruit in their inventory will result in that fruit disappearing | Yes |
| Headshot | Major | Crashes when certain mod entities die Note: The report was made on the Forge port by chronos_sacaria, NOT the fabric version. | - |
| FTBChunks | Major | Crashes only when ability protections with block restoration enabled are used inside claims | - |
| Minecraft Comes Alive | Minor | All transformations, be them zoans or otherwise are busted, issue is only visual as far as we know however | Yes |
| optifine | Minor | Varies a lot from user to user but it generally has issues when it comes to custom rendering code such as Aura's overlay, especially when using shaders | - |
| obfuscate | Minor | Some animations will not play correctly | - |
| pehkui | Fixed(?) | - | |
| performant | Fixed(?) | Yes |
If you have any reports regarding incompatibilities make sure to let us know so we can update this list and maybe fix the ones that we can fix.
Workarounds
Ma Essentials
There are two solutions to this, neither of which is perfect:
- Avoid using "One Fruit per World" as EXTENDED while also using Ma Essentials
- Disable the /invsee command using Ma Essential's config:
[Commands.invsee]
#Enable command: /invsee
enable = false
Minecraft Comes Alive
In MCA's config turn to false the following option:
"enableVillagerPlayerModel": false, // true by default
performant
In performant's config the following options need to be turned false:
#Enable faster pathfinding, default = true
fastPathFinding = false
#Enables improved entity collision and movement calculations for any non item entity, default = true
fastCollisions = false
#Enable multithreading support for entities, requires fastCollisions to be enabled. default = true
multiEntities = false
Magma
Some people mentioned using the following mod (or really anything that acomplished the same task) fixes the issue. However this was not verified by us and you are risking bumping into different bugs by using this, the better workaround (at least for the moment) would be to not use Magma (especially since their 1.16.5 branch has been archived). A proper fix is planned, however it is not a big priority given how other similar hybrid servers exist out there.