[Lava]

Those were mostly minor fixes, I am not planning to make any major changes

[Ammanda]

I see mod get two upgrades since than (9.0 I installed). I wont bother you with changes, I always assume it is improvements, bug fixes (although I did not noticed any), maybe some new contant, components and features.

All I definite need to know is what we did talked about, is anything going to change about your safe Hideout. I found it really great for lot reasons, including lot easier managment of items to place in containers, simply as access is way easier due to teleportation.

But as you did mention possibility to maybe remove it (I did understand you will not, that you just hope players wont abuse it), thats what I would ask, if you did changes about Hideout in updated, please let me know.

[Lava]

What I wrote:

I cannot do much more and prevent it in a different way that deleting that part of the mod and I don't want to do that.

When I said I don't want to do that means that I don't think I will ever delete it because it can be used in a wrong way. It is not going to be disabled, I never said it's something I'm planning to do.

I see mod get two upgrades since than (9.0 I installed). I wont bother you with changes, I always assume it is improvements, bug fixes (although I did not noticed any), maybe some new contant, components and features.

The changes are in the readme, there were some minor updates/fixes, nothing big.

Code:

Version 9.1 - September 2025:
- Wisps should no longer leave corpses
- Fixed a couple of items, including sod
- Updated Chinese translation

Version 9.2 - October 2025:
- Russian translation update by Neoko5

And there won't be new content for this mod. 

There would need to be some serious problem like "the game stops running because of quest so-and-so" for me to disable such quest/area, and I think if there was such problem, it would have already been reported and I would have already fixed it or disabled it.

[AnOpenHeresy]

Do I need to take care of moving the Glowing Wardstone to Bg2(EET) or is it placed somewhere in the dungeon?

[Lava]

There is no any special script to handle that, SotSC was primarily written for BG1EE and SoD, and there are no special adjustments for EET. Furthermore, be careful when using it in BG2, especially in ToB. Never use the stone while being in other forms of Pocket Planes.

[AnOpenHeresy]

Do I need to take care of moving the Glowing Wardstone to Bg2(EET) or is it placed somewhere in the dungeon?

Okay, thanks. Overall, your mods add a lot of content that I think is sorely lacking in the Baldur's Gate series as a whole. Pozdro!

[Lava]

Thanks! Have fun

[Isewein]

Unfortunately, it appears that SotSC is incompatible with BG Classic [Stone] UI: https://forums.beamdog.com/discussion/83...ui-v1-6/p1

When I attempt to install SotSC, WeiDU reports:

Code:

FAILURE:
ADD_MAP_ICONS: map icon file (MAPICONS.bam) is not a BAM V1 file
ERROR: [MAPICONS.bam] -> [override/MAPICONS.bam] Patching Failed (COPY) (Failure("ADD_MAP_ICONS: map icon file (MAPICONS.bam) is not a BAM V1 file"))
Stopping installation because of error.
Stopping installation because of error.
Stopping installation because of error.
Stopping installation because of error.
Stopping installation because of error.
Stopping installation because of error.
Stopping installation because of error.
Stopping installation because of error.

ERROR Installing [Shades of the Sword Coast – Expansion Pack for BGEE], rolling back to previous state
Will uninstall 1584 files for [sotsc/sotsc.tp2] component 0.
Uninstalled    1584 files for [sotsc/sotsc.tp2] component 0.
ERROR: Failure("ADD_MAP_ICONS: map icon file (MAPICONS.bam) is not a BAM V1 file")

Since BG Classic UI is the only mod which has modified this MAPICONS.bam in my override so far, it must be an incompatibility with this UI. Any chance for a way to make them play nicely together? I'd love to try SotSC, but I'm so attached to the classic, cozy stone interface...

EDIT: Seems like I can just remove the mapicons.bam from Classic BG UI without much loss – all it does is recolour the icons. 

Just to confirm though, is it working as intended that the "Mountain Cemetery" area shows up on the (regular BG:EE) world map from the start? Or possibly a sign of another incompatibility?

[Lava]

Hi! Sadly, the mod you mentioned clearly changed the format how all map icons are handled. So, even though it's EE, it expects icons that were used pre-EE. Sorry, but for now I do not have plans to do it, and I am unsure if there is a way to detect if the file requires bam v1 or bam+pvrz. Detecting the mod itself would keep the problem if there was any more mods that do this. Besides, I wouldn't even know how to approach / code this properly.

You may also try using Infinity UI++, which I think have a stony version too, but it's huge and may have other problems regarding compatibilities etc. I am not up to dates so you would need to check that.

[Isewein]

I see. That's fine! I understand that unfortunately that Classic UI mod is quite finicky (no WeiDU, no longer maintained...). It seems that removing mapicons.bam from it did the trick and doesn't break anything, but I realise that there might be other issues with aspects of the GUI.

Anyway, would you just quickly confirm that this is working as intended and not precisely such an issue?

Just to confirm though, is it working as intended that the "Mountain Cemetery" area shows up on the (regular BG:EE) world map from the start? Or possibly a sign of another incompatibility?

[Lava]

I see. That's fine! I understand that unfortunately that Classic UI mod is quite finicky (no WeiDU, no longer maintained...). It seems that removing mapicons.bam from it did the trick and doesn't break anything, but I realise that there might be other issues with aspects of the GUI.

Yeah, it may be risky.

Just to confirm though, is it working as intended that the "Mountain Cemetery" area shows up on the (regular BG:EE) world map from the start? Or possibly a sign of another incompatibility?

IIRC, it should show up as grayed out. There is no quest that directly leads people there, and I wanted to motivate player to find out how to reach that mysterious place.

[Isewein]

I see. That's fine! I understand that unfortunately that Classic UI mod is quite finicky (no WeiDU, no longer maintained...). It seems that removing mapicons.bam from it did the trick and doesn't break anything, but I realise that there might be other issues with aspects of the GUI.

Yeah, it may be risky.

What can I say – my nostalgia is stronger than my good sense here. I'll give it a try.

Just to confirm though, is it working as intended that the "Mountain Cemetery" area shows up on the (regular BG:EE) world map from the start? Or possibly a sign of another incompatibility?

IIRC, it should show up as grayed out. There is no quest that directly leads people there, and I wanted to motivate player to find out how to reach that mysterious place.
[/quote]

Brilliant, thanks for confirming. So at least I know that has got nothing to do with BG Classic UI. I just noticed it looking a bit out of place in the middle of an empty map, but I think that's only because I was on the lookout for map issues. Actually it makes perfect sense that Charname would have read legends of such a mysterious place up in the mountains in Candlekeep. Come to think of it, more landmarks should be visible from the beginning when you consider that...