BioWare hasn't said mods from ME2 aren't compatible with ME3, because there are no proper mods for ME2 to begin with. They've only said completely boilerplate ass-covering things like "we can't promise that our game will work as intended if you don't use it as intended." Which is fair and true, but also relatively meaningless.
If you use TexMod to change the appearance of your game, that doesn't impact... well, anything. It's completely irrelevant to importing, because the game doesn't even know you're doing it. That all happens on a totally different level of your computer's process. TexMods for ME2 aren't guaranteed to work in ME3, because the names and locations of the textures being altered *may* change (some did between ME1/ME2, some didn't), but if so, it will be the work of five minutes for we modders to update and release ME3 versions when necessary.
If you do something more complex, like .ini editing, the game does know you're doing that, but none of it is stored in your savegame, so it's vanishingly unlikely to affect your import. Your savegame doesn't know if your Avenger does ten damage per shot or ten thousand, or how fast your Hammerhead's shields regen. It doesn't even actually know whether you can use the Widow or not; it only knows that you have the "Can use Widow" plot flag. If you mod your game to give the Claymore instead, the save game doesn't know that and your ME3 import will still think you can use the Widow. It's true that changes to ini files won't carry over into ME3 - you'll be getting the Widow instead of the Claymore in the above scenario - but they won't hurt ME3 either, so "not compatible" here doesn't mean "your save is now useless and unimportable" or anything nearly as horrible and doom-y as the phrasing implies.
The most error-prone area is modifications to the savegames themselves, but still, there's a high margin of likely success here. If you've done something cosmetic, like alter your head mesh to use Sheploo's face texture on a custom face, that
should carry over just fine, since they'll probably use the same directory structure in ME3, and your imported face will just go ahead and use ME3's new Sheploo texture. I don't imagine they'd change the location of the texture since changing the other texture locations would break all custom faces, but if they do, it'd be easy enough to just edit your ME2 headmorph back to normal. Same is true for custom hair meshes, Illusive Man eyes, etc etc; all those resources will still exist in ME3 so there's no reason to think your custom headmorph won't be able to use them. Changing skin colors or eye colors will cause no problems whatsoever. Worst case scenario your Shep will show up bald and you'll have to go back and change your ME2 save's hairstyle real quick. But I'd bet actual real meatspace money that headmorph modifications made with Gibbed will import perfectly in 99.9% of cases.
If you modify your savegame in non-cosmetic ways, things get a little more complicated. Changing your weapon loadout shouldn't import and shouldn't hurt anything. Giving yourself a s/s romance should import and might occasionally cause strange cutscene behavior or unvoiced dialog but shouldn't actually break your game, and the expected behavior would be for it to play out exactly like an o/s Shepard's romance. Recruiting Legion early by screwing around with the Horizon flags might cause data corruption or might make no difference at all, though again, I'd put money on "no difference at all."
BioWare won't say that, though, because if they publicly said "mods will probably work fine" that would be taking on responsibility for something they have no control over, which would be phenomenally stupid of them. Even companies that still encourage modding, like Bethesda, still make a point of saying they can't provide support for mods or promise they'll function across expansions. Doesn't mean Oblivion mods and modded savegames didn't work just fine in Shivering Isles, and doesn't mean you've ruined your import for ME3.
Modifié par Quething, 04 janvier 2012 - 12:33 .