Topics created by Estecka

@mrfaul yeah, my thing is i hate digging through the start menu. so anything that can be done in the run prompt will be done. and yeah, keyboard shortcuts are clutch. why move your right hand to the mouse if you dont have to. it's just less efficient...

I'll take it as a "this is how it works" and make a feature request of it instead. I'll mark the issue as solved since I got something working.

the client is just a browser, and your message is simply attached without being processed by the server. you can do everything if you want .. including executing javascript by using script tags.

Well you are free to modify any aspects of the engine like lowering the constants so you build faster etc. Also there are different tools as mods available, but you have to be aware that those are cmd line based.

I don't expect to get this any time soon nor need it urgently; if I can get this into the devs' backlog it will be good enough. I don't have a very extensive custom UI... yet. RoomVisuals helps so much with understanding what's going on at a glance.

If only we had some kind of MapVisuals so we could use this in a map overlay!

Since we pretty much hijacked this I created a separated topic for it: Refining the game start: A "claim room" button instead of a forced "place spawn":

https://screeps.com/forum/topic/2437/ptr-changelog-2018-11-01-creep-pull/2 Under other unrelated changes, currently pending / on PTR

You can use Object.defineProperty with {enumerable: false}. > Array.prototype.foo = function() {return 'bar';} > for (let i in ['a', 'b', 'c']) console.log(i); 0 1 2 foo > Object.defineProperty(Array.prototype, 'foo', {value: function() {return 'bar';}, enumerable: false}) > for (let i in ['a', 'b', 'c']) console.log(i); 0 1 2

For fast iterations just use a local server, you shouldn't have those problems then. It is far better anyway to only push "stable" versions to the server anyway.

The fix is deployed, this shouldn't happen again.

Checking obstacles for players would be incorrect. There are a few cases when such check is excessive, like a creep stepping over a structure which will be destroyed at the next tick. These cases are more or less rare but still, it's breaking change. As for your other questions, well, if you're asking this then you're probably experienced enough to migrate to PathFinder.search which provides lots of necessary information (sooner or later, this happens to all of us).

That's correct, upgrading lodash may break someone's code.

It is fixed for me now.