I agree, in a way:

I think the boolean naming convention should be dropped, because either way, it doesn't make a lot of sense to write these methods with boolean naming conventions, and new users would have issues.

As a solution, perhaps using a "Call State" property instead, as a naming convention instead:

> Game.spawns.Spawn1.createState == 0; // Certainly assures that users are not reading this as a boolean expression.

Both ways of applying boolean naming conventions require a "learning curve", and are not intuitive:

> method.canDo() == 0; // Does not make sense as a boolean expression.
> method.cannotDo() == 0; // Does not make sense as a boolean expression, either.
> mehod.canDo() == 1; // Makes a lot of sense, and readable, but breaks exit code convention.

Either Way:

At some point there is going to be some refactoring/modification of the API, and it would help immensely to /forcibly require/ a "main" comment, or var apiModule = require("api-v.1.0.0"); or some such convention, that can let users know in advance their API level has been deprecated.

Implementation of return codes is certainly more economical that try/catch blocks--and returning a Creep object would break this efficiency.

However:
Having exit codes should not preclude passing in callbacks or object pointers, which modifies the reference passed in:

> var createdCreep = {};
> Game.spawns.Spawn1.createCreep([WORK, CARRY, MOVE], 'Harvester1', createdCreep);

this would certainly affect performance, code length, etc.

Memory Object not Persistent

Does anyone know why the Memory object wouldn't persist?

Notes:

1. In Tutorial Mode, right at the Build Road step.
2. main is completely commented out.
3. First attempt to play tutorial advanced to the point where the road was actually being built.
4. Due to server email spam, that I had not spawned in the "World", I exited tutorial mode, entered game mode and created a spawn1.
5. Returned to Tutorial mode, and cannot advance past this Build Road step.
6. Memory state completely vanishes.

Here is the Console log:

> Game.creeps.Worker1.memory.role = "harvester"; console.log(Game.creeps.Worker1.memory.role); console.log(JSON.stringify(Memory.creeps));
< [1:09:47 AM] harvester
< [1:09:47 AM] {"Worker1":{"role":"harvester"}}
< harvester
> Game.creeps.Builder1.memory.role = "builder"; console.log(Game.creeps.Builder1.memory.role); console.log(JSON.stringify(Memory.creeps));
< [1:09:48 AM] builder
< [1:09:48 AM] {"Builder1":{"role":"builder"}}
< builder
> console.log(JSON.stringify(Memory));
< [1:09:52 AM] {}
< undefined

Also,

After arriving at the point of the Build Roads tutorial step, the Memory editor cannot be used to reassign the roles--the changes do not persist.

The Memory object appears to not work--at all.

Memory.creeps = { Worker1 : { role: 'harvester'}, Worker2 : { role: 'harvester'}, Builder1 : { role: 'builder'}};
< [2:14:49 PM] Found Harvester.
< [2:14:49 PM] Found Harvester.
< [2:14:49 PM] Found Builder.
< [object Object]
JSON.stringify(Memory);
< {}
JSON.stringify(Memory.creeps);
< undefined

Oops. Yes, I meant to say the Memory object method is not working, in ADDITION to Game.creeps.Worker1.role.

I noticed this always happens at the Tutorial point where you begin building roads. The very first time I went through the tutorial, I was able to start building the roads, but was receiving emailed error messages from the server, for not building my spawn1 in the regular game.

After I came back to the Tutorial, these errors started happening.

Memory.creeps.Worker1.role = 'harvester';

results in:

[1:58:39 PM] TypeError: Cannot read property 'Worker1' of undefined
at _console1434229119212_0:1:5332
at Object.c.runCode:5:30325

Just as this doesn't work:

Game.creeps.Worker1.role = 'harvester';
< harvester
Game.creeps.Builder1.role = 'builder';
< builder
Game.creeps.Builder1.role;
< undefined
Game.creeps.Builder1.memory.role;
< undefined

I have this same issue.

In the Memory Navigator UI, I have the following message:

spawns.Spawn1 Incorrect memory path.

Can you provide the answer to the issue?

I am having a similar issue, and would like to know if this is just End User Error.

This is not necessarily a bug, but potentially an ambiguity in the tutorial.

If while doing the Tutorial, you take your time, browse through the API documentation, etc--after you have automated a creep harvesting, and transferEnergy(), the creeps will stop moving ... because they are Spawn1 is full.

I wanted to note this, in case new users want to find out what is going on.

.dropEnergy() ... will start them on their way again.

Cheers!

Hello,

In the Tutorial, there is a step to assign roles to creeps. The "Code Tip" is something like:

Game.creeps.Worker1.role = 'harvester';
Game.creeps.Worker2.role = 'harvester';
Game.creeps.Builder1.role = 'builder';

And does not work, but this does:

Game.creeps.Worker1.memory.role = 'harvester';
Game.creeps.Worker2.memory.role = 'harvester';
Game.creeps.Builder1.memory.role = 'builder';