Suggestion: IDResolver built into the launcher.

[Dex Luther]

People are already starting to add their own favorite mods to what is already available in the FTB modpacks. The number of people coming to the forums with ID conflicts is inevitably going to increase. Considering one of the goals of the FTB launcher is to make it easier for people to play modded Minecraft and also give them the ability to easily add/remove mods as they like, some kind of IDResolver could/should be built into the launcher itself.

When adding a mod, the launcher could scan the IDs for conflicts and warn the user of anything found. Giving the user an option to overwrite (for mods like Gregtech).

Mods could also be specifically written/made to support an FTB Launcher with a feature like this by including a 'FTBOverwrite.txt' file inside the .zip. This text file would just list the object IDs and/or Mod Name/Object Name that it's supposed to overwrite, and the FTB Launcher would just overwrite those automatically.

 

[b0h]

The best thing in my opinion would be to have an id manager built-in inside Forge.
In any case, idresolver doesn't like much Buildcraft.

At least, most of the mods should have fixed ids from the config files, then implement IDresolver at the end, so it can manage mods added by the final user.
This is what i did in multimc. I took the id fixed from the FTB pack, and then used IDresolver to manage any other mod that i added.
It worked like a charm.

 

[Dex Luther]

The best thing in my opinion would be to have an id manager built-in inside Forge.
In any case, idresolver doesn't like much Buildcraft.

At least, most of the mods should have fixed ids from the config files, then implement IDresolver at the end, so it can manage mods added by the final user.
This is what i did in multimc. I took the id fixed from the FTB pack, and then used IDresolver to manage any other mod that i added.
It worked like a charm.

Yeah. I just added IDResolver through FTB launcher itself, and had no issues with Buildcraft at all. Not everyone knows about it though.

The launcher is supposed to make things easy for everyone. There are a lot of people that are new to Minecraft mods and some that aren't so new, and have trouble or just don't know how to deal with Conflicting IDs. Seeing how it's a potentially game breaking issue, there should be measures implemented to prevent it. The only way I can see to prevent it would me to include IDresolver in the modpack itself, or implement IDResolver type functionality to the launcher.

 

[b0h]

Yeah. I just added IDResolver through FTB launcher itself, and had no issues with Buildcraft at all. Not everyone knows about it though..

That's because Buildcraft already coexists with the other mods that usually conflict with ( Redpower mostly ) and the team already have dealt with the id issues before releases.
FTB has a lot of work done in that matter, that simplify the work of adding new mods at the existing pack.

 

[Dex Luther]

That's because Buildcraft already coexists with the other mods that usually conflict with ( Redpower mostly ) and the team already have dealt with the id issues before releases.
FTB has a lot of work done in that matter, that simplify the work of adding new mods at the existing pack.

They've done work to get a lot of most compatible together. The most popular ones at least. Adding something like this to the launcher or the modpacks by default ensures that MOST mods a user wants to add themselves will at least behave with everything else.