Bug first: while trying to change the black/whitelist of what the mod accepts/ignores via Configured, the text remained red and wouldn't allow me to press the apply button. For instance, if I want to add a 1x1 oak drawer from Functional Storage to the whitelist, I would expect to put functionalstorage:oak_1 in the dialog, but no matter what I put in it (including modifying the default whitelisted curios:curios_container),
Suggestion next: allowing wildcards would make white/blacklisting much easier. If I wanted to enable all Functional Storage blocks, just put functionalstorage:* in the whitelist config. Then if there's a more specific block in the blacklist, like functionalstorage:oak_1, that would block the more general wildcard whitelist. And same vice versa, if I want to blacklist mekanism:* but specifically enable mekanism:personal_chest.
Quickstack 1.19.2-6.1, Configured version 2.1.1
Bug first: while trying to change the black/whitelist of what the mod accepts/ignores via Configured, the text remained red and wouldn't allow me to press the apply button. For instance, if I want to add a 1x1 oak drawer from Functional Storage to the whitelist, I would expect to put functionalstorage:oak_1 in the dialog, but no matter what I put in it (including modifying the default whitelisted curios:curios_container),
Suggestion next: allowing wildcards would make white/blacklisting much easier. If I wanted to enable all Functional Storage blocks, just put functionalstorage:* in the whitelist config. Then if there's a more specific block in the blacklist, like functionalstorage:oak_1, that would block the more general wildcard whitelist. And same vice versa, if I want to blacklist mekanism:* but specifically enable mekanism:personal_chest.
Quickstack 1.19.2-6.1, Configured version 2.1.1