Shrooblord

Alright. Well, I have contacted the mod creators in question. The thing is, these aren't just two liquids coincidentally named 'Blood' - I believe they serve completely uninterchangable purposes - or would the Forge dictionary sort that sort of thing out so that only one liquid named Blood would need be used? Well thanks anyway, Shrooblord

Hello forum and guys behind the Forge, I experienced an issue today combining two mods from Minecraft 1.7.2. The crash report itself is here (but its cause is pretty obvious and I will detail it below): So what's going on here is that the mod Tinkers' Construct by mDiyo and the mod Necromancy by AtomicStryker both introduce a liquid named Blood. Now before 1.7.x, this wasn't a problem, because blocks had different IDs and conflicts were resolved by editing the respective mods' config files. Now, with the changes introduced in the 1.7.x series of Minecraft (and following versions), block IDs no longer exist as such. Instead, blocks, items and liquids have names. Usually this is fine, but what happens when two mods try to add a new liquid with the same name? Well, yes, the game crashes like detailed in the crash report. Currently mods do not allow for block/liquid names to be altered by offering such options in their config files (and I have addressed this issue with the mod authors in question, rest assured), but I'd like to ask of you genius craftsmen behind Forge to come up with a safety net for situations like these. Could you create a feature in the newer versions of Forge that catches duplicate naming schemes and offers a way to resolve the conflict? I'm sure it would be a pain for users to have to go after the mod authors themselves and ask them to resolve the issue for them. It'd be great if you'd at least consider the idea. Thank you very much for what you've already done to support us Shrooblord