@deft-code even more so. Thanks for correcting me!

@elynx don't forget to also set swampCost if you're setting plainCost, to keep them at the proper proportion.

Footnote: for (X of Y) doesn't work for all kinds of objects for (X in Y) would... So be warned. But it certainly works for simple arrays and objects.

https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/for...of

It's always been like this, because roads modify the CostMatrix for the pathfinder from default terrain values. They also make swamps more easy to cross too. Ignoring roads will return swamps to their "hard to navigate" state as well (could be added to the documents, though).

Now, the question is, why are you ignoring the roads? From my experience there is absolutely no benefit from that outside of making sure they don't wear down as fast.

If you're trying to make your creeps treat the roads equally to normal plains, you can achieve so by setting plainCost to 1 and swampCost to 5 in the moveTo parameters, this will make roads equal in weight to plains, and creeps will choose the shorter path, however, creeps would still choose to take roads over swamps and walls.

Pretty sure they can at least contact humble store and ask them to correct the description Stores won't "just put things up for sale", they need developer's contact and permission to do so, at the very least.

Have been watching Tigga's deathball sieging one of Muon's rooms. And noticed that every time a power creep uses any of its powers (like DISRUPT_SPAWN), the room does not update any positions. Then on next tick creeps teleport around 2 moves ahead.

In a moment of epiphany, I opened a chrome developer tools console. And lo and behold! Any time a power is used i get the following error in the console:

TypeError: Cannot read property 'texture' of undefined
    at renderer.js?bust=1554143060683":1
    at powerInfluence (renderer.js?bust=1554143060683":1)
    at Sr.runProcessor (renderer.js?bust=1554143060683":1)
    at renderer.js?bust=1554143060683":1
    at Array.forEach (<anonymous>)
    at xr.applyState (renderer.js?bust=1554143060683":1)
    at renderer.js?bust=1554143060683":1
    at Array.forEach (<anonymous>)
    at Sr.applyState (renderer.js?bust=1554143060683":1)
    at Ir.applyState (renderer.js?bust=1554143060683":1)```

It's always the same error about the same property missing. Maybe this'll help you figure it out!

Explains why transfer events appear to have no actual event field specified to them....

The same happens to any of my rooms in Steam client whenever rampart configuration is changed by adding/removing ramparts or making them public/non-public. Just seems to lock the client up for a non-insignificant amount of time.

I find the entire even log system as it is right now very unwieldy and nigh-useless. Certainly not what it could be. Also parsing event logs for every room you run is a significant investment of CPU cycles, which pretty much prevents its use for every day tasks.

@smokeman right. But difference being the same code is executed on all shards, while being aware of the single shard. Console is only executed on the shard you're viewing. My point being, if you were trying to spawn the creep via console, it would've gone through no problem.

And yes, seems like keeping some powercreep data in intershard segment for the sync purposes.