Yes. Outside of the fact that it has nearly killed my windows installation (something went sideways, very badly), nothing has changed. Screeps still occasionally drops into non-accelerated mode upon loading a room, and settings say "no hardware acceleration available". Despite everything else on system running fine.

Ever since the latest update my steam client would often go blank and just say "no hardware acceleration available" in the settings gear until I restart it, then everything is fine again (until next time it does that). If I exit to map and return to any room it'll be with the simple renderer.

What's up with that?

A couple of hours ago there was another global reset, and it would appear my CPU usage is more or less back to where it was two days ago. It is much smoother now, at the very least.

Can anyone shed some light on what's going on with the servers lately?

This is my CPU usage graph for shard1 for the past 48 hours:

Notice how the graph drastically changes from being nice and smooth in the first part to being all over the damn place, super jittery, and averaging significantly more than before. I have not changed anything in my code or room layouts since. It all started after yesterday's server restarts when shard2 died (again). I am seeing similar problem on shard3, and many of my friends on shard1 and shard2 are reporting similar CPU troubles as well.

This is much worse than we had before server migration...

Also, as a side note, while it is not too late, consider switching to Spawn.spawnCreep instead. Spawn.createCreep is deprecated and can be removed at any update.

All you really need to change the parameter you pass as memory into an object where you attach the new creep's memory to the appropriately named memory key.

So the creep spawning bit would look like this:

            var creepMaker = 
                      this.spawnCreep(mainParts, creepName, { memory: { role: roleName, working: false } });

That's all. Just remember, creepName is required for spawnCreep, although you seem to already be providing one already, so should not be a problem.

I'd like some stuff my creeps on MMO could show off instead Like a banner or something!

While I generally like the idea of seasonal servers, I don't truly agree with the pricing model right there. Namely, having to pay for both access and cpu sub to be competitive not only sounds like pay-to-win, but also like double dipping to me. It just feels... wrong.

Here's my ideas on how you could go about this to make it a bit more fair to everyone:

1. Drop the cpu sub effect on seasonal shards. Leave it to be MMO specific, and allow everyone on the seasonal shards pay for entry, and have a specific cpu limit (say 100 for everyone). This puts everyone on equal footing (isn't that the goal for the seasonal servers?). Adjust the access cost/seasons pass accordingly, if needed.
2. Keep the sub cpu effect, but create completely separate shards for cpu-unlimited (normal 300 cpu cap) and 20-cpu shard, each with their own, separate leaderboards. This way we'll have equal footing for the subscribers and non-subscribers, leaving them to compete against their equals. Maybe even have separate goals for each of the shards?

@xenofix said in Pathfinder cannot find path within one room:

Luckily I know A* very well. But I always thought there are two implementations in screeps. One PathFinder written in C++ by General and a JS JPS version, which is the default in moveTo. The C++ PathFinder could be activated as default for moveTo by PathFinder.use(true), which is deprecated now. Did something change here? Is JPS still the default path finder or is it all PathFinder only now?

It's been the PathFinder by default for everything for a few years now.

Absolutely, the top source is accessible for mining diagonally from 14,18. I have a similar case in my room over here: https://screeps.com/a/#!/room/shard1/E29N12

This issue has been fixed with yesterday's path, thank you.