Loot assignment

Guides: How to record loot after a raid | Loot import troubleshooting | How to correct a loot mistake

Use Loot > Assign Loot to record which characters received items, by hand or from addon CSV. Each submission creates a batch: assigned items saved together. You need permission to assign raid loot; wishlists and prios are optional.

How do I enter loot by hand?

1. Open Loot > Assign Loot.
2. Search for an item and select it.
3. Choose the character who received it. If they are missing, use New character name and the optional Class, Spec, Role, and Member fields; see missing characters.
4. Add more rows as needed.
5. Review the details and wishlist/prio options below.
6. Press Submit.

The form offers up to 150 item 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.

1. Export the loot history as CSV from your addon.
2. Open Loot > Assign Loot, then choose Import Loot From CSV.
3. Paste the CSV text, including its header row.
4. Press Load Data.
5. Read the load report and check the item rows.
6. Correct the rows, choose assignment options, and press Submit.

Load Data does not save assigned items or create characters. It replaces the item 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 within your guild, including archived characters. Matching ignores capitalization and surrounding spaces, but keeps accents: Jose and José are different names. 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?

If you have permission to assign raid loot and edit characters, you can create missing characters on Assign Loot:

1. Leave the character dropdown empty and fill in New character name. CSV imports fill this from the export.
2. Check Class if the export supplied one, or choose it yourself. You can leave it as Unknown.
3. Optionally choose Spec and Role. Spec is disabled until you choose a class, then shows that class's specs for your guild's expansion. Choosing a spec fills in Role; you can change it.
4. Optionally choose Member after Role to link the new character to someone in your guild. The list shows active, non-banned members; leave it as Unclaimed for no owner.
5. Press Submit to create the characters and save their assigned items together.

Changing or clearing Class, Spec, Role, or Member updates all rows with the same missing character name. Changing or clearing Class clears a spec that no longer fits.

TMB creates each missing character once, using the first matching row's name, class, spec, role, and member. New characters have no raid-group membership, even if you selected a group for the assigned items.

If a matching character already exists when you submit, TMB uses that record without changing its details or owner, or restoring an archived character. If several characters match, select the intended one from the dropdown. A selected character takes precedence over the new-character fields.

Without permission to edit characters, choose an existing character or ask an officer to create the missing character.

To skip an assigned item, clear the character dropdown and any New character name, then check Skip items that don't have a character. Skipped assigned items are not saved and do not create characters. This checkbox does not bypass validation errors.

A validation error prevents saving the submission. Correct the highlighted fields and submit again. New characters, assigned items, list updates, and audit entries save together.

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?

The note and date toggles show or hide those fields. Hiding a field does not clear its value.

Set default date fills every received date field, replacing 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 assigned item. Rows without an import ID can be submitted again, and TMB does not universally compare item, character, and date to decide whether an assigned item 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 assigned item.

How do I check or change a saved batch?

After submission, TMB reports added items, created characters, and failures, then opens the audit log filtered to the batch. Each new character has a creation entry in that log. Read the result before retrying any rows.

Open Assigned loot history to find 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 assigned items.

Date Assigned on the batch edit page replaces every linked item'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 received dates.

You can also use Remove beside an assigned item to remove it immediately, or Remove all above or below the list to remove the remaining assigned items after confirmation. These buttons act immediately, separately from Submit. The batch and its audit history remain, and each removal is recorded. Removing an assigned item also releases its Unique Import ID for reuse.

Removing assigned items does not restore deleted wishlist or prio entries or clear earlier received markers. To change an individual date or add loot to a different character, use the character's loot editor. See How to correct a loot mistake.

Which CSV headers does TMB recognize?

Headers are case-sensitive. Use one supported name for each field. For a custom CSV, use these names and review the loaded rows before submitting.

Recognized class names, addon class tokens such as DEATHKNIGHT, and class IDs are converted to classes supported by your guild's expansion. Unrecognized values leave Class as Unknown. CSV imports fill names and classes, not Spec, Role, or Member. These fields do not change existing characters.

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.