I believe we can reach a compromise on this. Allow game objects to be serialized still, maybe mark a few properties as non-enumerable to prevent the circular errors. But not all of them, we still want to be able to inspect an object on the console. Then for Memory serialize use the 2nd parameter of JSON.stringify, the replacer, to exclude game objects or throw an error that they have a game object in memory.

The default object serializer that use to return something like [Object object] is now printing undefined, which is very confusing.

I wonder how practical it would be to log all RoomObject creation / destruction?

I have no idea why anyone thinks discord would be a better choice than slack.

Voice chat isn't that great at these game speeds, and given this is a coding game I don't understand why we'd move to a platform with less snippet support.

So you got attacked in a PvP game about coding and automation and you're upset? You still have your code, market credits, and GCL. You learn, improve your defense, and respawn to try again. If you automate room construction and claiming suddenly getting removed becomes far less of a setback.

Sounds like a sector close. In an effort to bring shard0's tick times back under control they're closing rooms periodically, starting with the edges of the world.

@artch Currently a bug in the implementation.

ReferenceError: roomObjects is not defined
    at spawnCreep (C:\Program Files (x86)\Steam\steamapps\common\Screeps\server\node_modules\@screeps\engine\dist\game\structures.js:1253:70)
    at . (evalmachine.:1:72)

when passing in energyStructures

I popped over to the steam downloading page and it said "content file locked". I had just closed notepad++ which locks all it's open files and click the little icon on the right hand of the download to try again and it finished updating. Wonder if any of that's relevant to your situation.

From driver/lib/runtime.js#274 you'll see the getUsedCpu function:

var getUsedCpu = function () {
            var elapsed = process.hrtime(startTime);
            elapsed = elapsed[0] * 1e3 + elapsed[1] / 1e6 + intents.cpu;
            return elapsed;
        };

but then at line 375 you'll see this:

outMessage.usedTime = process.hrtime(startTime);
outMessage.usedTime = Math.ceil(outMessage.usedTime[0] * 1e3 + outMessage.usedTime[1] / 1e6 + intents.cpu);

outMessage.usedDirtyTime = process.hrtime(startDirtyTime);
outMessage.usedDirtyTime = Math.ceil(outMessage.usedDirtyTime[0] * 1e3 + outMessage.usedDirtyTime[1] / 1e6);

Time is rounded up. That should account for some of the error, at least.

Steam has the option of opting into betas, any chance we could deliver new PTR features in the private server this way? Might help with testing.