Topics created by ThyReaper

Figured it out. Python's default auth handling expects a specific style of 401 response to the initialize request, which I guess isn't provided by the screeps site.

The three healers are blocking the attacker, so it's unable to find a path (and the healers are unable to follow it along that path). Once your creep came in on the other side they reshuffled and unblocked the path. Apparently invaders aren't smart enough to get out of each other's way.

Thanks for pointing out that file, that'll be helpful. Still, I'd prefer it to be officially documented - otherwise, the constants aren't necessarily guaranteed to be defined going forward.

I’m unaware of any methods of disabling garbage collection during execution of a specific code fragment (if you know them, please share). You can manually execute only non-incremental major GC runs that take very long time, and if you run them after each player script is over, it can easily make ticks 2 times slower and even more. Besides, another problem apart from the GC is runtime code optimizations that the V8 executes when analyzing code. They are very dependent on usage patterns that can vary from tick to tick, and various optimizations can behave differently. As for the API methods relating to CPU controlling – yes, we consider adding them in the future.