@o4kapuk
I have managed to find the problem. It was a mistake on my end, as I suspected and your suggestion to try with empty Main module helped to quickly identify the problem spot. Funny thing is that, just one keyword change did it.
The reason was that I my Main module I had this for loop and condition:
for (const name in Game.rooms) {
const room = Game.rooms[name];
if (!settings[name]) return;
// .... rest of the room specific code
}
I wasn't aware that when my creep enters a new room, it is listed in Game.rooms object even though it is not my room. In settings[name] I am keeping room settings. When the creep gets into a room that is not in my list, then settings[name] is undefined and return makes an early exit from the Main module and skips all other code execution. That was the reason for another side effect where my other creeps stopped all actions while the scout creep is in the other room.
I somehow made myself think that this return only returns from the for loop (god knows why! maybe I was thinking about forEach callback) and not from the entire module. So, a quick change from return to continue did the trick:
for (const name in Game.rooms) {
const room = Game.rooms[name];
if (!settings[name]) continue;
// .... rest of the room specific code
}
After that I tested all of the approaches for getting into the target room, and they all worked, where the one that used the pathThroughRooms array only needed to include the target room name in the array as well.
So, I'd say that this is solved and I hope that the details I provided will help someone else in the future if they encounter a similar issue.
Thanks for pointing me in the right direction!!
