Yea I didn't mean throw. I meant return an error code. but you can't edit posts here

I couldn't figure out why my creeps would only have 30 parts. I then found in the docs that creeps can only have a max of 30 parts. When calling Spawn.createCreep with a body that had more than 30 parts it would just user the first 30 and ignore the rest. I would expect some sort of error response.

One thing they could do to prevent the whole 'forfeit your tick' is by wrapping all console input in a try/catch block. In case an error occurs, display it and then run the regular script code.

I tried this and I still get the error.

I have been hanging out in the #screeps irc channel people are interested in talking strategy but few are interested in trading code review. Is anyone here interested?

My repo https://github.com/unstoppablecarl/screeps

When deploying, running console commands, or making memory updates manually I occasionally get this error.

proto-room:13
        this.job_list = new JobList(this);
                        ^
TypeError: object is not a function
    at Room.jobList (proto-room:13:25)
    at Creep.job (proto-creep:106:22)
    at Creep.act (proto-creep:10:20)
    at arrayEach (/opt/engine/node_modules/lodash/index.js:1289:13)
    at Function.<anonymous> (/opt/engine/node_modules/lodash/index.js:3345:13)
    at main:14:7

This is the line it is referring to https://github.com/unstoppablecarl/screeps/blob/5da67634bb3aee7ec7eb7aecaaec77a5b52eac05/proto-room.js#L13

As you can see it is fine there should be no error.

Agreed. This would make it much easier to manage flags and anything under them. As a primarily cosmetic change I think this would be low effort to implement.

I agree. There should be a mechanism in place that lets you identify creeps better at the very least see their role or a custom memory field in the sidebar when they are selected.

I would very much like to see this.