Enhanced Storage already has some integrations done with other mods (namely Reliable Recipe Viewer and Skyblocker). Naturally, I wanted to follow a similar code pattern to follow the maintainer's conventions.

However, these aforementioned integrations were done via reflection in order to keep the mods being integrated a soft dependency (which, by the way, is unnecessary as there are much saner methods to achieve this).

In order to create a plugin for SkyBlock Item List, you need to create a class implementing their Plugin interface in their API and add a skyblock-item-list entrypoint in your mod's fabric.mod.json.

With this in mind, this situation left me with three options if I wanted to make a pull request to Enhanced Storage:

1. Follow Enhanced Storage's maintainer's way of making integrations and use reflection. This would require the use of a Proxy to implement the Plugin interface from SkyBlock Item List, which is very much overkill for this use case. This would also require to somehow signal Item List to apply the plugin without adding an entrypoint in the mod's metadata file, as I would assume the maintainer would want to avoid this. For obvious reasons, I did not choose this option.

2. Forgo SkyBlock Item List's plugin API system and directly register the exclusion zones via reflection. I did not want to do this as it is a very hacky solution, and it would be more susceptible to incompatibilities should SkyBlock Item List ever decide to update their internal exclusion zone registration system.

3. Ignore the maintainer's conventions and actually add SkyBlock Item List as a dependency (which would still be considered a soft dependency). This is very poor practice when it comes to contributing to a project, so I couldn't pick this option out of principle.