The Idfix mod attempts to resolves ID conflicts for blocks and items for mods. Now you can install lots more mods without having to resolve ID conflicts.
Idfix Minus is the new iteration of the Idfix mod. It overrides the (broken) Minecraft Forge Id resolving algorithm. With Idfix Minus, all fixes to block and item Id conflicts go directly to mods’ config files. It’s called Idfix Minus because after the conflicts are resolved, you can remove Idfix Minus mod, and things will keep working. The downside of Idfix Minus is that it doesn’t fix conflicts for mods that don’t use forge configuration module.
Idfix Minus creates a list of all items/blocks Ids named idfixminus.txt. The existence of this global file is what allows to fix the not working Forge ID resolving algorithm. When all Ids are esolved and written into mods’ configuration files, you can remove both the Idfix Minus mod and idfixminus.txt file. But, if at later point you want to add another mod to your set, you have to have both Idfix Minus mod and the idfixminus.txt present. So it’s a good idea to keep the latter forever. In case idfixminus.txt is lost, you can regenerate the file by running minecraft with Idfix Minus installed: do that before adding new mods.
Q: I get an error: A mod has attempted to assign BlockID XXX to the Fluid ‘diesel’ but this Fluid has already been linked to BlockID YYYY. Configure your mods to prevent this from happening.
A: From what I understand, this is happening because two mods are setting fluid (a special concept introduced by minecraft forge) named ‘diesel’ each to its own block. Forge does not want to deal with a situation like this (even though it should), and just exists with an error. This would happen even without reassigning IDs, so this is not a problem 0f Idfix.
MickyFoley has suggested an easy solution:
• Open forge.cfg
• Locate B:forceDuplicateFluidBlockCrash=true
• Set it to B:forceDuplicateFluidBlockCrash=false
Q: A game crashes in a very suspicious way, and after a long time of staring at “shutting down internal server”, I find “java.lang.OutOfMemoryError: PermGen space” in game logs.
A: This is an oddity of Java. Fix it by adding -XX:MaxPermSize=128m to your JVM Arguments option of your profile in launcher.
Q: I still get block conflicts even after installing the mod.
A: (this only applies to Idfix – not Idfix Minus) Some mods don’t want to play nice with an external mod changing their IDs. MrCrayfish’s Furniture mod will silently ignore everything, but will use incorrect IDs when interacting with its blocks, producing very unwanted results. AE will refuse to create a block if it thinks there might be a conflict. My mod resolves conflicts when mods create blocks with conflicting IDs, but AE stops working before that. So, Idfix by itself does not have a solution for a problem like that. When you are creating a pack of mods and don’t yet have a world populated with blocks, there is a way to handle this problem by letting those mods that don’t play nice with Idfix claim IDs they want:
1. Delete the Idfix.txt file, delete configs directory.
2. Move all mods away from the mods directory.
3. Put mods that don’t play nice (you usually can figure out what those are by examining log files) and idfix mod into the mods directory.
4. Start the game. Pray it works. If it doesn’t, you’re on your own (but most often it will).
5. Put all mods back into the mods directory.
What happens is those bad mods receive IDs that they want, when launched without all other mods, and Idfix remembers which IDs those are. After this, when IDs for bad mods are stored in the idfix.txt file, you can add all other mods to the mods directory, and it’s going to work.
The 1.6+ installers use the new minecraft launcher. If you have not used the new launcher yet, make sure to run the installer at least once. Log into minecraft and load the latest version/release. Then run installer and install the mod.
If you already have a modded profile/version, you can have the installer install it to that version. If you leave it set to “(Default)” then the installer will keep the default structure for installs and will only create a modded profile if one is not present. See “Default Mod Profile” below for the version of minecraft where this mod will install.
The installers will install all mods that use the same profile into the same mods folder/jar.
The installer only needs one default version of minecraft in the versions folder to install a mod.
If Forge/ModLoader is not present then installer by default will add a version of Forge/ModLoader this mod is compatible with.
Internet Explorer users:
When downloading the .exe version of the installer, save the installer to a location like desktop, then run it. Do not run it straight from the browser, if you do you might get the “Skydaz Addons has stopped working”.
Mod Version: v1.0.0 for Minecraft 1.6.4
Mod Prerequisite: Forge
Mod Uninstall Option: Yes
Default Mod Profile: Forge
This mod uses Forge. The default setting will install mod and if not present, Forge to Forge profile. If you want the mod installed to another profile select the version using the installer and then install.
PLEASE CREATE A BACKUP BEFORE INSTALLING ANY MODS – START WITH CLEAN MINECRAFT AND YOU WONT HAVE ANY ISSUES!!! I AM NOT RESPONSIBLE FOR MESSED UP MINECRAFT. YOU HAVE BEEN WARNED.