I suspect that your client and the code you see there is out of sync with what is actually on the server. Try to restart your client. Log on using your browser or do something that can force an update.

letgives us the same scope as const

I personally still don't understand how this can work. I just did a simple test where I defined a variable with var at the scope of my main and not even that is working. Trying to use it from the console still gives an error indicating that the variable is undefined.

You are using some kind of magic and I feel left out.
Edit: I thought about it some more and I see now that the console command you tried in the screenshot still doesn't work for you either. Your issue was with your script and you tried to copy the statement to the console.

Was the error you got in the script, temporarily, exactly the same as the one you got when you tried running the statement in the console window?

@ffmathy Yes, at room control level 1 you can build one spawn.

@mrfaul The experience is probably wastly different for different players. From my standpoint it isn't the experienced players that new players should be concerned about, but the players starting at roughtly the same time in the same area. Those are generally more agressive in order to secure expansion options.

I haven't verified your code, but it seems to be trying to print som text next to your spawn. This is probably unrelated to the issue you describe in your original post where you talk about the behaviour of your creeps.

What do you mean when you say "creeps randomly abandon my spawn". Maybe you can include some code snippets of the related code?

To answer your original question more specifically. There is a function called getObjectById on the Game object you can use to get any game object by its id. The only limitation is that the game object has to be in a room that is visible to you.

The default behaviour of the moveTo function for creeps is to reuse the same path for 5 ticks. You can change the tick count with the reusePath option.

My own strategy is to generate a path with other creeps ignored and to keep the path for 100 ticks. If the creep is stuck, then I let it get a new path where other creeps are treated as obstructions. This is crude, but suprisingly effective.

@4nytime You probably also have some logic using those memory values. Double check them for the mistake mentioned by Donatzor.

The tooltip that pop up when I hover over the button covers almost all of it. It gets in the way of the click and cause the button-hover-event to deactivate. This creates an annoying flickering where the tooltip comes and go.

There is a small stip on the bottom of the button where you can point without getting the tooltip in the way.

It would be nice if the tooltip could be moved away from the button itself. The tooltip is basically anchored on the wrong side of the button.

I suspect that you have encountered the same issue with path finding as many before you. The creep bounce back and forth between rooms because the moveTo action returns "ERR_NO_PATH" the first tick in the new room.

https://screeps.com/forum/topic/1352/err_no_path-when-creep-moveto-flag-in-another-room/16