NOTE: This is no longer the case - boosted CARRY now allows carrying more without generating extra fatigue. See:
(sorry, I know this is a really old thread, but it's still the first search result for "carry boost")
As with any node environment, global does exist in screeps and is the global object. I put global.Game === Game into the console and got true. Perhaps something in the framework is messing it up. What framework are you trying to use?
I too find this popup really annoying - I really wish they'd do something to improve the selection UI.
I've made suggestions previously such as showing all objects of the selected tile in the right-hand menu, but the main issue with that is there are two very different things you might want to select - creeps, which move, and static objects, which don't. If you select a creep you want the selection to stick with it as it moves.
Actually that's another thing that's annoying - if you want to select a creep as it moves you have to click on the tile it is moving to. If you click on the creep itself you often end up with a popup that just says "road" because the creep has moved away. The UI should really handle click events on the creeps themselves, not just tiles.
Selecting the highest priority object sounds like a good idea, I guess the main question is how to make the optional menu clear enough but not get in the way. This could also solve the problem of ramparts - if I click on my storage I just want the storage, I rarely care about the rampart protecting it. If it selected the storage by default but had a menu where you could select the rampart with a second click that would be much better.
I would suggest the priority should be:
According to https://docs.screeps.com/api/#Room.findExitTo, findExitTo can accept either a string (room name) or a Room object.
I don't know why you need the spawn ID for this, but you can get spawns like this:
let spawn = room.find(FIND_MY_SPAWNS)[0];
@artch said in Draft: Seasonal server:
One more additional reason for selling season entrance fee: we may set up a reward for best players in the season. Say, 1 Subscription Token for everyone in season TOP-X.
Nice idea!
I would hope that the time spent on the chronicle, videos, etc would turn out to be really good marketing for you and end up paying for itself. Obviously that may or may not be the reality but I'm sure we all wish for screeps continued success 
The unique content is an interesting one. I'd be really happy with just a seasonal version of the current game. But ranked goals and interesting challenges is a pretty exciting prospect too!
Please see https://docs.screeps.com/api/#Constants and the documentation for StructureSpawn.spawnCreep.
Screeps return codes are like return codes in C. 0 means success, and anything else is an error code that gives some explanation of what went wrong.
So in your first example you specified dryRun: true and got 0 (OK) because it was possible. So you run with dryRun: false, and it creates the creep.
Then you get -6 (ERR_NOT_ENOUGH_ENERGY), because you've just used the energy to spawn the first creep and you don't have enough to spawn another one.
The final example gives -10 (ERR_INVALID_ARGS), because
spawnCreep([WORK,CARRY,MOVE], 'bab', {dryRun: true} == true);
is equivalant to:
spawnCreep([WORK,CARRY,MOVE], 'bab', false);
...which is not valid.
I am totally in favour of a seasonal server - I've been waiting for this for a long time.
However, like others I feel the pricing is a bit strange - you really run the risk of making this feel like double-charging. @Orlet has excellent suggestions there.
I understand why you would want to tie-in with the persistent game and help promote it, but I think you should seriously consider option 1 to just completely avoid the double-charging issue completely. If you do go for option 2 you are going to have to think very carefully about your marketing.
There is another issue I would like to raise here. I personally have an issue with subscription services and prefer to only buy lifetime subscriptions or not at all. Are you considering any kind of lifetime membership for the seasonal servers? Also, what about players who are only interested in the seasonal servers? It seems strange that you can't buy access to the high CPU seasonal server without also getting access to the persistent servers.
Personally I would choose to give up access to the persistent servers and only run on the seasonal servers, given the choice. Perhaps you've deliberately designed the pricing to prevent that. But it might be nice to have the choice. The lifetime subscription was quite an expense and I'm not really happy about possibly having to pay similar again for the seasonal access.
Another suggestion would be to have a fixed CPU limit on the seasonal server (say 100 CPU) and give players a choice of how to access it:
@artch, I have to say that in light of the recent update I am now quite confused by the decision not to do anything about this.
I would urge you to rethink your previous assertion that this would be a major breaking change. The community has put in significant effort to investigate and show that this change would actually have very minimal impact.
The strongholds update did actually contain several major breaking changes, so clearly you are willing to make changes if the benefits are clear. I think they are clear in this case. The current situation results in strange and confusing bugs and there is no advantage to keeping it this way other than some notion of backwards compatibility, which is pretty moot since this has been shown to be almost entirely backwards compatible. Additionally, it is exactly those players that would be affected who are asking for this to be changed.
We keep getting memory corruption on shard2, with creeps losing their memory or parts of it.
It's happened just now - a few minutes before I got an email notification with the following error:
ReplyError: OOM command not allowed when used memory > 'maxmemory'.
and then 5 minutes later all of my creeps have lost their memory.
Any news on what's going on here? This is pretty serious, it would be nice to at least know that it is being fixed!