📦 Quartermaster — the loot bot

Reads your loot channels so every drop lands in the desktop Loot Tracker.

In Discord

The Quartermaster is the quietest bot in the estate. It has no commands, it never posts, and most people never notice it is there. Its whole job is to read the loot channels and remember what dropped, so that the SWG Loot Tracker in the desktop app can tell you what a heroic actually drops and how long it has been since anyone saw the thing you want.

Note: The Quartermaster only ever reads. It will not post, react, DM you, or reply. If something in a loot channel is talking to you, it is not this bot.

What it reads

It watches the loot channels the server has pointed it at, and it recognises two kinds of message:

Source	What it takes
Nae's Loot Picker and RNGenie distribution posts	Every item line from the distribution, plus who received it.
Kith LFG run debriefs	The loot recorded on a run when it reaches Debrief.

For LFG runs it deliberately reads only the debrief message, not the individual roll cards. Those describe the same drops, and counting both would double every item in your statistics.

Someone posts loot→Quartermaster reads it→Inbox file→Loot Tracker in the app

What you have to do

Almost nothing. That is the point.

Run a heroic and distribute loot the way you already do, with the loot picker or through an LFG run.
Post it in the loot channel the way you already do.
Open SWG Loot Tracker in the Kith Workshop and click Refresh.
The drop is there — item, source, date, and who got it.

Tip: You do not need to be in a run for its loot to count. The Quartermaster reads the whole channel, so the tracker's "how long since this dropped" answers are drawn from the entire community's runs, not just yours.

Why the drop you posted is not showing up

Work down this list — it is almost always one of the first two.

Symptom	Cause and fix
Nothing new since you last looked	You have not pulled it in yet. Click Refresh in the Loot Tracker; the bot writes to an inbox, the app reads it on demand.
One channel's loot never appears	That channel is not on the watch list. Ask an admin to add it.
An older run is missing	It fell outside the backfill window. The bot backfills a limited number of days when it starts — by default a week.
Very old drops vanished	Expected. The inbox has a retention window, by default about three weeks. Anything the tracker has already ingested stays in the app.
A hand-typed loot message was ignored	It only parses the loot-picker and RNGenie formats and LFG debriefs. Free-text "we got X" messages are not read.
The item name looks wrong	The tracker matches names against the real Restoration item list. Report it — see below.

Getting the most out of it

Post loot in the loot channel, not in the run thread. Thread chatter is not read; the channel is.
Let the loot picker format it. A pasted screenshot of loot cannot be read — it needs the text post.
Use LFG debriefs for heroic runs. Recording loot on the run gives the tracker the instance, the date and the group in one go, which hand-posting cannot.
Do not delete and repost. Deleting a message does not remove what has already been read, and reposting can create a duplicate.

Tip: The value compounds. A single run's loot is not interesting; a season of the whole community's runs is what lets the Loot Tracker tell you that nobody has seen a particular drop in six weeks.

For server admins

The Quartermaster is configured from a local management dashboard rather than from Discord, so there are no admin commands to learn. From it you can:

Setting	What it controls
Servers and channels	Which loot channels are watched. One bot covers many channels.
Backfill days	How far back it reads when it starts up. Default 7.
Retention days	How long captured lines stay in the inbox. Default 21.

Admin only: The dashboard is bound to the loopback interface on the machine the bot runs on — it is not reachable from the internet, by design. See the estate runbooks for how to reach it.

Reporting a problem

If a drop was parsed wrong — wrong item, wrong recipient, counted twice — report it with the message link and what it should have said. The parser is regularly corrected against real posts, and a concrete example is what makes that possible. See Reporting a Bug.

← PreviousWayfinder — the LFG bot Next →Lamplighter — the bug bot