SCREEPS FLAGS UPGRADE
SCREEPS FLAGS FULL
SCREEPS FLAGS CODE
SCREEPS FLAGS FREE

This cache brought the job controller usage down to the level of the other processes, but the increase in memory size has increased the time spent on prepare (yellow). Now when creating an energy job I first check if the premade job exists. So seeing as memory is bit faster now I decided to put premade jobs with hashes into an object keyed on the building id. Hashing the job is not a quick process hence the high usage.

SCREEPS FLAGS CODE

So much so that the overall CPU usage (orange) almost matches it higher up.ДЄ quick read through of my code showed me that for every building that might receive energy I was creating a job, hashing it, and then looking for that hash in the database. Straight away I can see that my highest CPU user is the jobs controller (light blue). From here I can see where my code needs improving and watch my improvements go to work. I added some profiling to my code to monitor how much each process is using. This is the code I added at the top of my loop to make use of this. Your code moves from node to node between ticks so you canвЂ™t just start using mory instead and leave it at that but with a little check to see if this is the same node as the previous tick you can make some savings. These nodes preserve the global object between runs which means anything you put in there can be used again next tick without deserializing it or processing it. The first gain I made was to abuse how Screeps runs players code.

SCREEPS FLAGS FREE

Knowing that some players IвЂ™ve spoken to on Slack run empires bigger than mine on the free 10 CPU you get from buying on Steam my CPU usage is rather high.

SCREEPS FLAGS UPGRADE

For example, I added links to improve the energy transfer speed in my rooms and saw my time to upgrade nearly half.

The graphing and estimation lets me see how improvements to my code are doing. I have the grafana dashboard open most of the time so I can see how everything is going without opening the whole game. It has quickly become a huge part of how I play Screeps. Grafana then reads data from Graphite and produces graphs and another analysis tools. In a nutshell, 1 program uses the screeps API to move Memory.stats in statsd which uses Graphite to store data. I have an HP microserver at home which handles the docker setup from screeps-grafana pretty well. IвЂ™ve seen a few screenshots on the Screeps Slack group of Grafana dashboards for a players Empire which I looked at enviously. The existence of the flag adds a job to the queue that essentially a harvest job with another rooms storage as its destination. Again with the jobs system, this was pretty easy.

SCREEPS FLAGS FULL

To get back to full functionality I need to add some flags for harvesting other rooms.

If I want it to break from its norm and do another job I drop a flag of a certain colour and the AI handles it. When it did reach RC3 both of my source containers died before the tower got built which threw a huge spanner in the works and added a few hours to wait for that room to be self-sufficient.

The sources are so far apart that it takes a lot longer to get energy where itвЂ™s needed. Of the 2 rooms, I claimed 1 has gone really well, getting to RC3 before anything died and building up very nicely. Once you hit RC3 in a room you can drop a tower which can heal everything very quickly, my AI relies on towers to heal. I had quite a few issues with me not having healer creeps. Adding extractors back in took a small amount of work (see commit). The new AI makes adding new jobs a lot easier. To get this working I get my creeps to move to the flags RoomPosition and then claim the rooms controller once they are nearTo the RoomPosition. I need to move to the target room and then aim for the controller. Game.rooms only contains rooms you control or have creeps in so I canвЂ™t just get the controller of the room the flag is in. It took a bit of work getting the room claiming system to work. It wasnвЂ™t important at the time, my rooms were all dead and I only needed it to gather energy and build new creeps. The new AI from part 12 was not as complete when it was called into service. This is part 13 of my Screeps story, you can read the whole story here. If (mycreep.2017 Screeps Screeps Part 13 вЂ“ Building Up if creep has no energy, go to the energy source and harvest some if our creep doesn't exist, create it from our spawn The code inside of these curly brackets will run once per tick. If you're new to programming, or you're new to JavaScript, but you think Screeps is cool and you really want to play it, in this tutorial I'm going to show you the simplest Screeps code possible and I'm going to walk you through step-by-step what each line of code means, what it does, and how I got there.

Screeps flags