I think other programs are using "LOCALAPPDATA" environment variable too. so not goo idea to chnage it. what you can do is replace screeps folder with symbolic link. I did that for few programs since I installed SSD into my PC setup.

Symlink on windows can be created by opening cmd and execution command:

mklink /j "c:\mklink" "d:\mkfolder"

Sure replace path location with yours.

If it happends on private server maybe this is same issue? https://screeps.com/forum/topic/2829/room-energycapacityavailable-returns-null-due-to-corrupted-spawn-store/2

After staring for some time I saw the lines that should distinguish constructued walls are there, but the if color is same lightness as wall decaroration they almost disappear. I think good solution will be use wall decorations border color for that lines. Or adjust the lightness of lines correcponding to walls decoration color

@Davaned I think the major thing is credits are not part ofe game world, there is no such resources type. If they would you will need to store them and then credits can be stealed by other players. When they are on the account they are much safer

@artch Also this will affect network parts if it lies through remote harvesting rooms. Maybe in some situations there will no alternative paths other then through remote mining rooms. Maybe make it so if warp container is near the source this effect applies. Gradually like at distance <= 5 max decay to distance 20-15 low or zero effect. Or strict if distance <= 20-15 100% decay effect.

I have a guess. If MMO uses multiple clusters or containers that runs players code, maybe sometimes ballancer picks wrong instance for particular player and alternates that between different ticks. Maybe hash collisions

I have two instances of global right now. As I use generators a lot in my latest codebase it had a bad consequences. Creeps were moving back and forth because different global instances had different targets for them. I made a fix for now, it detects if current globalId is different from lastGlobalId and restarts the threads. But I can imagine how other players code that relies on global or generators can suffer.

Maybe you can add global detection on server side. Simply adding id to global (maybe name that property _id) and storing lastGlobalId per player in some storage will allow you to monitor how often it happends and restart runner containers for that players.

Here is the method I used to detect multiple globals:

let globalIndex = Memory.globalIndex = (Memory.globalIndex || 0) + 1;
Memory.lastGlobalIndex = globalIndex;

function checkGlobal() {
	if (globalIndex !== Memory.lastGlobalIndex) {
		console.log('2 globals!', 'globalIndex:', globalIndex, 'lastGlobalIndex:', Memory.lastGlobalIndex);
		Memory.lastGlobalIndex = globalIndex;
		fixGlobals(); // some logic to fix
	} else {
		console.log('globalIndex:', globalIndex);
	}
};

module.exports.loop = function() {
	checkGlobal();
	// ... other code
};

You can use similar method but instead of memory save this 2 variables (globalIndex and lastGlobalIndex) in some database per each player (maybe per shard also).

@tun9an0 I also thought about creep convoys with energy to help sieged colony. But depedning on the terrain your path will go through attacking squad or not. In first case it is very hard to keep haulers alive, sure there can be healers and attacking creeps or towers can heal them... But what if attacker just have more creeps and will intercept haulers easily

What if make a power to use on nukes so they will limit terminal throuput for some time. But maybe it is not good to mix this 2 things... Or imlement other two power creep classes so attacking with them will be more effective even vs good repairing. Don't forget that disrupt terminal can be done only in room where power enabled.

@cookies I see some problems with solution that you suggested. The main is warp containers are neutral thus anyone can connect to your network and steal resources. Maybe if warp containers were owned it could fix that. 1 per room, owned and you gotta defent it.

The second is cooldown should be triggered by sending to another warp container and not by creep withdrawing from it. Also can't imagine how capacities can add up. If container "merges" (shares) with near room warp containers, that containers can't be shared simultaneously for their neignbour rooms.