Not sure how I got in this scenario, but apparently after running my ai with the new pathfinder, I got in a scenario where my ai was half dead and timing out. After removing `PathFinder.use(true)` this seems fixed.
Of course it`s just speculating if the new pathfinder actually caused the fix (or just a push of the code triggered it) or what in the new pathfinder may cause the timeout... But I guess it`s better way better to post this incident anyway in case other may have similar troubles.
In which room does this problem take place? (I wish we could find the rooms a player has by looking up by their name though)
I have received this message, I am at least 20 rooms away where this is happening
Your rampart #5606a32cd8fd75310bee2e02 in room W15S21 is under attack!
hmm, how is data encoded, do we use ascii, or limit ourself to the set a-z0-9 (1 storage device alone can have up to 51 states though...)
I think it would be interesting to see how the pathfinder was build. Then we can get the useful parts out of it.
Woops, its https://mikolalysenko.github.io/l1-path-finder/www/. The # part of the url isn't useful 
https://mikolalysenko.github.io/l1-path-finder/www/#pairingheap
Sadly the nodes don't support weights, but otherwise a very interesting pathfinder.
And bit annoying to track what the creeps are doing...
Are you sure there is no syntax error in the module?
You might want to start with a few commands to get a basic bot, so you get a basic feeling how javascript works.
Then you might want to learn more about javascript, blend it in with some things in the screeps api. That should be sufficient to build a basic bot.
Reading a lot of stuff about javascript may help to get your javascript skills up, there are lots of articles on the internet, that's just a matter of getting the information from good sources like from mozilla/<insert whatever organization that cares about js development> developers zone or congresses, tutorials, workshops, or anything that is aimed for a beginning js developer.
And don't be afraid to make mistakes, it certainly will happen. With good information and later by having some javascript experience, it will be easy many of those mistakes (though some mistakes will be understandable hard to avoid).
And the most important part, have fun.
uh the snippet didn't show up correctly, just watch this link
https://help.github.com/articles/github-flavored-markdown/#syntax-highlighting
Hmm, I tried a simple test and this works:
Spawn.prototype.test = function() {
console.log("Hello world");
}
Game.spawns.Spawn1.test();
Also, I use this to highlight my code (I hope it shows up correctly)
<some random code here>
Are you sure the prototype is included? insert a console line right after declaring the function for test purposes.
Steps to reproduce:
Expected:
All changes should sync with all editors
Result:
Changes saved in main editor updates external editors as expected.
Changes saved in external editor doesn't update in main editor, which isn't working as expected.
I have about 40 repos and the list stops with r where s becomes after because my repo is called screeps (assuming the list is ordered alphabetically, though I just heard a rumour that organisation repos are listed first).
It would make no sense to have Room.energyAvailable with 2 spawns, since both spawns can't use energy from each other. Spawns can only call energy available by themselves and extensions.
That's why I request for a separate spawn.energyAvailable and room.energyAvailable properties.
Uh after some discussion on the chat, because of the confusion, it might be better to have a spawn.energyAvailable and room.energyAvailable (spawn has some energy to play with, not all the energy in the room anyway).
Please don't compare with three element at the same time. Separate them like
a < something && something < b
Yeah, life woud be a lot easier but javascript sadly won't understatement you.
Anyone who succeeded? I tried both in desktop and android, both using firefox 39 and I can't log in using the github icon.