1. Good. That is always my recommendation.
2. Sorry, I sometimes miss things (although I was also speaking to the other person with a problem, as well as you). So it must be how Forestry is coded. Forestry must expect the IDs to be exactly what it expects them to be.
Is IDR changing Forestry's IDs? If so try making it change a different mod's IDs and keeping Forestry's IDs. This may resolve the problem (but will still be an issue as if Forestry expects the IDs to be exactly what is in the config file then they have a compatibility issue...)
3. See the above. Again, try keeping Forestry's IDs the same (if they are not already). Otherwise there should literally be absolutely NO reason that IDR is causing a 'rendering' issue (which is what the exception claims is the problem).
Ok, ran it AGAIN, this time telling to to raise the priotiry of forestry to 1, then when forestry cam eup i tol dit to set it to default and change everythings elses ID's, but its still happening...
Hello, I have written my own version of ID resolver for 1.6.2.
It resolves ID conflicts for blocks, items, and enchantments; automatically without need to click that "assign all ids in reverse" button. You just put it into mods directory and it makes things work.
It's a simple mod with only three classes; no gui, no special config, just one file with a list of registered IDs.
I'm not sure if it's ready for release, but it does work with a bunch of mods I downloaded. It's also a bit faster: for my list of mods, with ID Resolver it takes 31 seconds to launch, while with my mod it's 24 seconds.
Thank you so much it works great i realy needed this mod im running a custom modpack i made with 30+ mods and i finally started getting id conflicts, i tried changing them myself but it was a lost cause there lol. Thank you for this awesome mod.
Ok, ran it AGAIN, this time telling to to raise the priotiry of forestry to 1, then when forestry cam eup i tol dit to set it to default and change everythings elses ID's, but its still happening...
Well. I'm not sure how IDR is conflicting with Forestry's render method... The only thing I can suggest now is to report it in Forestry's thread. If you chose to do so mention that you are using a third party updated version (and give a link either to the post from which you downloaded it or the download: right clicking the number in the upper right corner and selecting copy link location, then pasting will allow you to make a link to that post directly).
gubaguy: try removing all mods but forestry and id resolver, removing all configs, and then running minecraft. It should work, and ID resolver should reserve IDs for forestry. After that add all other mods.
How is this file formatted? As I already have a list of ids to change (just in case IDR bugs out) in this format:
OriginalID:ClassPath = NewID
Will I be able to move this data to your version?
P.S. Sorry for multipost
Since they didn't change too much of the code (just enough to make it work with a newer version) it should be identical to the original IDR's format, in other words, just as you have it.
Also, you do know that there is an 'edit' button on your posts, right? This allows you to not double post.
gubaguy: try removing all mods but forestry and id resolver, removing all configs, and then running minecraft. It should work, and ID resolver should reserve IDs for forestry. After that add all other mods.
Let me reexplain this since you obviously didnt read previous posts, ID resolver works FINE without forestry.
Forestry works FINE, without ID resolver.
All the other mods work FINE PERIOD, but once the IDs get resolved, ID resolver and forestry crash minecraft.
Remove all configs and all mods but IDR and Forestry.
And, in a slightly more polite way: Gubagy, have you tried Forestry and IDR together alone (without any other mods except those that are necessary to run Forestry and IDR) and in a clean, fresh install? (i.e. remove ALL data, download Minecraft, install mods necessary for IDR and Forestry)
If yes: then you've done what AUTOMATIC_MAIDEN is suggesting (and can clarify that point), if no: then try that and tell him/her that it didn't work.
And, in a slightly more polite way: Gubagy, have you tried Forestry and IDR together alone (without any other mods except those that are necessary to run Forestry and IDR) and in a clean, fresh install? (i.e. remove ALL data, download Minecraft, install mods necessary for IDR and Forestry)
If yes: then you've done what AUTOMATIC_MAIDEN is suggesting (and can clarify that point), if no: then try that and tell him/her that it didn't work.
It's good that you're trying to remain calm and polite Master_Aricitic, however I believe that Guba has already tried this before. Read here:
Still crashes for no reason, if i remove ID resolver and all other mods it runs jsut fine with jsut forestry, but the SECOND i put ID resolver in with it, crash.
Now I realize that in here he has not outright said he's tried just Forestry and IDR, however it seems rather implied in his wording. Above he does confirm that he's tried just Forestry, without problems. His next comment of adding IDR again seems to imply that he only added IDR to the Forestry mix, and boom.
Me? I can't figure out what's going wrong either. Hopefully you can figure this out for the poor guy.
It's good that you're trying to remain calm and polite Master_Aricitic, however I believe that Guba has already tried this before. Read here:
Now I realize that in here he has not outright said he's tried just Forestry and IDR, however it seems rather implied in his wording. Above he does confirm that he's tried just Forestry, without problems. His next comment of adding IDR again seems to imply that he only added IDR to the Forestry mix, and boom.
Me? I can't figure out what's going wrong either. Hopefully you can figure this out for the poor guy.
That is entirely possible. Honestly I cannot imagine how IDR is causing a 'rendering exception'... unless Forestry is expecting exact IDs (or if somehow IDR updated modifies some class that affects Forestry's rendering...) The former is vastly more likely than the latter (as it would have happened before if the latter were true), but I find it hard to believe that the developer of Forestry was stupid enough to explicitly hard-code the IDs...
Really, we will have to have a response from Forestry with regard to this to have any further idea...
Hello, I have written my own version of ID resolver for 1.6.2.
It resolves ID conflicts for blocks, items, and enchantments; automatically without need to click that "assign all ids in reverse" button. You just put it into mods directory and it makes things work.
It's a simple mod with only three classes; no gui, no special config, just one file with a list of registered IDs.
I'm not sure if it's ready for release, but it does work with a bunch of mods I downloaded. It's also a bit faster: for my list of mods, with ID Resolver it takes 31 seconds to launch, while with my mod it's 24 seconds.
will this be updated to 1.5.2? or has somebody made there own id resolver for 1.5.2? if this is already been said i apologize i merely don't have the time to read through 190 pages of information
Ok, ran it AGAIN, this time telling to to raise the priotiry of forestry to 1, then when forestry cam eup i tol dit to set it to default and change everythings elses ID's, but its still happening...
Thank you so much it works great i realy needed this mod im running a custom modpack i made with 30+ mods and i finally started getting id conflicts, i tried changing them myself but it was a lost cause there lol. Thank you for this awesome mod.
Well. I'm not sure how IDR is conflicting with Forestry's render method... The only thing I can suggest now is to report it in Forestry's thread. If you chose to do so mention that you are using a third party updated version (and give a link either to the post from which you downloaded it or the download: right clicking the number in the upper right corner and selecting copy link location, then pasting will allow you to make a link to that post directly).
I am sorry I was unable to help you.
I would like to know if it works with 1.5.2 as well.
I would like the answer to this as well please.
Since they didn't change too much of the code (just enough to make it work with a newer version) it should be identical to the original IDR's format, in other words, just as you have it.
Also, you do know that there is an 'edit' button on your posts, right? This allows you to not double post.
Let me reexplain this since you obviously didnt read previous posts, ID resolver works FINE without forestry.
Forestry works FINE, without ID resolver.
All the other mods work FINE PERIOD, but once the IDs get resolved, ID resolver and forestry crash minecraft.
Remove all configs and all mods but IDR and Forestry.
And, in a slightly more polite way: Gubagy, have you tried Forestry and IDR together alone (without any other mods except those that are necessary to run Forestry and IDR) and in a clean, fresh install? (i.e. remove ALL data, download Minecraft, install mods necessary for IDR and Forestry)
If yes: then you've done what AUTOMATIC_MAIDEN is suggesting (and can clarify that point), if no: then try that and tell him/her that it didn't work.
It's good that you're trying to remain calm and polite Master_Aricitic, however I believe that Guba has already tried this before. Read here:
Now I realize that in here he has not outright said he's tried just Forestry and IDR, however it seems rather implied in his wording. Above he does confirm that he's tried just Forestry, without problems. His next comment of adding IDR again seems to imply that he only added IDR to the Forestry mix, and boom.
Me? I can't figure out what's going wrong either. Hopefully you can figure this out for the poor guy.
That is entirely possible. Honestly I cannot imagine how IDR is causing a 'rendering exception'... unless Forestry is expecting exact IDs (or if somehow IDR updated modifies some class that affects Forestry's rendering...) The former is vastly more likely than the latter (as it would have happened before if the latter were true), but I find it hard to believe that the developer of Forestry was stupid enough to explicitly hard-code the IDs...
Really, we will have to have a response from Forestry with regard to this to have any further idea...
Is the version he is reporting 1.5.2? Forgive my stupidity (and poor memory).
Frankly, I would test this myself, but I'm not playing Minecraft right now...