Option 3 looks good.

This may help some folks. Seems to be a common question on Slack asking how to figure out actual usage.

if (typeof Game.cpu.getHeapStatistics === "function") {
	let heapStats = Game.cpu.getHeapStatistics();
	let heapPercent = Math.round(((heapStats.total_heap_size + heapStats.externally_allocated_size) / heapStats.heap_size_limit) * 100);
	console.log("heap usage:",Math.round((heapStats.total_heap_size)/1048576),"MB +",Math.round((heapStats.externally_allocated_size)/1048576),"MB of",Math.round(heapStats.heap_size_limit/1048576),"MB (",heapPercent,"% )");
}

How about EVENT_DESTROY? There is currently no easy way to see when a structure is destroyed except for storing all structures in Memory and comparing on a regular basis. It would be triggered on the use of destroy() or when the structure hitpoints reach zero. I think that would be very useful.

It would be helpful if there were portals on shard2 in the intersections that would allow travel across the areas with closed sectors. Right now if traveling from shard1 a person is stuck picking from only 4 rooms. A creep spawned on shard2 with a CLAIM part can't travel to the next group of 4 rooms and claim one.

Alternatively opening more rooms around the portals from shard1 would also solve the problem.

Newly built extensions don't display energy level (yellow fill). Clicking on the extension shows the proper energy level in the right status panel.

Issue persists until the room is reloaded by going to another room or similar.

Playing on Shard1 but I am guessing this impacts all shards.