How Kitbag finds a build
What happens between your requirements and the builds on screen.
The short version
Most calculators run forwards: you pick artifacts, they add up the stats. Kitbag runs
backwards. You name what the build has to do, and it finds the sets of artifacts that
do it, cheapest first. If nothing can reach your numbers it says so, and says which
requirement was the one that could not be met.
It runs on your machine, not ours
The whole search happens in your own browser, across as many CPU cores as it can use.
Nothing you type is sent anywhere. The page asks our server for exactly one thing, the
item catalogue, once, and everything after that is local, which is why changing a
number redraws the answer instead of spinning.
Your settings live in the part of the address after the #,
which browsers never transmit. A Kitbag link pasted into Discord carries the entire build with
it, and our server never learns what was in it.
Why it does not just try everything
Per slot there are 103 artifacts, six qualities and sixteen upgrade levels to pick from,
and a container holds up to seven slots. Checking every combination is not slow, it is
impossible:
| Slots |
Combinations |
Distinct sets |
| 3 | 9.7 × 1011 | 1.9 × 105 |
| 5 | 9.5 × 1019 | 1.1 × 108 |
| 7 | 9.2 × 1027 | 3.0 × 1010 |
So Kitbag does not make that search faster. It makes it smaller, in three steps, none of
which can throw away a build that would have won:
-
Only some stats are in play. A question touches a
handful of the 34, and two artifacts that are identical across those are the same
artifact as far as your query is concerned.
-
Some artifacts cannot help. If one is no better
than another on everything you asked for and costs more, no best build needs it.
-
Some cannot appear at all. Where you set a hard
minimum, an artifact that leaves it out of reach even alongside six of the very best
is in no build that works.
What survives is usually a few dozen candidates rather than several hundred, and the
status line under the results tells you how many of the 103 it actually had to search.
Where mixed-quality builds come from
Leaving quality on Any runs seven searches at once, one per grade plus a mixed one. Six
of the seven hold a single grade and so cannot express a build that mixes them, so every
finished build then goes through a second pass that buys a cheaper grade for any slot
that did not need the expensive one. That pass only ever makes a move that costs less
and still meets every requirement, which is where a build of one Legendary and five
Uncommons comes from.
The same question gives the same answer
The search is budgeted in work done rather than in seconds. A fast machine finishes
sooner, but it does not get further: the same query returns the same builds on a phone
and on a desktop, so a link you send someone shows them what it showed you. The clock is
only a backstop.
Where the prices come from
Completed auction sales, not asking prices: what people paid, rather than what sellers
hoped for. Each figure is the median of recent sales, because one Scallop going for three
million against a median of seventy thousand would drag an average along with it.
Prices are held separately for every quality and every upgrade level, which
matters more than it sounds: around 78% of sales are of un-upgraded items, so pooling
them gives you the +0 price wearing a +15 label. On some artifacts that understated the
real cost by 28 times.
Where an artifact trades rarely we still show a price and mark it as resting on thin
evidence, rather than treating it as free. Containers, armour and buffs are not priced
at all, so a budget covers artifacts only.
Why a build stopped where it did
Every result says which requirement it is sitting hardest against. "Why won't it give me
more carry weight" almost always answers to a radiation or psy cap nobody was thinking
about, and a number without that reason is how a tool ends up looking arbitrary.
One artifact you will not see
Rubik has no fixed stats. It rolls a random set of
bonuses, so there is no honest number to put in a sum, and our catalogue carries none.
The effect is that Kitbag never recommends one: an empty socket does the same nothing
for free. If you own a Rubik, treat it as something to fit around a build rather than
something this page can plan for you.