Describe the Addition
It would be incredibly convenient to me, for modpack development, to be able to specify multiple possible replacements in sequence such that if the first one doesn't exist (ie if a user has removed one of the mods), the swap can fall back to a second preferred option.
Example: I want to swap the slate from Blooming Nature out for the shale from Quark. If Quark is not installed, I would like the slate to be replaced with regular stone rather than remaining as slate.
I had hoped it would just work if I tried this:
{
"inputs": ["bloomingnature:slate"],
"output": "quark:shale"
},
{
"inputs": ["bloomingnature:slate"],
"output": "minecraft:stone"
}
But it seems like if a swap fails due to missing output, no more swaps are attempted on the block in question. Which does make some sense. But I would find it very handy to be able to do a fallback like this.
(Thanks, btw, for an incredibly useful tool!)
Screenshots and Videos
No response
Additional Context
No response
Describe the Addition
It would be incredibly convenient to me, for modpack development, to be able to specify multiple possible replacements in sequence such that if the first one doesn't exist (ie if a user has removed one of the mods), the swap can fall back to a second preferred option.
Example: I want to swap the slate from Blooming Nature out for the shale from Quark. If Quark is not installed, I would like the slate to be replaced with regular stone rather than remaining as slate.
I had hoped it would just work if I tried this:
But it seems like if a swap fails due to missing output, no more swaps are attempted on the block in question. Which does make some sense. But I would find it very handy to be able to do a fallback like this.
(Thanks, btw, for an incredibly useful tool!)
Screenshots and Videos
No response
Additional Context
No response