Exporting TMB data

Guide: How to prepare for your first raid

Open Guild > Exports to copy data for Gargul or download records for a spreadsheet or another tool. Exporting does not lock lists or record loot, and each export includes different information.

Which export should I choose?

CSV is a table format suited to spreadsheets. JSON keeps data in a structured form, useful for scripts and other tools. View opens the output in the browser; Download saves a file.

The export page also lists a legacy TMB Tooltips Addon export. TMB labels that addon unsupported.

How do I export for Gargul?

1. Find Gargul on the Exports page.
2. Open Wishlists and select the numbered lists you want.
3. Press Export.
4. On the generated page, use Click to copy.
5. Paste the result into Gargul's TMB import interface. See Gargul's import instructions for the addon steps.

The current wishlist starts selected. You can include several numbered lists. If none are selected, TMB falls back to the current list; unchecking everything does not mean “export no wishlists.”

Guild → Export Gargul opens the generated page directly with the current wishlist selected. You can change Wishlists there too; wait for the page to reload before copying the new output.

Use Click to copy for the addon. Raw shows the same data as JSON for inspection; it is not the normal addon import text.

What does the Gargul export include or leave out?

The export includes entries still needed: wishlists and prios that have not been marked received. It records character names, item ranks, whether an entry is a wishlist or prio, and off-spec flags.

Public guild item notes, free-text item Priority, and tiers are also included. Officer item notes, attendance, received-loot history, and captured raid reserves are not part of this payload. This TMB wishlist/prio export is separate from Softres.it's reservation exports.

• Multiple numbered wishlists are combined. Their original list numbers are not included in the payload.
• Group information identifies each character's main raid group. It does not preserve the separate raid-group association of each prio entry.

To update the addon later, generate and import a new export. TMB does not keep it synchronized automatically.

What should I know about the loot CSV exports?

The general loot exports include character/item details such as record type, rank or order, OS flag, public note, dates, and related item notes and tiers. The combined export also adds item-note rows that are not items received by a character. Captured raid reserves are excluded from these loot CSV exports.

Wishlist records use the guild's current wishlist number. The multiple-list selection beside Gargul does not change these CSV exports.

Archived characters are excluded from these loot rows. The exported raid-group name is the character's main group, so do not read it as proof that an assigned item or prio belongs to that group.

A received-loot export and a wishlist export answer different questions. A wishlist entry marked received is still a wishlist entry; it is not a replacement for a received-loot record. See Received loot.

How do I export reservations?

Open Reservations on Guild > Exports and choose Download CSV or Download JSON to save a file. View CSV and View JSON open the same filtered output as raw text in a new tab for copying. In that tab, use Select All and Copy (Ctrl+A, then Ctrl+C; Cmd+A/C on macOS), then paste into your destination. Both formats are displayed as plain text so CSV opens in the browser instead of forcing a download. Leave filters blank for every saved reservation in the guild, or combine them:

• Min Date / Max Date include both calendar dates, using the displayed timezone (your browser timezone, or UTC if detection is unavailable or the server cannot interpret it). Dates refer to the raid, not when the reserve was saved. Future dates are allowed.
• Raid Group matches a group attached to the raid, rather than the character's current group.
• Dungeon matches a dungeon attached to the raid, rather than the item's loot sources.
• Character includes archived characters as choices.

On a raid's detail page, Export reserves > Download CSV / Download JSON downloads all currently saved reserves for that raid using the same schema. The same menu offers View CSV and View JSON in a new tab, with identical raid scope. This shortcut supplies only the raid scope and ID, so the attendee table's Search does not affect it. The filename includes the raid ID, and a valid raid without reserves downloads an empty result. See Raid details.

On a character profile, Export reserves above Raid History downloads all currently saved reserves for that exact character, including archived or unclaimed profiles and profiles with no visible raid history. Its View CSV and View JSON options show that same character scope as copyable text in a new tab. It does not combine alts or inherit the profile table's Search, pagination, or attendance/group filters. Both formats use this same occurrence schema, with only scope=character and the character ID supplied by the shortcut; filenames include character-<character-id>. A valid profile without reserves downloads an empty result. The server reads current saved data without the profile/export cache, including reserves without a current attendee entry. Eligible profile viewers do not need edit or claim permission. For a narrower period, use the Reservations form above with that character selected. See Character profile exports.

Each record is one saved reservation occurrence. Repeated copies of the same item remain separate records with different reservation IDs. Archived and unclaimed characters, historical expansions, and future, archived, cancelled, or attendance-ignored raids are included. A character need not still be on the raid's attendee list. A valid filter with no matches downloads CSV headings or an empty JSON reservations array.

The export includes reservation, raid, character, member, and item IDs; current saved names and character class/spec; raid groups and dungeons; raid/character status; reserve order; and reservation save timestamps. Missing item definitions leave the item name blank while retaining its ID. Item names prefer the guild's current expansion definition and fall back to an available historical definition. Save timestamps are TMB timestamps, not original Softres.it import timestamps. Private notes and provider management tokens are excluded.

JSON schema version 1 includes the guild ID, normalized filters, UTC generation time, and a reservations array. CSV uses the same 23 record fields; group/dungeon ID and name lists are JSON arrays inside quoted cells. Timestamps use UTC ISO 8601. Missing values are null in JSON and blank in CSV; CSV booleans are 0 or 1. Records are ordered by reservation ID.

CSV prefixes scalar text beginning with a spreadsheet formula marker (=, +, -, or @, including after leading spaces/control characters) with an apostrophe. JSON preserves the original text. Use JSON for lossless processing; both formats preserve duplicate reservation quantities.

Reservation downloads are generated from current saved data without the shared export cache. Each file uses one consistent database snapshot, so simultaneous edits cannot mix earlier and later records within that file. It is a read-only report, not a Softres.it export or a restore/import format.

How do I export a Character Item History comparison?

Open Raids > Character Item History, choose characters and a raid window, then use Export comparison. This action is on the comparison page rather than Guild > Exports:

• Character summaries (CSV) has one row per effective selected character, with displayed-raid participation and received-reserved/other totals, plus all-history last-item and waiting figures.
• Raid and item details (CSV) has one row per character/raid/item ID from the union of reserved and received items. A pair with no items has one row with blank item fields and zero quantities. It preserves grouped quantities rather than individual reservation IDs.
• Complete comparison (JSON) contains one versioned capture with its scope, summaries, raids, cells, and referenced item names.

View character summaries (CSV), View raid and item details (CSV), and View JSON open the corresponding comparison as raw text in a new tab. Use Select All and Copy there to copy the complete result. These views use the same scope and capture rules, fields, privacy rules, and CSV text treatment as the matching downloads. If the browser blocks the new tab, allow pop-ups for TMB and choose the view again.

The scope is the selected characters that match the current Raid Group/Class/Role filters, in current sort order, against only the displayed raids for the current dungeon and page. Character-picker Search does not deselect characters. Previously loaded pages are excluded. Received/Reserved visibility, Show items/Hide items, orientation, Detailed/Compact, and expanded histories are presentation controls; both item types remain in the files. The action is disabled during raid loading or file generation and when there is no character or raid scope. If navigation fails, the previous window remains exportable after loading ends.

The details retain saved quantities for not-listed character/raid cells even though the page displays a dash there. The membership field keeps these records distinct from attendance, and their receipts reconcile with character-summary totals. Sum the item quantities, but count attendance by distinct character/raid pairs or use the summaries CSV: attendance repeats across item rows. Matching received quantities use that character's recorded reservation for the same item in the same raid; repeated reservations do not multiply awards. See Character Item History counting rules.

data_source is loaded_page_data. history_cutoff_utc is the page's browsing cutoff, not an immutable database snapshot timestamp. The initial summaries and later raid batches can reflect different save times. The export makes no additional fetch, provider request, or database change; reload the page to obtain newly saved data first. Each menu choice captures its then-current scope; JSON keeps the complete comparison in one capture. These analytical files differ from Reservations, which reads current saved reserve occurrences and can include future or cancelled raids.

The files use schema version 1, stable English headers, UTC ISO 8601 timestamps, and numeric values. Missing values are blank in CSV and null in JSON; CSV booleans use 0/1, and list fields are JSON arrays inside quoted cells. CSV scalar text beginning with =, +, -, or @ after any leading spaces/control characters gets an apostrophe prefix for spreadsheet safety; JSON preserves the original text. Known item IDs remain even if the loaded name is missing. No rendered item HTML, notes, member/account identifiers, or private wishlist/prio data is exported. Hidden attendance produces blank CSV/null JSON credit, excuse, attended-total, and raids-since-last-item values; it is never inferred from awards.

Filenames are character-item-history-summary-<guild-id>-<UTC-date>.csv, character-item-history-details-<guild-id>-<UTC-date>.csv, and character-item-history-<guild-id>-<UTC-date>.json. Generation yields between chunks and captures only the selected characters and up to 20 displayed raids, while the final file still requires browser memory proportional to its size. For the page controls and interpretation, see Exporting a comparison.

Is attendance export the same as an attendance percentage?

No. Each row records a character's credit for a raid. is_exempt indicates whether they were excused. The export does not give the final attendance percentage shown on a profile.

The export excludes cancelled raids and raids marked to ignore attendance. It also omits characters that are not linked to a member.

It can include archived raids, archived characters, and excused entries. The guild's attendance-statistics lookback window does not limit these rows. If you calculate your own percentages, account for excuses and choose the time period you mean to measure.

See Raids and attendance for how TMB records credit and absences.

What do raid-group status values mean?

The archived status describes the character, not the raid group. A character can appear in several rows because they belong to several groups. A group with no matching character can also produce a row with blank character fields.

See Raid groups for membership types.

Why does an export still show old data?

Some exports reuse a recently generated copy, called a cache. That copy may predate your changes, even if another guild member generated it.

The Exports page shows a cache-duration notice. Wait for that period to pass, then generate the export again. Refreshing repeatedly may return the same cached data. Different export types can use different cache settings; Gargul's payload and reservation downloads are generated directly.

Why might two exports contain different data?

Each export has its own purpose and scope. Your guild's privacy settings and your viewing permissions can also affect whether wishlist or prio records are included.

Do not assume an export is a copy of the table currently on screen. Page filters, display limits, archived records, and selected wishlist numbers are not handled identically by every output. Review the actual file before relying on it or sharing it.

Exports are not a complete backup with a matching restore button. An exported CSV is not necessarily suitable for the loot-assignment importer, which expects particular columns and records assigned items. See Loot assignment for that separate process.