How limited and API is it in relation to modded block entities?

[UnclearAnonymous]

Hello again, I've recently been talking to other mod developers about adding compatibility with their mods, such as lootr, quark, betterend, and betternether. However, when I spoke with the creator of supplementaries, he believes it won't be possible due to the mod's limitations, even for blocks that should be simple like the spider head, because the spider head is only doable on Neoforge as there we have emissive block quads. Is it possible to work together to perhaps achieve compatibility? MehVahdJukaar/Supplementaries#2069

[maDU59]

Hi, I'll try to be as clear as possible.
Here are the mods I plan to add compatibility with once the API is good enough: Sophisticated storage, Lootr, Quark, Better end, Better nether and Iron chests (so unless the dev of the mod want to do it, I'll probably do it myself, built-in into obe)
As for the API, there is a USAGE.md file that says what it is possible to do with it. The planned additions are the following:

• Being able to register a transformation provider (for block entities like modded chests where the model is not rotated in the same way as the vanilla ones)
• Being able to register a model layer location provider (for block entities where the model is not the same as the vanilla one)
• Being able to register a whole new model provider (for fully custom modded block entities)

[UnclearAnonymous]

Currently, the devs of Quark(Partonetrain) and Lootr(noobanidus)they seem interested in the idea, probably will be helpful

[maDU59]

Could the discussions be linked here please?

[maDU59]

Oh those are the links to the discussions, not the mods, nvm

[maDU59]

Thanks a lot! Quark's dev seems to have tried using that API and seems ok about adding obe's compatibility into quark, that's awesome! Tbf I would not have asked to the developers and would've done the compatibility myself, you saved me a lot of time by asking, I appreciate it!

[maDU59]

1.1.7 improved the API!
It is now possible to register a custom transformation to apply to a group or a block entity type as well as a custom model provider.
I believe the only thing left that could be needed are:

• A fully custom model baker
• The ability to have a custom renderer that renders even when the block entity is replaced by a model (i.e. transparents chests where you can see the items inside)
• Being able to register per-block instead of only per-group and per-beType