@systemparadox The 'over time' slowdown appears related to the GUI actually, as hitting the icon in the upper-right and just hitting 'OK' to restart the GUI thread speeds things right back up again as a workaround at least. But yeah there's some kind of bug causing it to slow down over time. Happens with both the Legacy/SVG and the newer WebGL GUI.

Also instead of worrying about >5 ticks/second just manually upgrade the RCL and place a mixture of completed extensions and construction points. Once you know the basic code loop works, skip over the 'grindy' bits in the Simulation mode.

@artch Since moving onto an enemy ConstructionSite removes it, would it be possible to return an ERR_ code from Room.createConstructionSite if you attempt to make a ConstructionSite on top of an enemy creep instead of allowing it to occur?

@rurik Correct, if they're paying subscribers they don't get de-activated, but the devs have said already they disable free users that aren't active for 30 days so I'd think enabling an instant-despawn as well for those player slots if they "go zombie" would be reasonable.

They already spin down CPU to 0 if you're not active for long enough, I'd be all for despawning for 'deactivated' players, that's the extent I'd be okay with personally.

Yeah, only one Creep.attackController every 1000 ticks, but that's 300 * the number of CLAIM parts on the attacking creep, so you could feasibly (for ~6600 energy per creep) blow away 3000 ticks every 1000 to quadruple the decay rate with whatever creep you're sending out to Creep.reserveController on it's way to wherever it's heading, and hit multiple sites if needed with one creep feasibly.

Some (most?) of the public bot codebases are using TypeScript already, and there's a lot of folks using WASM transpiled stuff.

JavaScript as a target is becoming more and more common due to it's use on browsers, so I just don't think this is an issue really versus the entrenched playerbase that a titanic shift in language support would throw out the window whole-cloth.

Well the docs are at https://github.com/screeps/docs, the back-end engine is at https://github.com/screeps/engine, and there's actually very little at the main https://github.com/screeps/screeps repo. Just issue a PR against the appropriate repo after making the edits.

Good spot, wrote up a quick Pull Request to fix the docs, pending the Screeps devs accepting it, as the behavior is common across other components and mentioned in the docs, looks like it was an oversight.

https://github.com/screeps/docs/pull/88 for anyone wanting to track this further.

Biggest problem with the Slack is that it's designed for handling teams of folks that all will get along amicably, there's no tools available to filter or deal with individuals that cause issues except leaving whatever channel they're in, unless a moderator steps in and kicks them off the Slack entirely.

There's literally no other moderation tools on Slack at all, and zero as an individual user.

Screeps might get large enough that model won't work long term, as unlike an official Discord there's no way to ignore or block individuals you personally find problematic, which is why I'm not on the Slack server honestly, already ran into a few of those so I left the server.

Well the docs list how to tell them apart: There's no .hits property on indestructible game-placed walls.