After a bit of analysis, it appears that the PTR common module is stuck on an old commit, judging by the fact that CONTROLLER_DOWNGRADE_RESTORE is defined but FIND_TOMBSTONES is not. However, it does have updated versions of the other modules; Tombstone is available in the global namespace.

@crusher48 The chances of natural invaders being an issue to an attacker seem even lower than the chances of invaders being an issue for their creators.

FWIW I am using IVM.

@artch said in StructureSpawn causing "circular structure" error on JSON.stringify():

We can add RawMemory.autoCreateObjects boolean property which is true by default, but you can change it to false before accessing Memory first time on the tick.

I think it should be false by default, but if there were an option I can use to prevent this, I would be absolutely ecstatic.

@gankdalf I don't like setting time frames, but it's definitely our focus now, and will become our primary development project as early as this summer.

Game.map.findRoute tends to always work, but it isn't guaranteed.

PathFinder is the native library for pathfinding. (iirc) The default cost matrix is the same "cost matrix" used by findPath, meaning all objects that can block a creep are max path cost, swamps are more expensive than plain, and roads are 2x cheaper than road.

If you're building a custom CostMatrix, it's best to do the whole thing yourself than rely on some interleaving between the default matrix and your custom overlay.

findPath is the old pathfinder built entirely in js. It's good to get started with but not good if you want efficiency.

A lot of documentation is scattered, typically the best resource is your own experience. If you want a fast and very controllable path, only use PathFinder.

To be honest, I don't see the advantage of the current operate extensions over the previous iteration. The previous iteration provided the ability to load up extra resources into extensions to save on the amount of extensions each hauler needed to visit, save up resources for multiple consecutive creep spawns, and even allow smaller rooms to deploy stronger creeps by buffing up their extensions to a higher level. The current operate extensions does fill extensions faster and can potentially replace one dedicated hauler creep, but since the power creep has carry capacity anyways, it can already fill extensions in a room quite quickly just using its own carry capacity (filling about 100 energy per tick to RCL8 extensions just through withdraw and transfer commands). Increasing extension capacity provides more tactical options than just merely filling extensions.

as long as you're tweaking the server and those heap spikes are a regularily problem, it would be nice if you could spend more heap memory (in general, gcl-dependent, or per claimed room don't know what's possilble).. so nobody has to worry about being thrown out of the game after a server tweak

Screeps feels tuned so that someone who is engaged with the game on a daily basis is favored in most conflicts.

For example, the difference of attacking someone who is AFK for a coupel days vs someone who is active is a huge change. This is just another extension of that, where if they come back they can recover quickly from losses, but if they ignore it they can lose everything.

I'm with @artch on this, I think its a (mostly) healthy way to keep people who care about the game significantly engaged. It might be tuned a little too strongly, but when you remember it took someone probably a month to build up that room to level 8, losing half of that while afk is a downer.

@shedletsky This is my first attempt at adding it to the docs. This is my local copy. I am not sure the formatting is consistent this way, but I have run out of time for goofing off on this.

EDIT - and it seems the wording on custom filters not being cached needs reworded ... the base query is cached, but the filtering is not cached.

Turns out this was caused by the assets folder missing in the beta branch.

@o4kapuk @Dissi @artch

Could this be merged into Game.map.isRoomAvailable ?
It could return a number instead of the bool.

Memory is not affected, it's the same thing as a syntax error in a code download.

It gets really fun when you place a flag by hand in a room that has no active entities in it (enemy or friendly creeps). The flag gets added to your Game.flags object but you can't modify it in the code, which means if you try to change the color it fails to actually change the color even though setColor returns 0.

Rampart juggling is also effective. Just keep the invader marching back and forth between two of your ramparts. Sure that doesn't kill the invader but it dramatically reduces the amount of damage it will do to your wall.

The real point here is there are multiple effective techniques to deal with them. In a tight combat scenario against an aggressive human neighbor strong invaders could be a real problem but that is true regardless of RCL. It might be a good idea to disable invaders in a battle arena but I think they're fine on the MMO server.

Another instance of same issue, link for tick immediately proceeding event: https://screeps.com/a/#!/history/shard2/W9N41?t=5263598

Edit: Oh I see what happened to me was not the same issue. There was nowhere else for the enemy creep to go

I doubt I will get around to creating a PR any time soon as I know the private server code very well and have many other projects that are progressing slowly.

So if anyone else wants to put a PR in for this, feel free.

Fixed.