Custom mod support config? + Mod suggestions Forge

[Roadhog360]

Greetings. I hope you are doing well. First off, I think it'd be beneficial to have configs for players to add support themselves, if possible. The idea is they'd add a plank, and a log to the config and specify the wood name, and it'd register all types of wooden furniture using that plank's place sound and texture, and the log's textures too. Or maybe auto-registration? Although admittedly that sounds like it'd be... really difficult.

And I was hoping you'd add support for a few mods:

• Hellion's Sniffer+
• Upgrade Aquatic
• Quark
• The Outer End

And to bring these over to the Forge versions since they work on Sinytra connector perfectly from my testing:

• Promenade
• Terrestria
• Traverse
• Cinderscape

I think since Sinytra connector exists now, and possibly more ways to bridge mods between loaders will be added in the future, I suggest making it so the mod compat blocks have parity even if it may not be expected for the mods to be there; in case a connector allows the mod to be present. This way, you'd be prepared for any ports or connectors as the compat would already be there waiting in the code.

I may even PR this myself if it goes unaddressed as I feel motivated to contribute to mods that are in my pack at the moment. Maybe after I am finished with what I am currently busy with I'll consider taking a look. Let me know if you'd be open to the configurable mod compat, or auto-registration as a possible opt-in and in the case I decide to work on a PR, I will see what I can do for you. Happy decorating!

[Juuxel]

Sorry for the late reply to this issue too.

First off, I think it'd be beneficial to have configs for players to add support themselves, if possible. The idea is they'd add a plank, and a log to the config and specify the wood name, and it'd register all types of wooden furniture using that plank's place sound and texture, and the log's textures too.

Technically, it would be possible to bring Adorn's data generator into a production environment using virtual resource and data packs. It'd be an optional addon mod most likely, as the feature is generally not needed, but implementing it is not too hard as Adorn is pretty extensible.

Or maybe auto-registration? Although admittedly that sounds like it'd be... really difficult.

Auto-registration is not really feasible as the texture paths can't be pulled reliably without scanning model files.

And I was hoping you'd add support for a few mods:

Thanks for the list of suggestions. I've been slowly clearing out my backlog of compat mods and also making adding them less work. I don't know yet if I'll add them in the 1.21.x cycle or if it'll wait for 26.x, where I'll do more development after the ports.

As for the Sinytra Connector mods... they aren't really proper Neo mods, so I'm not sure whether I should add support for them or not. If there aren't any issues with compat mods needing different files in Adorn per loader in the future, I might just bundle all compat data in both jars to make things simpler.

[Roadhog360]

How I was thinking it would be handles is it would just check for the existence of that block ID. Compatibility would simply hinge on the presence of a specific blocks ID, which it would then take the information from if present for that piece of furniture.

This way, compatibility data wouldn't rely on a specific loader.

[Juuxel]

By relying on a specific loader, I just meant that in the past, the compat mods may have had differences depending on the platform which was reflected in Adorn's data files. (And before pack overlays were added, the files had to have different load condition formats for Fabric and Neo or Forge.) This problem is mostly resolved now as multiloader mods built from a single codebase have become the norm.