Conversation
Syntax sugar for cases where you may only want to exclude a mod if a config is set (or not set).
|
This is wrong : It doesn't use a supplier and checks for the config right away (might not be loaded And you can already do that with the current system by simply extending the class and adding your method |
To address this I'd have to rework the mod exclusions to use suppliers instead of TargetedMods directly. If someone needs a supplier, we can add that later, but as written it does exactly what I need it to.
Yes, that's obviously possible. It's also irrelevant, as the entire system could be (and used to be) implemented in a separate mod. I don't see any reason why these shims shouldn't be in Unimixins itself. |
|
I've modified the mod exclusions on a temporary branch to use BooleanSupplier instead of a raw boolean, this allows the condition to be evaluated during the |
|
Merged the BooleanSupplier re-implementation into this PR after some discussion in the Discord channel https://discord.com/channels/741043720241152001/1168018260105637928/1396154842237505618 |
Syntax sugar for cases where you may only want to exclude a mod if a config is set (or not set).
Current use case: a transformer in Hodgepodge that works with DAPI, but only if a slow RFB plugin is enabled.