jastey

See, that's the point. Roxanne doesn't badmouth other modders. It was the person behind that username who did so, using multiple other accounts to make it look like: q.e.d.

@Baptor Thanks! Did you confirm this for a newly started game?

I agree, my statement was too strict. Of course we edit for text format, if it is necessary for readibility.

I guess it is a copy&paste from an online translator. We will not edit posts of user/guests because of text format, but I agree that it is a little off-putting. No offence meant.

You are on BG:SoD from Steam. You need to run the DLC Merger as your very first mod to be able to install other mods (properly).

@Kentoto sorry if my post sounded annoyed. The game versions 1.3 -> 2.x had a lot of changes. Mods that were updated are most likely no longer compatible with 1.3. With risk I meant this - even if a mod installs fine on 1.3, there is a high risk there will be incompatibilities ingame if the mod is working for 2.x.

@Salk that's fairly easy if you know the structure. You need the topic number which would be "24727". Then the new link is of the following: https://www.gibberlings3.net/forums/topic/24727-a where the "-a" at the end is just a placeholder because the forum expects some text there, this will be substituted with the correct text once you open the link.

@Kentoto You play older versions of the game with mods on your own risk. You can't expect modders to keep the mods compatible with outdated versions of the game(s).

Please post the content of the file here in a spoiler. The link is supposed to go to this forum (it changed when we did software update and needs to be updated). You are in the right place!

The more detailed we get bug reports, the better we can provide fixes.

Sorry I didn't see this. As Grammarsalad pointed out, the "COPY_EXISTING" followed by the patch function means that the area in the game is taken and patched. The next mod takes the then current area version (with the changes from the first mod) and patches the new changes, and so forth. So, every mod patches its own travel regions to the same area and it's all compatible. Also as Grammarsalad pointed out, the only thing that could happen is that, say, two mods add a travel region at the exact same spot. Then it might be that only one will be accessible in game. But that's easily fixed by one mod chaning the location of its travel region.

Not wrong per se, but the patch (every patch) comes with changes which can lead to incompatibilities with exiting mods until they are updated. I'm reluctant to say this but if you want a more-or-less bugfree experience of mods you'd need to revert to 2.5 until the mods are updated. Alternatively, install and play the 2.6 with your most favorite mods and give feedback and bug reports to speed up the mod updating process.

@argent77 wow, thank you!

Does anyone know whether content changes were made to SoD? I mean like fixing content bugs, corrections to dialogues, this kind of thing - SoD only fixes. EDIT: I'm asking to know about changes with regard to my mods, not because I think SoD is especially buggy, and because the official patch announcement does not contain info on SoD afaik.

Changes to the worldmap do not show for old saves. You need to start a new game.

Awesomeness!

About 99%. There is no 100% guaranty it will work (this is the IE engine we are talking about!). But I would expect name quirks to be the most likely problem, if at all.

@Lauriel ah ok. I had a glance at it and had the impression it's not exactly the same problem, but I didn't read it carefully.

@grodrigues to tagg someone, start with an @ and chose the person't name from the dropdown list that should appear after typing the name. Otherwise, the user will not get a notification. Just FYI.

I would have said that Transitions and EndlessBG1 predated the problem, but it's the same in the end I guess. To repeat myself: EndlessBG1 uses all the original transition cutscenes etcpp, so unless there is a highly unlikely (because unrealistic) "has to happen right after Sarevok's death" kind of counter to it, I wouldn't know how something like this could be caused by the mod.

Actually, it doesn't - it only delays the time when the original transition from BG1 to SoD is called. But once it happens, the transition is the original one, with no changes (and even less meddling than Transitions does ) I woudn't know how any of the tweaks would affect this. None deal with item/magic usability nor touch the SoD transition.

Inside the EET mod folder.

@morpheus562 Thank you!

@morpheus562 would it be much asked if you'd elaborate on the problem? I would very much like that we collect knowledge about changes in the 2.6 instead of every modder finding them out separately..

We'd need more specific bug report to be able to help.