Containers can't be opened...

[Kasmir]

...but no idea which mod is causing this problem. 

 

Update: Reloaded mods and this is no longer happening.

Edited May 24, 2023 by Kasmir

[HockeyPhool]

Seeing the same issue with v12.4.0_01. I suspect Banner Switcher mod, but haven't been able to disable it yet to prove it.

[Aslain]

Next time please include logs, without them I cannot help much.

[Venger]

Same issue here, here's the logs I have... Aslains_WoWs_Logs.zip

 

[nagymacs]

Same issue here. I uninstalled and the reinstalled and the problem is gone

I guess some leftover from the earlier version causes it and the uninstall takes it away

[Aslain]

I confirmed problem with Auto container collector mod, which is 100% reproducable for me, some people says it's also caused by the Banner mod, but I couldn't confirm that. Tell me precisely what steps you have done that led you to this issue, detailed steps.

[Venger]

I had the bug and I do not use the Auto Container Collector Mod... I removed the Banner/Container in Port mod, and it works again, so that looks like the culprit.

Edited May 26, 2023 by Venger

[Aslain]

Saddly I cannot reproduce it. If you give me repeatable procedure I will try again.

[Venger]

Might require going into battles, maybe using the new Battle On button after a game rather than returning to port first, not sure... 

[Venger]

FYI, the Battle On! button might also be screwing with the Aslain Version Checker as well, it's popping up going back to port from battle now, it should only pop up I think on first entry into the game....

[Aslain]

7 hours ago, Venger said:

FYI, the Battle On! button might also be screwing with the Aslain Version Checker as well, it's popping up going back to port from battle now, it should only pop up I think on first entry into the game....

Could you show it on screenshot? Do you receive any pop up about new version in port now after loggin in?

[nagymacs]

Sadly it is back. Here is my log. What happens is, that it collects the first container, or opens one container, then it does nothing more. you cant collect containers, you cant open containers. Buttons are not grey they just do not react. You can see what containers you have. And I agree it must be a combination of something. Today I played convoy, and container collection, opening worked multiple times. Then went to play brawl, and it does not work anymore. I restarted the game client, bug is still there, I could collect only one container and it works no more. I uninstalled and reinstalled the mod. It is working again. I try to find when it stops working, I have some more containers to test

Aslains_WoWs_Logs.zip

[nagymacs]

I went into battle, on the end went back to port. Still works.

[h3ll0]

I don't know about this one. I can though tell that Auto container collector is expecting a little update for this game update. Thx 👍

[Aslain]

Finaly reproduced that issue with the Banner etc. mod, to trigger it, I had to click on one of that container types:

[nagymacs]

21 hours ago, Aslain said:

Finaly reproduced that issue with the Banner etc. mod, to trigger it, I had to click on one of that container types:

That very well may be. I had no idea what is going on, the error came and go, came and go.

[Aslain]

Well that mod is gone, so nothing to talk about now 😉

[nagymacs]

7 hours ago, Aslain said:

Well that mod is gone, so nothing to talk about now 😉

Actually the mod is gone, but the error is still there, just saying.

[Aslain]

I can check it but only if someone can provide logs and reproduction steps.

[nagymacs]

2 hours ago, Aslain said:

I can check it but only if someone can provide logs and reproduction steps.

I think that it is caused by the operation "collect container". And I'm not sure it is mod related.

[kron]

it wasnt a MOd Pack issue, had that happen to me too, just had to restart the game. I didn't have autolopen container mod installed.