Topics created by tynstar

Thanks a lot, @artch! I simplified the code a bit more and filed bug 1446634.

I also use Chrome, and I paste in truly massive JS snippets into the console to run adhoc reports.  Never had an issue with it. I do notice that Screeps breaks miserably on Edge, so it's possible there are similar problems with Firefox.

True, but what I'm saying is that this shouldn't happen in situations except for when a brand new creep is spawned, otherwise the person could just step on the site or kill the creep if the site's below another structure. You can withdraw on the same tick yeah, but you can't use energy that you're withdrawing in the same tick, such as for building. You must wait until the next tick, simply because they game isn't sure the energy you're withdrawing will actually be withdrawn.

I repeated my test and could not reproduce the issue. Obviously I must have mixed up things the first time Thanks for the answer.

Yeah I stumbled upon the same issue. However checking for safemode is required anyways and safes you a lot of find calls worst case, so I would consider this a lower priority.

For the record: the new site docs.screeps.com went live today.

OCS has an ok reputation system (if I do say so myself, har har). Maybe you can use that (open source / BSD license).https://github.com/ScreepsOCS/screeps.behaviour-action-pattern/blob/dev/task.reputation.js