It is the case though!

https://docs.screeps.com/api/#StructureRoad

Note: every creep step decreases the decay timer for 1 tick per each creep body part

I've not seen any since the 9th Oct.

@wtfrank that is the absolute worst case. In the majority of cases the room will either be closer than 600 ticks or the controller will downgrade a bit before the attack to recontrol it comes.

I like option 3. It appears to fix the issue without changing anything else significantly.

@artch said in Expose respawn/novice property on Game.map and/or Room:

@tigga Terrain data is statically cached in all nodes and is fetched only once on launch. Novice/Respawn status is stored in MongoDB where all rooms info is located, this kind of query is way more expensive.

Right, but as a user I'd just do the following:

if (!global._roomInRespawnNoviceArea || resetRespawnNoviceCache) {
    global._roomInRespawnNoviceArea = {}
    for (all ~4000 rooms) global._roomInRespawnNoviceArea[roomName] = isRespawnNoviceArea(roomName)
}

Where resetRespawnNoviceCache is set on the tick any walls go down or up. There's probably a good reason you can't do this - I'm not at all familiar with the backend and you obviously are! My point is that this array shouldn't come to more than 4kb per user, and populating it once per reset seems fairly cheap.

EDIT: I've used an object for simplicity. Pushing this into UInt8Array would be 4kb, packing it into a bitmask could get it down to 500b.

@artch said in Expose respawn/novice property on Game.map and/or Room:

Adding this to Game.map isn't possible without adding a lot of burden to the DB. The only viable option is to add it to the Room prototype, but you'll need to have visibility.

This would be better than what we currently have.

Regarding db burden - couldn't it be done with one bit per room? Obviously that's not going to give us time until expiration, but given terrain data is significantly larger it seems strange that it can't be done efficiently. I guess terrain data doesn't change... but respawn areas don't change much! I'm coming from a place of not having looked at the code at all so this may be an oversimplification...

A syntax error doesn't work, nor did the circular require.

Still have no way to do this from code AFAIK.

No, the code runs, it just causes my script to timeout rather than blowing out the heap and triggering a reset.

@mototroller said in Force a global reset:

const heap_bomb = () => { new Uint32Array(810241024); heap_bomb(); };

This works in console, but doesn't seem to work in code.

I'm going to test black's solution. Seems like it should work more reliably.