@tigga said in Season #1 announcement:

Looking forward to this!

At the same time we're going to announce some other exciting news as well

Hmm. Arena? New power creeps? Something else entirely? Or maybe the warp container + terminal changes drop?

I still hate the new terminal changes, but I am looking forward to new things

@maxion Why should they have to accept it? If playercreep pulls enemycreep left, and enemycreep moves right, both should just stay still. Adding in logic so that if player creep pulls downleft and enemycreep moves downright, they both move straight down would just be a bonus.

Can I ask why this is not creep.pull(target); creep.move(destination) or creep.pull(target,direction)?

Those seem much more useful and interesting.

I failed to elucidate properly.

This code has run for weeks properly on the live world.

There is no rhyme or reason for it to intermittently fail on a private server, unless something wonky is going on in the server.

sparr: role is creep.memory.role, inside a loop of Game.creeps.

All of my creeps have a role, and it makes no sense for the error to be intermittent.

Randomly will begin to receive the following error stack, after a while it sometimes just stops.

TypeError: role.startsWith is not a function
 at Object.run (SpawnManager:75:22)
 at Object.wrap (screeps-profiler:272:12)
 at Object.module.exports.loop (main:18:12)
 at __mainLoop:1:52
 at ContextifyScript.Script.runInContext (vm.js:35:29)

Ive been running the private server for a while, GCL is climbing, but CPU limit remains static.

I have not been able to locate a constant to edit\enable this.

I have a feeling this might be related to the lack of email verification, but am unsure.

Several players in slack are recieving this error, while other players are having no issues.

Did something change in maintenance this morning?

I'm totally against the reservations limit unless it counts towards sources and not rooms - e.g. u get 6 boosted sources in the reserved rooms, but not allowing us to reserve rooms basically negates the idea of it.

Id suggest seperating claiming and boosting sources, and requiring a claim to unlock the sources.

1 claimbodypart doing creep.boostSources(controller) gives... 100ticks of boost, but they disappear if the claim runs out.

 Another alternative to reducing unclaimed energy sources capacity (first two changes in the changelog)
would be limiting the reservations count available to a player depending on his/her GCL. Say, three reserved
rooms per one claimed room. You can harvest as many remote sources as you wish, but you can “upgrade” only
6 remote sources per claimed room maximum. It'd allow to achieve nearly the same effect we want to see with
these first two items in the changelog.

 What do you think about it?

This looks like a much better solution if the issue is excessive reservations.  I honestly doubt that there are that many people who would be affected by this change, but it does allow for GCL scaling, which I like.