Reporting bugs — what to send

[XeldarAlz]

Reporting bugs — what to send

A clean bug report saves about 5 round-trips. Here's the short version.

TL;DR

For a wrong action (teleported to the wrong place, didn't accept, got stuck mid-quest): file a GitHub Issue with the bug template.

For a question about whether something is a bug at all: post in Q&A first — triage is faster there.

What goes in a good bug report

The bug template has slots for all of these, but the short list:

1. Plugin version — shown in /xlplugins next to "Auto Daily Tribes".
2. Expansion era of the affected tribe(s) — ARR / HW / SB / ShB / EW / DT. Quest dialog and turn-in flows shift between expansions, so era is a frequent root cause.
3. Specific tribe(s) affected — Loporrits, Pelupelu, whatever.
4. Where in the run did it fail? — Teleport / Accept / Play / Turn-in / Selection-UI / Allowance. The plugin's per-tribe flow is teleport → accept → play → turn-in, and each stage fails in its own way.
5. What you expected vs what happened — one sentence each.
6. Repro steps if you have them. "It happened once" is fine to report — but if you can reproduce, say so.
7. Dalamud log — open /xllog, click Open log folder at the bottom-right, attach dalamud.log. Filter by [AutoDailyTribes] to trim it.

The most useful single thing you can send

If the plugin got stuck talking to an NPC — or teleported to a location and didn't recognize the issuer — target the NPC and run:

/adt target

That dumps the targeted object's BaseId and position into chat and dalamud.log. Paste those lines into the issue. About half the "it didn't see the issuer" bugs are wrong-BaseId bugs, and that command is the fix path.

Other plugins active

Auto Daily Tribes leans on Questionable to actually play each quest, and uses vnavmesh / lifestream / Teleporter style helpers through it. If you have other plugins that touch quests, teleport, or input — Questionable, AutoRetainer, vnavmesh, RotationSolver, BossMod with auto-target on — list them in the bug report. Plugin interaction is a real source of stuck states.

What not to do

• Don't keep retrying against a broken state. If the plugin keeps re-teleporting to the same broken issuer, stop it from the main window. Re-running against the same broken state just generates more identical log lines and rarely uncovers anything new.
• Don't file security issues here. Use the private security advisory flow — see SECURITY.md for what counts.
• Don't paste 10,000 lines of dalamud.log inline. Attach the file. The bug template has a separate field for short snippets if you want to highlight the key lines.

Misclick / wrong-tribe scenarios

If the plugin accepted the wrong quests at a tribe (e.g., picked up only 2 of the 3 dailies, or chose the wrong subset), please include:

• Which tribe.
• Which quests it took vs. which were available (screenshot of the journal is fine).
• The era. The same tribe can have different available quest sets by rank — and rank-up days are a known source of selection oddities.

Thanks for the reports. Tribe-specific quest bugs are the lowest-friction way to make this work for more people than just me.