This way of compartmentalizing requests proved to be quite useful in some cases, giving the convenience of “throw it all in a box” while still allowing me to specify which creeps do what. At early levels, the hatchery puts requests into that group, but at RCL4+, the hatchery gets its own dedicated attendant (the queen) and its own request group. For example, each colony has a request group which suppliers attend to. TransportRequestGroups (which existed in my old AI, but which I cleaned up in the Overlord Overload rewrite) act as a “box” to group prioritized resource requests. Finally, in Part 3, I’ll give a detailed explanation of how my new logistics system works.In Part 2, I present a generalization of the “creep routing problem”, discuss why finding an exact solution is infeasible and motivate my approach in finding an approximate solution to the problem.In Part 1, I’ll talk about the advantages and disadvantages of my old system and why it motivated an overhauled logistics system.
Since this post is really long (but I hope it’s worth the read!), I’ve divided it up into three parts: In this post, I’m going to talk about the overhauled logistics system I’ve spent the last few months working on. (And it’s probably the single part of the game I’ve spent the most time thinking about.) Logistics – the problem of efficiently transporting resources – is one of the most interesting and deepest problems in Screeps.
0 kommentar(er)
