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.