[Suggestion] Compatibility/porting between older Nether's Delight and My Nether's Delight
Mickeon opened this issue · 1 comments
Hello. We saw this mod being a neat overhaul to the already pretty neat Nether's Delight mod. While it would be lovely to make the switch from old to new (which is in active development), we're afraid we can't do that. Removing the old mod would cause all previously made food and blocks to disappear, since the IDs are entirely different.
My question is, would it be possible to make a compatibility layer of some sort? As in, converting the Nether's Delight identifiers if Minecraft/Forge does not recognise them.
I feel like there must be some sort of failsafe available to be listened to for this exact situation.
Possibly. There are events fired by Forge when missing mappings are found
for blocks and items that allow other mappings to be used instead. I
believe these are fired per mod domain, so doing conversion of entries from
that mod in THIS mod might be difficult. We can investigate a bit though
tor. 16. mai 2024, 23:19 skrev Micky ***@***.***>:
… Hello. We saw this mod being a neat overhaul to the already pretty neat *Nether's
Delight* mod. While it would be lovely to make the switch from old to new
(which is in active development), we're afraid we can't do that. Removing
the old mod would cause all previously made food and blocks to disappear,
since the IDs are entirely different.
My question is, would it be possible to make a compatibility layer of some
sort? As in, converting the Nether's Delight identifiers if Minecraft/Forge
does not recognise them.
I feel like there must be some sort of failsafe available to be listened
to for this exact situation.
—
Reply to this email directly, view it on GitHub
<#7>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD4VVBZN3R2PD3LGBSH7WQTZCUPF3AVCNFSM6AAAAABH27LEHOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGMYDCMZWGY2DMNI>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>