It appears that there is a bug within—or at least triggered by—this mod, whereby the game becomes largely frozen if the player opens a container with a large number (perhaps ≥256) of items inside. In this situation, it is still possible to open & close UI panels, open & close the context menu, and move the party around in the game world, but most other actions produce no effect: moving container items to/from inventory, casting skills, activating context menu actions, activating game world transitions, loading a save, and others. The only workaround appears to be to kill the game process and load a save created prior to opening the container.

Disabling this mod prevents the issue.from arising.

This issue has been previously reported in Larian's forum[forums.larian.com], with the same preconditions, the same symptoms, and the same workaround. However, that report did not appear to be raised to this mod's author/maintainer, so I'm reporting it here in the hope of closing the loop and getting the issue resolved.

In my particular situation, this occurred in Act 2 with the Lady Vengeance Storage Chest—particularly, the version of the chest that is implemented by LaughingLeader's mod, “Lady Vengeance Storage Chest Fixer”.

https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=1966757974

Due to the nature of the bug's apparent preconditions, it is unlikely to arise with any other container, but it is very likely to arise with this particular container (provided that the player chooses to make heavy use of it). I have not attempted to reproduce the bug with any other container. Consequently, I have not narrowed down the etiology of the bug; it may arise from within this mod, or from within LaughingLeader's mod, or from within the vanilla game. However, some behavior by Auto Identify is certainly implicated, since disabling it resolves the issue reliably. Note that, in the aforementioned forum post, the reporter was not using LaughingLeader's mod, so at least in that case, the bug appears to arise simply from Auto Identify (and the vanilla game code). However, I cannot say with certainty that his mod isn't implicated at all in my case, since I don't know whether the code path is different with his mod versus without his mod.

It is worth noting that LaughingLeader appears to have encountered a similar bug within his aforementioned mod (in the absence of Auto Identify), and he succeeded in patching his mod to fix it. That patch was (as of now) the last update to his mod; the diff is available on GitHub[github.com], in case you'd like to cross-reference it. In case you face difficulty in tracking down this bug, you may wish to reach out to LaughingLeader—not only for his general expertise in modding this game, but also because his mod's code might be incidentally involved, and especially because (according to this mod's credits) he contributed to this mod as well.

https://steamhost.cn/steamcommunity_com/id/LaughingLeader