Everloot: WoW Forever data

Returns cited evidence for a natural-language WoW: Forever question: observed, curated, game-file and 2023 Warcraft Wiki claims, each with source URL, licence and date. Start here for why, where or how many. Check that a claim contains the requested fact: a subject mention alone is not an answer. Observations need three agreeing installs; files stay unconfirmed with their build; archive lore may differ in Forever. If the requested fact is absent, say unrecorded rather than importing Classic or retail knowledge. For names use search_knowledge, then the hit's verified gameId with item_page, npc_page or quest_page. Further-reading URLs are search links, not fetched evidence. Disconnected observations are unrecorded, not zero.

Returns one item's dated auction history on one Forever realm: public full-scan days used by market_value, plus separate browsing sightings. Browsing prices are the median of each install's last scan that day. A day needs 3 reporters, or, while few players upload, Everloot's own installs; preserve the own-scan label and counts. Use the full realm name (CAMWOW US1 Realm 4 PvP); a unique whole-word suffix of at least two words also resolves. Ambiguous or unknown names return candidates; choose a full name before retrying. Full-scan days use the house with most units listed (ties: Alliance, Horde, Neutral), the same house as market_value structured content; browsing sightings remain a separate source, not split by house. No house selector exists; preserve the house named in the text. Use market_value for value and latest scan details, item_page for facts and vendor_page for vendor prices. Keep scan dates and corpus age; an old minimum is not a live auction offer. Missing data is unrecorded, not zero.

Lists which races can be one class in WoW: Forever, on which faction, and each race's racial traits (name, active or passive) from the game files (found in game files, unconfirmed, with the build). Narrow to one faction. Use it for whether a race can be a class, or which races a class is open to; use talent_tree for the class's talents, and population for how many play it. What each trait does is on the class page, linked from the answer.

Returns what one install still misses in one collection, against what that install uploaded as owned, grouped by source. A list row is public after 3 installs agree on the collection, the source and the item; owned is what that install uploaded. Not a Blizzard profile read and not a copied catalog. Use it for which items of a collection a player is missing; use completion_progress for achievements, reputations and titles. When that install never uploaded the collection, the answer says owned is unknown, not empty. Reads Everloot's public player data when connected. Missing or unavailable data is reported explicitly. Ask for the player's deliberately shared ownerInstallId from their own EverlootDB.installId in SavedVariables/Everloot.lua and required sharing setup; never infer or probe another owner's id.

Shows what one install's characters have finished and what is closest to done: achievements with the largest share of criteria or progress met, reputations nearest the next standing, titles known, and quests finished in a chain. A list entry is public after 3 players (installs uploading from different addresses) report it identically. Progress shows only when that install uploaded it with the collection sharing choice and a verified grant; without it the answer says so. Not a Blizzard profile read and not a copied catalog. Use it for what a player is closest to finishing; use collection_gap for missing collection items, and guild_board for a guild's kills. Reads Everloot's public player data when connected. Missing or unavailable data is reported explicitly. Ask for the player's deliberately shared ownerInstallId from their own EverlootDB.installId in SavedVariables/Everloot.lua and optional characterKey from their completion upload; never guess them or probe other players.

Counts how much of WoW: Forever's database is settled or confirmed, per zone, per type and per field, as https://everloot.app/database/coverage shows it. Coverage is settled over expected, with confirmed over expected beside it; the denominator is the larger of expected and observed, and confirmed includes settled. A player-reported fact is public after three installs agree; fields one or two installs short are counted without their values. Scoped totals and the current build's settled-list size come separately dated and measured. Only public report identifiers and game-file facts are listed, never unconfirmed values, baseline rows, names or ids, or player names. When coverage data is available, every answer states its scope, method, data date and install counts; when it is not, the answer states the scope and marks the counts, data date and installs [?], not zero. Unknown values are [?]. Without zone the answer is a summary: scoped totals, each type, and one line per zone, 20 zones at a time; detail adds per-field counts and reported entries. A page holds fewer than limit when more would pass 12000 bytes. A zone filter that matches no released zone is unmeasured (measured false, null totals), not zero. A partial answer says how many it shows of how many and gives nextOffset; pass it as offset with the same arguments for the rest. Use it for how complete the database is for a zone or type; use the page tools for the facts themselves.

Lists the Forever addons and tools in the community registry, with a board ranking: most installed, rising, most active, freshest release or best maintained. Each project shows its GitHub repository, stars, latest release, last commit, whether its .toc declares a Forever interface number, and installs from Everloot uploads (counted from 3 installs; a missing count means not counted, not zero). Projects are ranked, never people. GitHub facts carry the time they were refreshed. Use it for which Forever addons exist and how maintained they are; use everloot_plan for Everloot's own features, and recent_changes for Blizzard's posts. limit caps the projects listed.

Lists every typed relation of one entity, in both directions, grouped by relation. Player-observed relations (dropped by, sold by, reward from, located in) are listed where 3 installs agree, with the install count and last seen. Game-file relations (created by, reagent for, part of set, same icon) are found in game files, unconfirmed, with the build they came from. Ids are verified game ids from search_knowledge, a page tool, a drop row or world_map_near. For an NPC's drops use kind=npc, rel=dropped_by, direction=to; for an item's sources use kind=item, direction=from. Use it for where something comes from or what something drops, sells or rewards; use the page tools (item_page, npc_page, quest_page) for one entity's own facts, and world_map_near for what is near a place. Reads Everloot's public player data and the game-file relations of the current build.

Returns the Everloot feature catalogue: what is live, what is next, what is waiting, and which reference sites are page shapes only, as the tracker that ships with the site holds it. Use it only for questions about Everloot itself, such as whether a feature exists; it holds no game data. For game facts use search_knowledge or answer_sources; for community addons use ecosystem_projects. With no arguments it returns the whole tracker, every row with what done means, as it always has. Any argument returns a bounded page instead: a summary of the counts and each row's id, name and how far it is proven, 40 rows at a time; detail adds what done means (10 rows at a time) and status narrows to one section. A page holds fewer rows when more would pass 12000 bytes, states the tracker revision (the tracker records no date), and when partial gives nextOffset; pass it as offset with the same arguments for the rest. Needs no account.

Returns one knowledge record in full, by the string id a search result gave: title, the full text in the source's words, the URL to cite, and metadata with the source, licence and date. It is the ChatGPT connector counterpart of get_entity, which gives only an excerpt. Use it after search, or with a search_knowledge id as a string. Give field, a JSON pointer such as /questIds, to read one value of the record's data: text then holds that value as JSON, and an array comes in pages of up to 48 rows with nextOffset for the next page. A long array in a whole record is cut at 48 rows. The text block is the same JSON as a string.

Returns records matching a known exact full name, case-insensitively, optionally narrowed by kind. Use search_knowledge for partial names or when this exact lookup misses; no exact match does not mean no gameplay facts exist. Check kind, gameVersion and sourceKind before choosing: lore is archive background and has no gameId. Pass recordId (also id) to get_entity or fetch as a string; pass the separate verified gameId to item_page, npc_page, object_page or quest_page. A zone gameId, as a string, goes to world_map_near.zone. Several kinds can share a name; never guess a game id from a lore record.

Returns one knowledge record's summary, by the numeric id a search_knowledge or get_by_name hit gave: title, a short excerpt in the source's words, the URL to cite, source, licence and date. Gameplay metadata separates recordId from gameId and labels sourceKind, build or observed snapshot support. A game-file record carries its build and says when player uploads confirm it. Use it to read one hit again by its id; for the whole text, call fetch with the same id as a string. An id no record has returns a null hit, not an error. Give field, a JSON pointer such as /questIds, to read one value of the record's data instead of the excerpt; an array comes in pages of up to 48 rows, and nextOffset says where the next page starts. A pointer that leads nowhere answers with the keys it could have used, not an error. Pass only recordId here; a verified gameId from gameplay metadata goes to item_page, npc_page, object_page or quest_page. Lore archive ids are never game ids.

Returns the peak and current gold of one character and the money events its own upload recorded: income (loot, quests, vendor and auction sales) and spending (flight paths, postage, barber, respecs, auction purchases), each install's ledger kept apart. A category with nothing recorded reads as unrecorded, not zero, and gold from other gameplay is unrecorded. The gap between recorded income and peak gold is shown as unrecorded, never called bought gold or a ban. Use it for one uploaded character's own gold history; it cannot look up a character that never uploaded. Use guild_board for a guild's loot, and market_value for prices. Reads Everloot's public player data when connected. Missing or unavailable data is reported explicitly. Ask for the player's deliberately shared character and realm; it needs that owner's shared upload, not an inferred identity.

Returns one guild's published officer board and public progression. Use guild_search first for its exact name and realm; use guild_rankings to compare guilds in an instance. Roster, kills, loot, attendance and item level need 2 agreeing officers with verified grants. Public kills need 2 members' installs or an officer-published kill; sightings show characters the addon saw, not the game's roster. Characters can opt out and hidden guilds return no answer. Without an officer board, only the public part is available. Item level names how many roster members were measured, never a combined score. Names are in-game names only. Missing or disconnected data is unrecorded, not zero.

Ranks every guild with an agreed kill in one instance: by bosses killed, then by who reached its latest kill first, then by name; equal rows share a rank. A kill is a guild's once 2 of its members' installs report the same boss there, timed at the earliest report, or once its officers published it on the guild board, which carries no time. The boss list is the encounters 3 installs reported in that instance, in that order; a boss not on it counts for nothing. There is no score, no rating and no total across instances. Use it to compare guilds' progress in one raid or dungeon; use guild_board for one guild's own board, and guild_search to find a guild. Reads Everloot's public player data when connected. Missing or unavailable data is reported explicitly.

Finds the guilds whose name starts with what you typed, each with its realm, faction, how many characters the addon saw in it, and the count and date of its agreed boss kills. A guild is listed once 2 of its members' installs report the same boss, once its officers published a board, or once a character was seen in it. Guild names only, never a member's name, and a guild that asked to be hidden is left out. Characters seen are counted only when the player pages are connected; otherwise the count is unrecorded, not zero. Use it to find a guild's exact name and realm before guild_board; use guild_rankings for a ladder. Reads Everloot's public player data when connected. Missing or unavailable data is reported explicitly.

Lists item categories from the game files (found in game files, unconfirmed, with the build): class and subclass with the client's English names and slugs, slot and quality. With no arguments, the whole tree with item counts. With item, that item's category path. With class (a slug such as weapon or armor), and optionally subclass, slot and quality slugs, the item ids in it. Use it to place an item in its category or to list a category; use item_page for an item's name and stats, and entity_relations for where it comes from. Ids only: item names come from player uploads, through item_page.

Returns one Forever item's page by item id: the agreed name, drop frequency from observed loot windows, agreed map pins, and player-reported armor, block, damage per second, stats and resistances. A number is public when one value has 3 agreeing installs in the newest build that 3 installs reported, and no competing value has 3; contested numbers are withheld. Each number states its agreeing installs, build and last seen, with the corpus date and method. Missing numbers are [?] with a reason. No baseline rows or player names. Use it when you have an item id; use market_value for its price, entity_relations for what drops or sells it, and item_categories for its class and slot. Reads Everloot's public player data when connected. Missing or unavailable data is reported explicitly. If only a name is known, call search_knowledge first and use its item gameId, never recordId or a lore URL number.

Returns one item's market value, historical value, minimum buyout and units listed from uploaded full auction scans on one Forever realm. Daily values are medians of reporters' values; a day needs 3 reporters from distinct addresses, or Everloot's own installs while few players upload, labelled with counts. Market value weights public days up to 14 calendar days old toward recent days, excluding thin days (5 units or fewer) and outliers. Historical is the median over 60 calendar days, using non-thin days when present. Use the full realm name (CAMWOW US1 Realm 4 PvP), or a unique whole-word suffix of at least two words. Ambiguous or unknown names return candidates; select a full name and retry. Text lists each auction house separately; structured content uses the house with most units listed (ties: Alliance, Horde, Neutral), named in the text. No input selects a house; never blend their prices. Preserve scan dates and corpus age: the minimum is a recorded scan, not a live offer. Use auction_history for dated history and vendor_page for vendor prices. Get a verified item gameId via search_knowledge first if needed.

Returns one Forever NPC's page by NPC id: the agreed name, the agreed map pins, and the loot windows reported for it that are not yet in the drop rates. A name or pin needs 3 installs agreeing; a pin does not require a drop. No copied spawn list. Use it to name or place an NPC when you have its id, from a search_knowledge hit, a drop row or entity_relations; use vendor_page for what an NPC sells, item_page for one drop's rate, entity_relations for every typed link, and world_map_near for what stands around it. Reads Everloot's public player data when connected. Missing or unavailable data is reported explicitly. Resolve a name with search_knowledge first; use its NPC gameId, never its recordId.

Returns one game object's page (a chest, herb, ore vein or fishing pool) by its entry id: the items players looted from it, each with observed loot windows, windows with the item and distinct install reports, and where players saw it on the minimap. A frequency is public after 3 install reports; a public object with nothing in its windows reads as a measured zero. The name shows once 3 installs agree on it. Use it for gathering nodes and containers; use npc_page for creatures, and item_page for every source of one item. Reads Everloot's public player data when connected. Missing or unavailable data is reported explicitly. Resolve names with search_knowledge and pass the object gameId, never an archive recordId.

Counts observed Forever characters by race, class, faction and level band from opt-in addon census uploads, not the whole realm population. Each character counts once. Normally counts need 10 characters, 3 installs and 3 addresses, rounded to 5, with inferable small counts hidden. While few players upload, Everloot's own installs also count on their own, though the 10-character minimum still applies; preserve that label because counts can come from one player's game. The window is active in 7 days by default, or since launch. No names. Missing census data is unrecorded, not zero. Use class_races for which races can be a class; use this tool for observed counts.

Returns a Forever profession leveling route between skill levels: agreed steps, summed reagents and estimated cost, leaving uncovered ranges as gaps. A reported recipe or orange skill range needs 3 agreeing installs. Costs use median reagent prices from at least 3 distinct installs: unscoped observations without realm, build or observation time, not one listing's price or a current realm minimum. Agreed vendor prices may supply reagent costs; training is listed separately. Use recipe_thresholds for colour-change ranges. Use market_value with a verified item gameId and full realm name for a dated realm price. Missing prices stay unknown, never free.

Returns one Forever quest's page by quest id: agreed title, level, giver, turn-in and rewards. Each fact needs 3 installs agreeing. No copied quest text. Use it when you have a quest id, from a search_knowledge hit or entity_relations; use answer_sources for a question about the quest's story or chain, and entity_relations for what the quest rewards. Reads Everloot's public player data when connected. Missing or unavailable data is reported explicitly. Resolve names with search_knowledge and use the quest gameId, never recordId. For quest_chain records use get_entity with field and nextOffset to read the chain.

Returns the newest official changes for WoW: Forever, newest first: Blizzard blue posts (title, author, time, a short excerpt and the link to the original), hotfix posts, and new game builds. Excerpts only: Blizzard's post text is Blizzard's; full posts are available at their source URLs. A build's time is when Everloot first saw it, not Blizzard's release time. Use it for what Blizzard changed or posted lately; use answer_sources for lore and game facts, and ecosystem_projects for community addons. filter picks one kind; limit caps the entries.

Returns where one Forever profession's recipes turn yellow, green and grey, as skill ranges inferred from the colours players' trade-skill windows showed, never guessed exact numbers. A recipe appears only after 3 installs agree. Agreed reagents come with estimated cost per craft from unscoped median prices from at least 3 installs, or agreed vendor prices; missing prices stay unknown. Use it for how long a recipe keeps giving skill points; use profession_path for a step-by-step route between two skill levels. Narrow the list with part of a recipe name. Reads Everloot's current public corpus.

Searches the knowledge base in the shape ChatGPT connectors and deep research call by name: up to 10 results, each with an id for fetch, a title and a URL to cite. It is the same search as search_knowledge. Use it only when the client expects the search and fetch pair; other clients should call search_knowledge. The text block is the same JSON as a string.

Searches partial names, keywords or a topic across agreed gameplay names, released zones, reference catalogs (achievements, factions, titles, quest chains, mounts, legacy perks, races, instances) and the lore archive; exact-name matches rank first. Use get_by_name only for a known exact full name. Check kind, gameVersion and sourceKind: lore is historical background, not current Forever gameplay. Pass recordId (also id) to get_entity, or fetch as a string; pass a verified gameId to item_page, npc_page, object_page or quest_page. For world_map_near.zone stringify the zone gameId. Lore has no gameId; never turn an archive id or URL number into a game id. Hits carry source, licence and date, plus build or observed snapshot support where available. For achievements, factions, titles and quest chains, read generic records with get_entity and field pagination. Use answer_sources for cited evidence; search is the ChatGPT connector counterpart.

Decodes an Everloot talent share code (EL1-<class>-<spec>-<build>-<payload>, or a calculator link carrying one after #plan=) against the class's trees: the talents and ranks it holds, points per tree, the lowest level that can hold it, and every problem in plain words: a code made on another build, nodes the tree does not have, ranks cut back, points the rules would not place. Nothing is dropped silently. Use it when given a share code or a calculator link; use talent_tree to read the trees themselves. Game-file data, found in game files, unconfirmed.

Returns the WoW: Forever talent trees of one class from the game files (found in game files, unconfirmed, with the build): every node with its talents, ranks, grid position, prerequisites and row gate, plus the levels talent points arrive at. Node ids are the ids a share code names. Use it to read or explain a class's trees; use talent_plan to decode a share code against them, and class_races for which races can be the class. Narrow to one tree by name; without it the answer holds every node of every tree. With builds, the answer also lists the Everloot team's published starter builds for the class, each labelled as the team's and not observed, with its share code and page. The answer links the calculator.

Returns the goods one Forever vendor sells, by the vendor's NPC id, each with the copper price players saw. An item is listed when 3 installs agree on that item and its copper price; two agreed prices both stay listed. No copied catalog. Use it for what a vendor sells and at what price; use npc_page for where the vendor stands, entity_relations with the sold_by relation for who sells an item, and market_value for auction prices. The id is the same NPC id npc_page takes. Reads Everloot's public player data when connected. Missing or unavailable data is reported explicitly. For a vendor name, resolve its NPC gameId with search_knowledge first.

Lists the entrances, NPCs, vendors and treasures near a spot, nearest first, with straight-line distances in yards. Give a zone (name or map id) with x and y from 0 to 100, or an NPC id to start from where that NPC stands. Entrances come from the game files; one is confirmed once 3 installs zoned in from it. NPCs, vendors and treasures are player-observed and listed only where 3 installs agree on the position. Zones the files hold back as possibly unreleased are not offered. Use it for what is near a spot; use npc_page, vendor_page or entity_relations for one entity's own facts. Reads Everloot's public player data when connected.