Loot assignment
On this page
Summary
Open Loot → Assign Loot to record which characters received items. Enter awards by hand or load addon CSV, check the rows and list-update options, then press Submit. Loading CSV only fills the form; submitting saves the awards and can also remove or mark matching wishlist and prio entries.
How do I enter awards by hand?
Each submission creates a batch: a group of awards saved together. You need permission to assign raid loot to use this page. You do not need wishlists or prios to record loot.
- Open Loot → Assign Loot.
- Search for an item and select it.
- Choose the character who received it.
- Add more rows as needed.
- Review the details and wishlist/prio options below.
- Press Submit.
The form offers up to 150 award rows. Use the row's remove control to clear an unwanted item and recipient. If you reuse a cleared row, check its date too.
The raid-group filter beside the recipient controls narrows the character picker. It does not set the assignment's saved Raid Group.
How do I import addon loot history?
TMB's importer supports fields used by Gargul, RCLootCouncil, and LootReserve. Before relying on an export, check that your addon is set up and being used correctly so it actually records the loot you want to save.
- Export the loot history as CSV from your addon.
- Open Assign Loot → Import Loot From CSV.
- Paste the CSV text, including its header row.
- Press Load Data.
- Read the load report and check the award rows.
- Correct the rows, choose assignment options, and press Submit.
Load Data does not save awards. It replaces the award rows already in the form, including unsaved manual entries. Loading another CSV starts over rather than adding to those rows.
The load report shows loaded and skipped rows, off-spec flags, missing character names, and parsing errors. The importer examines only the first 150 source rows, even when some of those rows are skipped. Split a larger export into smaller parts, each with its header row.
What should I check after loading?
Check the item, recipient, date, OS flag, and notes on every row.
Characters are matched by name without regard to capitalization. For the CSV field player, TMB removes the realm suffix from names such as Sam-Realm. Other supported name fields do not strip that suffix. Check the selected character rather than assuming the match is right.
Automatic item loading needs an item ID. An item name alone is not enough. Correct a missing or incorrect item using the item picker.
TMB can infer off-spec from supported export fields and some note or response text. Check the OS checkbox after import. Imported public and officer notes are limited to 140 characters each; officer notes can combine votes, responses, and other notes from the export.
What if a character is missing?
Choose the correct existing character, or add the missing character to TMB before recording their award. See Members and characters.
You can check Skip items that don't have a character to submit the other awards. Skipped awards are not saved, and missing characters do not become temporary guests.
The importer also skips recognized disenchant and vendor rows. These do not become a separate disenchant or vendor history in TMB.
Which details can I set?
| Detail | What it does |
|---|---|
| OS | Marks this award as off-spec. Leave it unchecked for main-spec. |
| Public note | Adds a short note to the award, up to 140 characters. |
| Officer note | Adds a separate note for authorized viewers, up to 140 characters. |
| Award date | Records when the character received the item. A blank date uses the submission time. |
| Assignment name | Names the batch, such as “Week 1 MC clear.” Without a name, it uses Batch followed by its ID. |
| Raid | Links the awards to a particular raid event. Optional. |
| Raid Group | Links the awards to a regular raid team. Optional and separate from the recipient filter. |
The note and date toggles show or hide those fields. Hiding a field does not clear its value.
Changing the default date fills all award date fields with that date, overwriting dates already in the form. Review dates after using it.
What happens to wishlists and prios?
The two deletion checkboxes are independent:
- Delete assigned items from each character's wishlist: remove matching wishlist entries. If unchecked, keep them marked received.
- Delete assigned items from each character's prio list: remove a matching prio. If unchecked, keep it marked received.
These start from the guild's defaults. Leaving them unchecked means “mark received,” not “leave the lists untouched.”
Wishlist matching can include linked tokens and rewards and can affect one matching entry in each numbered list. Prio matching affects one matching entry, even if the character has the item prio'd in several raid groups. The selected batch group does not restrict that search to its own prios.
Some items, such as certain legendary fragments, require manual updates. Check the result and audit entries. See Wishlists and Prios for list behavior.
Will TMB stop duplicate imports?
Some exports supply an id that TMB turns into a Unique Import ID. TMB checks submitted import IDs against saved records and reports an error when an ID already exists.
This does not catch every duplicate award. Rows without an import ID can be submitted again, and TMB does not universally compare item, character, and date to decide whether an award is a duplicate.
The error allows you to change or remove the ID for an intentional resubmission. Check the existing history first: doing this can create another copy of the award.
How do I check or change a saved batch?
After submission, TMB reports added items and failures, then opens the audit log filtered to the batch. Read the result before retrying any rows.
The assignment history lists saved batches. Select edit beside the batch to open its details, change its name, raid, or raid group, then press Submit. Changes to raid and group apply to its linked awards.
Date Assigned on the batch edit page replaces every linked award's received date and the batch's own date. Leave it blank to keep the dates. History date filters use the batch date, which may differ from individual award dates.
The batch editor changes shared details. To correct or remove an individual award, use the character's loot editor. Removing an award does not restore deleted wishlist or prio entries or clear earlier received markers. See Received loot.
Which CSV headers does TMB recognize?
Headers are case-sensitive. Use one supported name for each field. These are the parser's accepted fields, not a promise that every CSV export will load correctly.
| Data | Supported headers |
|---|---|
| Character | player, character, name, Winner |
| Item ID | itemID, item_id, Item ID |
| Item name | item, itemName, item_name, Item Name |
| Date | date, dateTime, date_time, Time |
| Public note | publicNote, public_note, Reason |
| Officer note | officerNote, officer_note; combined with note, votes, and response when present |
| Off-spec | offspec; some note and response values can also set OS |
| Import identifier | id |
| Disenchant/vendor indicators | response, Disenchanted, Reason |
The Time field is read as a Unix timestamp in seconds. The importer can also derive a date from id. Check the loaded dates, especially when using a custom CSV format.