You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm currently running a custom modpack and have encountered a situation where some mods do not respect ForgeTags/oreDict, despite items being named very similarly. Yes, it's the copper problem
The text was updated successfully, but these errors were encountered:
There is a conversion upgrade that's been disabled for some time now, that was designed to address this problem. Since many versions ago, the mechanic doesn't work anymore, so the upgrade needs more work to be reimplemented once again.
There are some plans regarding this work on the upgrade, including config settings, so watch this space.
The conversion upgrade will be returning shortly for 1.20.1 and 1.21.
The original implementation tried to be intelligent about what it could safely convert, but under the new tags system, I think it's almost universally unsafe to convert. So it will be a strictly whitelist-based system in the config, with a few ore-type entries seeded by default.
I'm currently running a custom modpack and have encountered a situation where some mods do not respect ForgeTags/oreDict, despite items being named very similarly. Yes, it's the copper problem
The text was updated successfully, but these errors were encountered: