Skip to content

Compatibility

Jump to bottom
embeddedt edited this page Sep 27, 2023 · 17 revisions

In order to avoid confusion and frustration over Embeddium's mod compatibility policy, this document aims to provide objective categorization of interactions between Embeddium and other mods, and outline the exact support policy for each.

The overwhelming majority of mods are regular content mods that do not patch vanilla chunk rendering, Rubidium chunk rendering, or access Rubidium internals directly. For the most part, these mods are expected to work out of the box, and if there are issues, it is usually Embeddium's fault, and should be reported to Embeddium.

There are, however, some mods that require more invasive patches to accomplish their rendering. It is usually not trivial to support these mods from Embeddium's end as it would require custom logic to be added for each mod (which is not maintainable long-term). Often, the issue is relatively easy to solve from the other mod's end, and I am happy to work with developers to provide suggestions to reimplement their code in a manner that works regardless of whether or not Embeddium is installed.

Known incompatibilities

  • [1.20.1] Rubidium addons - on 1.19.2 and earlier these will work. On 1.20.1 there are issues since Embeddium upgraded to a newer version of Sodium, and you should look for Embeddium versions of the same mods (for example, Embeddium Extra and TexTrue's Embeddium Options).
  • [1.18.2/1.19.2] Effective - it relies on a mixin into vanilla chunk rendering to know when to display particles. Fixes have already been provided to the mod, but it has not received an update since October 2022.
  • [1.20.1] Physics Mod - interacts with Sodium code directly, and therefore broke when Embeddium upgraded to Sodium 0.5.2.

Former incompatibilities

  • [1.20.1] Snow Real Magic versions before 9.0.2, as the mod uses mixins into Sodium internals, which will break with updates.
  • [1.20.1] Some Create blocks didn't render by default with Rubidium/Embeddium; updating to Create 0.5.1e or newer should resolve this. If you cannot update for some reason, use the workaround here at the cost of degraded performance.
Clone this wiki locally