administrators

This is a known issue, we're working on it But thanks for reporting anyway

Thanks for the report, we'll take a look

The fix should be deployed atm.

It's sad to hear your code is broken. Did you have a chance to check the change on the PTR? It was deployed 2 months ago, seems like plenty of time to prepare. All known possible breaking use cases are listed on the original PR page:

• Object.create(RoomPosition.prototype, ...) -- please use new RoomPosition

• Object.assign({}, rp) - properties on RoomPosition are no longer "own properties" so they won't be picked up by functions that filter on own properties

• rp.x = -1; rp.y = 50 -- invalid values are no longer supported on RoomPosition

• rp.roomName = 'e1s1' -- lowercase room names will be converted to uppercase

I believe it's one of these. And they should not be very hard to fix.

As to the logic behind this change, it's about heap memory usage which becomes the most crucial and vital weakness of many players' code since our transition to IVM, especially for those who have visibility to many rooms and game objects.

OK, we updated usePower documentation a bit, and added the full list of available powers to the Power article.

As to specific powers subtle semantics, I don't think it's realistic to expect all possible nuances and edge cases to be explained in the description, it'd be more like wiki rather than documentation. We better leave this to individual players and community to figure out.

@crusher48 It's in the game client, check this page https://screeps.com/a/#!/overview/power. Don't hesitate to create a PC there, it won't be saved until you click Save, you can just plan skills and then cancel.

@tigga Thank you for the report, we'll fix it.

@twothe All game objects and their methods are fully documented. What do you think can be improved?

Nice catch! Thanks, fixed.

It's a typo. Copy-pasted from another power and forgot to change. Should have been entire room range. Thanks for reporting, fixed.