What changed?
Allbrother
Member Posts: 261
So I just decided to come back to BG:EE after a while and now all my kit mods have their names and descriptions screwed up when they were fine the last time I played, which was immediately after the release of SoD and the modmerge (which I have on my game). I've looked through the tp2s to try and work out what would cause the SAY things to get screwed up, but no dice. For the ones that change strings I checked and they still point to the right place, so I have no idea. Can anyone help? What did Beamdog change between the release of modmerge and now that would explain this nonsense and how to fix it?
edit:
For the record, I also tried BG2:EE and it's screwed up there too, though less so
edit:
For the record, I also tried BG2:EE and it's screwed up there too, though less so
0
Comments
EDIT: Instead of modmerge you can also use Argent's DLC Merger which operates like a mod (i.e. can be uninstalled, too).
And DLC merger uses the same detection as modmerge, I think, so if the one doesn't run the other doesn't either, I guess.
What I meant was that the effect of the modmerge is no longer present for a patched game, but appearently somthing modmerge uses for detection whether it ran or not is giving a false-positive. This can be fixed but I don't know how.
1.Initially, I still had the game on my PC so I just uninstalled all mods and played fine on vanilla.
2.Then I decided to do mods, installed one - names and descriptions were off.
3.Made this thread to figure out if a change in one of the recent patches forced mods to do things differently and that was why my old mods weren't working.
4.Uninstalled the game, deleted the remaining folder, downloaded and installed game again.
5.Installed dlc merger
6.Installed one of the old mods - same issue.
7.Uninstalled old mod, downloaded and installed a couple of mods from the compatible mods thread - same issue.
8.Uninstalled dlc merger as it was hanging up on first running the mods weidu's forcing me to close and run the mod setups again.
9.Applied mod merge. I recall it saying "key not detected, extracting" or something along those lines.
10.After running mod merge tried the mods again - still the issue
11.Uninstalled all mods again, tried running mod merge again - displays some kind of error and closes immediately (too fast to read the error, can't see a log).
12.Verified/repaired the game, tried modmerge again - same thing.
13.Verified/repaired again, tried installing dlc-merge, it's aborting installation.
14.Got annoyed at dealing with modmerge and dlc-merge and moved to test on BG2EE (old installation)
15.Installed old mod - same issue. Uninstalled old mod.
16.Installed new mod - it looked find but other classes/kits now had their names/descriptions wrong. What?
17.Uninstalled new mod, opened the game to see the same thing with no mods installed. Grew suspicious of old mod (always started with installing that one) breaking the game even after being uninstalled
18.Verified/repaired the game, didn't get fixed.
19.Uninstalled, re-installed. Loaded up the game - all looks good.
20.Installed new mod, loaded up the game - all looks good. Suspicions intensify
21.Uninstalled new mod, installed different old mod (not the suspected culprit) - works like a charm
22.Uninstalled old mod, installed suspected culprit, fired up game expecting to say AHA! - works like a charm... what?
23.Installed other old mod and new mod and ran game with all 3 mods together - works like a charm. Uninstalled all 3 mods - still works fine.
24.Uninstalled BGEE again (this time removing user data as I had done for BG2EE, but not the previous time for BGEE)
25.Re-installed BGEE again, tried modmerge - got error and closed again.
26.Tried DLC Merger again, aborted again... WTF?!
27.Uninstalled (deleting user data) and re-installed AGAIN, tried DLC merger AGAIN, gets aborted AGAIN
28.Posted this.
29.Set my PC on fire
30.Burned down my house and jumped out the window
31.Now a ghost, this is still infuriating
32.Help
edit:
So I managed to snatch a screenshot of the error on modmerge before it closes. It says something to the effect of sod key found, you've already done this, stop farting around. Also, I noticed that dlc-merger says it's aborting because DLC is already merged when using option 1 and because no dlc archives found when using option 3.
So both tools think they're installed, despite this being a clean game install with the DLC being locked into the zip
I tried disabling sod (by renaming the zip) which worked and the mods work fine with the BGEE base game. Enabling the zip breaks them again and both modmerge and dlc-merge now think they're installed (despite this being a clean game install) so they won't do anything
When you run modmerge.exe it should work.
You seem to have done quite a bit of messing around with files. Maybe something went wrong in the process. Beamdog didn't change anything between the release of modmerge and now.
Modmerge rejecting to run is your problem, and I fear it does so because there is a marker file left somewhere due to the folder mixup.
Thanks to everyone who responded
Not modmerge, but I have a faint recall that there were some problems with running it again after the patch was applied which should have lead to a clean install but somehow modmerge recalled being run in this game folder before.
Argent gave some ideas how to fix this here in the modmerge thread which I could have seen earlier.
@Allbrother Yay!