How Everloot works

Every fact on Everloot that comes from play starts as something a player saw in game. This page follows one of them, say a loot window, from the game to a page on the site. The same rules apply to the website, the API and the MCP server.

The addon records#

The Everloot addon notes what happens around you while you play: drops, vendors, auction prices you browse, recipes, trainers, gold in and out. It saves them to a file on your computer. Nothing leaves your machine until you upload.

Some modules are off until you turn them on. The census is one, and the list of your installed addons is another. Install steps are in Install the addon.

You upload#

You choose when to upload. On the upload page you see a preview of everything before it is sent. The optional Desktop App can do the same after you log out, and it shows what leaves your computer. See Upload your data.

Uploaded observations are public as anonymous records, with no character names and without your install id, so anyone can check our counts. What is never published, and why, is on Privacy and your data.

Three installs have to agree#

A drop, a vendor item, a spawn point, a recipe range or a market price appears as a fact only once at least 3 different installs have reported it the same way. For prices and catalogue entries, different means different upload addresses, with an IPv6 address counted by its /64 block. One household cannot make a fact true on its own.

On the site you see this as a row of diamonds, one for each install that has reported the fact:

Until three agree, the page says so instead of guessing.

Unrecorded is not zero#

If nobody has recorded something, the page says unrecorded. A zero appears only when it was measured: for example, "0 drops in 40 kills" once three installs killed that creature and none of them saw the item. A storage outage or a missing source is never shown as zero.

Loot windows show what dropped, not how many kills it took, so they do not make a drop rate on their own. A rate is drops divided by recorded kills.

Found in game files, unconfirmed#

Some pages, such as the talent calculator and the map, use data a maintainer read from the game's own files. Blizzard hides some item details until an item drops, so the files show what exists and play shows what is real. Everloot keeps the two apart.

• Every such entry is labelled found in game files, unconfirmed. A record there does not mean the thing is, or will be, in the game.
• It is stamped with the build it came from.
• It is Blizzard's data, shown as facts, and kept apart from Everloot's own data and licence.
• Only unencrypted data is read. Encrypted content stays out.
• When players later see the same thing in game, the entry shows both: found in the files and seen in play.

Builds#

Game-file data is stamped with the build it came from, on the page and in every answer. When Blizzard ships a new build, a reviewed change records what moved in the tables Everloot reads. Forever has no live build yet, so these entries come from a pre-release build. The what changed page lists recent Blizzard posts and builds, and the MCP server gives assistants the same list as a resource, everloot://builds.

Spoilers and held-back content#

Content found only in the game files can spoil things that have not been released. It is hidden by default behind a spoiler switch. For example, a zone that looks unreleased is held back: the map draws it, dashed and labelled unconfirmed, only when you turn spoilers on. The public MCP tool leaves held-back zones out altogether.

Data age#

Answers built on player data say how old they are. The corpus API returns dataAsOf, and MCP answers end with the age of the data. The snapshot behind the corpus feed changes about every ten minutes, so check dataAsOf before you trust a number.

The full rules#

The shorter version is on How we count. The long one is the data policy. Questions players ask most are in the FAQ.