avdg

pfff its too easy to store memory by accident when things load slow..

and broke my bot once again :p

wow, with this update the script can be cut at any moment, while everything executed stays executed... scary...

github.com/avdg/screeps/commit/… vs github.com/qiao/heap.js/blob/…

I'm too lazy to benchmark, though I can observe that it will probably do less

Also pushed my priorityStack implementation... Not sure how much it is faster than heap.js (in the worst case it might have a slower sort)

Except here... support.screeps.com/hc/communities/public/questions/…

It's a bit like simcity to be honest :-)

that update broke a lot of stuff I guess...

its back?

changelog will be big...

energy decay increased from 1 to 1000

repair power is increased

and constants are changed (engine file is still reachable)

there seems to be a new object called 'link' in the game

but the api is still up

can't even post

even the simulator is closed

Hmm can't play now

We really need a way to control peace :p

tscmoo is sending a lot of backup :P

tscmoo is kinda going for the offence

and respawning doesn't give me walls :p

wow I'm death

lol, my guards are protecting the edge

uh, I need to fine tune the path cache I guess...

hmm maybe that is the problem

and the target is a moving one

its actually a double sink system

but I need to box the situation before I can make a good conclusion

it seems that when both are trying to find the closest, it may seem to use a lot of time

bringing them closer together

its actually more supply and demand

already aiming to get such stuff done for few days, but transporters are complicated and I had to write a lot of code (and test it)

just noticing that when I'm generalizing the system to my transporters

that sink system is actually putting more load on the pathfinder

probably trying to say hi :-)

ow boy my logs are getting spammed by other bots :p

but I do maintain my bot ai code on github itself, but only the core part

(because code tends to improve a lot if worked on it and managed well)

personally I don't care as much because if I don't push, code gets outdated quick anyway

I'm not sure, I guess it prefers what you want

Hmmm... github.com/…

above 10 uses I guess the code runs faster if reused (by putting them in a function)

under 10 times (? maybe 5, maybe 20 didn't benchmark it) you'll get closer to compile par compared to code compiled once (unless v8 doesn't like to optimize the code)

if they are only used once or twice, the code would probably spend most of the time being compiled

it gives v8 more opportunities to optimize code if they are reused a lot

also I would use more functions later on but introduce them slowly