This tool is for detect conflicts for blocks and items without having to run Minecraft. When adding mods, especially some of the complex ones, the game will crash before it gets to the point where it tells you the ID Conflicts. Many times, it's the conflicts themselves that cause the crash. Also, adding a mod to your game one mod at a time can be painful, and this tools allow you to add them all at once and debug the conflicting IDs at once.
I made this mod for troubleshooting my own problems and it helped out tremendously. However, I haven't done much testing on other platforms or other builds.
Installation:
Drop the IDConflictDetector.jar file into the Minecraft folder where the config folder is housed.
Use:
First make sure you don't have any of the resulting CSV files open in a program that locks files when running IDCD (ie, Excel, Notepad, etc. Notepad++ doesn't lock files however).
Run the jar file. If your computer is set up to run java files, it should work by executing it like an exe file. In Windows, you may have to right click it and select, "Open With," and then select, "Java™ Platform SE Binary".
Config Files:
Running the program for the first time will create two config files with default values:
1. IDCD_ConfigExceptions.txt for a list of config files to exclude.
2. IDCD_SectionExceptions.txt for a list of specific sections to exclude inside config files. Open up one of the examples in the spoiler below to see how it works.
These can be updated with whatever you need for your set up so you only see actual conflicts and not other random non-block/item IDs or values.
The Results:
Next the process will create 3 csv files.
IDCD_AllID.csv - this will hold all the IDs and what configs/entries are using them
IDCD_Conflict.csv - this will hold all the conflicting IDs and each config/mod that uses that ID. Some of these will not be real conflicts (like the number 1024 is often used for non-block ID type values like Barrel sizes).
IDCD_EmptyIDs.csv - This has all the unused block/item IDs.
The program works like a charm. Thank you very much for releasing it to the public. Also a short question, do I have to run the program every time I update the configs or does it update the files automatically after the first run?
Thanks for the complement! Unfortunately it does not auto update and you have to rerun for a fresh list.
However, since you get all the conflicts and all the empty IDs to use, I generally fix large chunks of IDs at once instead of rerunning it after each config.
Thanks for the complement! Unfortunately it does not auto update and you have to rerun for a fresh list.
However, since you get all the conflicts and all the empty IDs to use, I generally fix large chunks of IDs at once instead of rerunning it after each config.
Oh, if you meant this program's configs then yes, you still need to rerun after updating those. I may have misunderstood the first time I replied.
This tool is for detect conflicts for blocks and items without having to run Minecraft. When adding mods, especially some of the complex ones, the game will crash before it gets to the point where it tells you the ID Conflicts. Many times, it's the conflicts themselves that cause the crash. Also, adding a mod to your game one mod at a time can be painful, and this tools allow you to add them all at once and debug the conflicting IDs at once.
I made this mod for troubleshooting my own problems and it helped out tremendously. However, I haven't done much testing on other platforms or other builds.
Installation:
Drop the IDConflictDetector.jar file into the Minecraft folder where the config folder is housed.
Use:
First make sure you don't have any of the resulting CSV files open in a program that locks files when running IDCD (ie, Excel, Notepad, etc. Notepad++ doesn't lock files however).
Run the jar file. If your computer is set up to run java files, it should work by executing it like an exe file. In Windows, you may have to right click it and select, "Open With," and then select, "Java™ Platform SE Binary".
Config Files:
Running the program for the first time will create two config files with default values:
1. IDCD_ConfigExceptions.txt for a list of config files to exclude.
2. IDCD_SectionExceptions.txt for a list of specific sections to exclude inside config files. Open up one of the examples in the spoiler below to see how it works.
These can be updated with whatever you need for your set up so you only see actual conflicts and not other random non-block/item IDs or values.
The Results:
Next the process will create 3 csv files.
IDCD_AllID.csv - this will hold all the IDs and what configs/entries are using them
IDCD_Conflict.csv - this will hold all the conflicting IDs and each config/mod that uses that ID. Some of these will not be real conflicts (like the number 1024 is often used for non-block ID type values like Barrel sizes).
IDCD_EmptyIDs.csv - This has all the unused block/item IDs.
I don't see a program this small needed a license but just in case:
If you want to modify or use this program in some third party application, please ask for permission first.
I have a little jave program I made very very similar to this and its funny because I just started letting people know about it month ago but never uploaded it to the public and now someone has made this . lol just find it very ironic I mentioned my program a month ago and now its made and available to the public. I think mine is a little better because it has a config file I can edit and choose the location of the minecraft configs folder , and my program I made is going on two years old and its what I use on all mod packs I have made and a couple very popular packs I keep up to date for some folks.
Also people need to keep in mind that not all mods have it to where you can change the ids in the config . I have came across several mods to where the ids where not changeable and I had to actually decompile the mod and fix the id problem myself. There's several mods in the mod packs I manage I have decompiled and changed ids. So this id conflict detector you have here is not 100% Guarantee.
I have a little jave program I made very very similar to this and its funny because I just started letting people know about it month ago but never uploaded it to the public and now someone has made this . lol just find it very ironic I mentioned my program a month ago and now its made and available to the public. I think mine is a little better because it has a config file I can edit and choose the location of the minecraft configs folder , and my program I made is going on two years old and its what I use on all mod packs I have made and a couple very popular packs I keep up to date for some folks.
Also people need to keep in mind that not all mods have it to where you can change the ids in the config . I have came across several mods to where the ids where not changeable and I had to actually decompile the mod and fix the id problem myself. There's several mods in the mod packs I manage I have decompiled and changed ids. So this id conflict detector you have here is not 100% Guarantee.
Could you put a link in this thread to it? I'm no longer supporting this (dropped out of Minecraft myself) but anyone else who sees this could check out yours.
PS: It's coincidence, not irony Learned that from Castle, hehe.
I have a little jave program I made very very similar to this and its funny because I just started letting people know about it month ago but never uploaded it to the public and now someone has made this . lol just find it very ironic I mentioned my program a month ago and now its made and available to the public. I think mine is a little better because it has a config file I can edit and choose the location of the minecraft configs folder , and my program I made is going on two years old and its what I use on all mod packs I have made and a couple very popular packs I keep up to date for some folks.
Also people need to keep in mind that not all mods have it to where you can change the ids in the config . I have came across several mods to where the ids where not changeable and I had to actually decompile the mod and fix the id problem myself. There's several mods in the mod packs I manage I have decompiled and changed ids. So this id conflict detector you have here is not 100% Guarantee.
Summary:
This tool is for detect conflicts for blocks and items without having to run Minecraft. When adding mods, especially some of the complex ones, the game will crash before it gets to the point where it tells you the ID Conflicts. Many times, it's the conflicts themselves that cause the crash. Also, adding a mod to your game one mod at a time can be painful, and this tools allow you to add them all at once and debug the conflicting IDs at once.
I made this mod for troubleshooting my own problems and it helped out tremendously. However, I haven't done much testing on other platforms or other builds.
Installation:
Drop the IDConflictDetector.jar file into the Minecraft folder where the config folder is housed.
Use:
First make sure you don't have any of the resulting CSV files open in a program that locks files when running IDCD (ie, Excel, Notepad, etc. Notepad++ doesn't lock files however).
Run the jar file. If your computer is set up to run java files, it should work by executing it like an exe file. In Windows, you may have to right click it and select, "Open With," and then select, "Java™ Platform SE Binary".
Config Files:
Running the program for the first time will create two config files with default values:
1. IDCD_ConfigExceptions.txt for a list of config files to exclude.
DynamicConfig.cfg
default.mrot
DynamicLights
DynamicLights_dropItems.cfg
DynamicLights_mobEquipment.cfg
DynamicLights_onFire.cfg
DynamicLights_otherPlayers.cfg
DynamicLights_thePlayer.cfg
NEI.cfg
NEIAddons.cfg
NEIServer.cfg
NEISubset.cfg
ids.cfg,# biome ids
Thaumcraft.cfg,# Custom enchantments
Thaumcraft.cfg,# Entity id's
ThaumicTinkerer.cfg,# enchantments
These can be updated with whatever you need for your set up so you only see actual conflicts and not other random non-block/item IDs or values.
The Results:
Next the process will create 3 csv files.
- IDCD_AllID.csv - this will hold all the IDs and what configs/entries are using them
- IDCD_Conflict.csv - this will hold all the conflicting IDs and each config/mod that uses that ID. Some of these will not be real conflicts (like the number 1024 is often used for non-block ID type values like Barrel sizes).
- IDCD_EmptyIDs.csv - This has all the unused block/item IDs.
Download:Latest Version
License:
I don't see a program this small needed a license but just in case:
If you want to modify or use this program in some third party application, please ask for permission first.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumIdfix is awful, even more ID Conflicts with it.
However, since you get all the conflicts and all the empty IDs to use, I generally fix large chunks of IDs at once instead of rerunning it after each config.
I've only used it once and I think Logistic Pipes broke it... but it's still nice when it worked.
I don't use it any more just because I like having manual control over the IDs.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumLogistic Pipes didn't break it, IDFix broke Logistic Pipes, the way IDFix handle the IDs is very wierd.
The original post's download link is updated to the latest version.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumI have a little jave program I made very very similar to this and its funny because I just started letting people know about it month ago but never uploaded it to the public and now someone has made this . lol just find it very ironic I mentioned my program a month ago and now its made and available to the public. I think mine is a little better because it has a config file I can edit and choose the location of the minecraft configs folder , and my program I made is going on two years old and its what I use on all mod packs I have made and a couple very popular packs I keep up to date for some folks.
Also people need to keep in mind that not all mods have it to where you can change the ids in the config . I have came across several mods to where the ids where not changeable and I had to actually decompile the mod and fix the id problem myself. There's several mods in the mod packs I manage I have decompiled and changed ids. So this id conflict detector you have here is not 100% Guarantee.
I put it in the config folder and launched as a Java program and it did nothing.
PS: It's coincidence, not irony