^ You can also click 'source' on that link-page and it will take you to the github for that lodash function.

https://github.com/lodash/lodash/blob/3.10.1/lodash.js#L6307

Folks have asked, though it was determined it would split the community too much (some folks would not/could not change) and the features offered wouldn't be good enough.

Further reading:

https://screeps.com/forum/topic/2101/screeps-discord

https://wiki.screepspl.us/index.php/Community_Communication

If the exact error text is Room.find then likely as your first example is showing, you need to have Game.rooms['RoomNameStringHere'].find();

specifically, find() needs to be called on a room object, so you could also do:

let myRoom = Game.rooms[RoomNameGoesHere];
let myTowers = myRoom.find(FIND_MY_STRUCTURES, {filter: {structureType: STRUCTURE_TOWER}});

Would recommend as well if you haven't yet, checking out slack, very rapid response most of the time and more dynamic.

Yes, though to expand on your question filter is an option for room.find that uses lodash's filter to search the result of the FIND_* you call, your passing it an object, filter, with the arguments you want it to use when searching.

When you pass it a filter, it calls the lodash here: https://github.com/screeps/engine/blob/master/src/game/rooms.js#L641

You can read more about lodash's filter here: https://lodash.com/docs/3.10.1#filter

sources[poi].x is likely the issue. Every game object has a roomPosition, which is normally stored in its .pos property.

https://docs.screeps.com/api/#Source.pos

So, sources[poi].pos.x & sources[poi].pos.y will be your X and Y values, while sources[poi].x is no a defined property of sources, valueOf is probably making it NaN, instead of throwing an error (I presume)

Also, would recommend checking out the screep's slack! There's a #help section that is normally pretty lively and faster to get response, bit more dynamic as well.

Before there were shards, the MMO was just shard 0. As it was the only map/server it was even larger than it is now, and tick times (If I recall correctly) even longer.

With the advent of shards, S1 started out small and opened up more but still stayed a smaller size, S2 followed and finally S3 which is CPU restricted and was billed as the non subscriber shard, where everyone was on 20 CPU across the board.

S0 since then, has had rooms slowly being deactivated in order (I assume) To speed up tick time, including the time when a whole out-side ring was collapsed:

https://twitter.com/ScreepsGame/status/994137796574089216

There were/are some player movements who went around and tried to take out zombie players and clean out S0 rooms, but not sure where that stands now.

S0 also hosts some of the older players, their codebases. Not sure the exact factors that slow it down, but considering it has 11339 claimable rooms and no CPU cap (so older players have at max, 300) While Say, S3 has 7076 rooms and a 20 CPU cap on everyone, it prob slows it down a bit, even though S3 has way more players.

Can remove them with the CLI. default steam I think its removeWhere. Mongo just remove, so depends on what your using. Could also use mods/make a mod to disable them.

I'd recommend joining slack and asking around #servers, slack tends to be quicker/livelier responses.

There is a slack:

https://chat.screeps.com/

in slack, there is a channel called #thewarpath, conflicts/nuke launches/landings are automatically collected and posted there.

There is a #politics channel but its not used alot, generally watching the #general channel and a few others you can read and learn of many things goin' on.

there's also a #help channel if you have questions.

Have you tried submitting a ticket?

https://support.screeps.com/hc/en-us/requests/new

https://docs.screeps.com/creeps.html#Movement

Each body part except MOVE and empty CARRY generate fatigue.

1 point per body part on roads, 2 on plain land, 10 on swamp. Each MOVE body part decreases fatigue points by 2 per tick. The creep cannot move when its fatigue is greater than zero.

If your interested in the code side, can view the movement intent.

https://github.com/screeps/engine/blob/master/src/processor/intents/movement.js