I think it's very hard to understand what was considered a bannable offense here, apart from multi-accounting.
I think if there's some behavior possible in the game, even exploiting bugs, it shouldn't be a bannable offense. If there is some persistent griefing it indicates the game needs to be changed in some way.
To make sure it's not you clobbering the array or something, make a branch where that's the only code. If that doesn't work, there is a bug.
I'm also constantly getting these messages now.
Storing the ID is the correct way to do it.
Yeah, so if you are for example looking at the API reference for Mineral, and you wonder what they do, you need to click at:
Simple! 
There should really be direct links to the important and heavily used non-API documentation. They're unnecessarily hard to find at the moment.
At least it should be so that if you lose two levels on the controller, it will only reset it to the one above it. E.g. if you let your controller slip to level 1, it should be restored to level 2 and not 8.
Edit: Dissi explained why that's not a good idea: GCL boosting by letting your room downgrade to level 7 and bringing it back up to 8 over and over.
It seems to affect only those who has gained a level recently. I noticed immediately after getting level 6 that the UI says 70 even if Game.cpu.limit states 80. My average CPU usage is slightly above 70 and my bucket is empty.
I can also confirm this. Actual CPU is 10 lower than it should be.
At the very least it should spill on the ground, but perhaps better to turn it into a neutral structure which can be pillaged at the attacker's leisure.
Now, both the Screeps logo and the Home button takes you to the frontpage, which is really uninteresting when you're already playing the game.
I propose that the Home button works like the World button does now, takes you to a player-defined "home" area in the world, and that the World button will take you to a world-view of the room you're currently in (like clicking the world map link in the minimap.
Ah! That makes sense. I wish it did take 0 though, since it doesn't give any benefit in the game. It's more like console.log. It's a lot more interesting to watch the creeps when they talk a little bit. The console is not well suited for that.
This seems to have been fixed partially. I noticed that when creep.say is called, it's sometimes close to 0 cost, and sometimes close to 0.2. Some basic test code show this to be inconsistent even within one tick:
let buckets = [0,0,0,0,0];
_.forEach( Game.creeps, function(creep) {
let time = Game.cpu.getUsed();
creep.say("0123456789");
time = Game.cpu.getUsed() - time;
if(time < 0.05) {
buckets[0]++;
} else if(time < 0.10) {
buckets[1]++;
} else if(time < 0.15) {
buckets[2]++;
} else if(time < 0.20) {
buckets[3]++;
} else {
buckets[4]++;
}
});
console.log(JSON.stringify(buckets));
Typical result:
[14,0,0,0,67]
It's never in between. So it's clear that usually CONST is applied, but sometimes not.
Yes, you find notification settings under Manage account: https://screeps.com/a/#!/account
I use containers in all my rooms, because links alone can't handle the amount of energy I transport to a room. With this change I'll use them even more.
Secondly, I'm afraid I have to report a bug, since I'm repairing and harvesting simultaneously. I understand now that this is not supposed to be possible.
1. Open Simulator mode in Custom mode.
2. Select player 1, write `let this_is_player1` and save.
3. Select player 2, write `let this_is_player2` and save.
So far, so good.
Now, with player 2 active, open the extra window. Player 2's code now reads `let this_is_player_1`.
(By the way, it would be much better if I could set Player 2 to run an explicit branch. Now it's a tiring copy-paste job.)
Opening the separate window can also overwrite the code for the second player in the simulation mode.
Can confirm that building roads on ramparts still returns ERR_INVALID_TARGET
Expected ERR_NOT_IN_RANGE, but got OK. Code sample:
let res = creep.repair(target);
if(res === OK) {
// good job, little creep
} else if(res === ERR_NOT_IN_RANGE) {
creep.moveTo(target);
}
Unfortunately, the little creep doesn't do a very good job in this situation.