Roadmap & how to contribute

[XeldarAlz]

Roadmap & how to contribute

End goal: full hands-off automation of every Allied Tribe from ARR through Dawntrail, across every job your character can play, with the user only ticking which tribes to run today.

Below is the live state. The canonical version is the README; this post mirrors it for discussion.

Shipped

• Every Allied Tribe from ARR through Dawntrail listed in one window — Amalj'aa, Sylphs, Kobolds, Sahagin, Ixal, Vanu Vanu, Vath, Moogles, Kojin, Ananta, Namazu, Pixie, Dwarves, Qitari, Loporrits, Omicron, Arkasodara, Pelupelu, Mamool Ja, Yok Huy.
• Per-tribe state readout: rank, reputation bar, daily allowance pill.
• Era-grouped sections (newest first), tribe-specific icons.
• Locked tribes greyed out with hover tooltips explaining the unlock.
• Click cards to select; Run selected automates the picks back-to-back.
• Cancellable mid-run; selection persists across reloads.
• Per-discipline job preference: Crafter, Gatherer, and Combat — Specific / Current / Highest-XP / Lowest-XP modes. (Combat was added in v1.0.0.2.)
• /adt target debug helper to dump a targeted NPC's BaseId when a tribe doesn't recognize its issuer.

In progress

Nothing actively in flight. The recent v1.0.0.2 release fixed the Run selected queue (only the first and last of N selected tribes were actually running) and added Combat job auto-switching.

What's next

Open. The next batch of features will come from the Ideas category — if there's something you want, post it there with the rationale and trade-offs (see the feature request guidelines). 👍 on an Idea post is the single most useful signal for prioritization.

How to help

This is a solo project. The biggest force multipliers, ordered by impact-per-minute:

If you don't write code

1. Report tribe-specific quest bugs. Pick a tribe that's misbehaving, attach a dalamud.log showing the plugin's actions vs. what should have happened, and a fix is usually a small change. See the Reporting bugs post.
2. Run /adt target when the plugin doesn't recognize an issuer, and paste the BaseId into an issue. Half of "didn't see the NPC" reports become one-line fixes once we have the right BaseId.
3. Test rank-up days. The day you cross a rank threshold is when tribes' available quest sets shift, and is also when subtle selection bugs surface.

If you do write code

1. Read CONTRIBUTING.md — covers build, project layout, PR norms.
2. Look at issues labeled good first issue. Tribe-specific quest fixes are usually the lowest-friction starting point.
3. Keep logic small and direct. This plugin has one job. No heavy abstractions "for later."

Build & test

git clone --recurse-submodules https://github.com/XeldarAlz/FFXIV-AutoDailyTribes.git
cd FFXIV-AutoDailyTribes
dotnet build AutoDailyTribes.sln -c Release

CI rejects PRs that don't build, so build locally first. There's no test suite to speak of yet — testing is in-game against the tribes you touched.

What I'm not planning to add

• Telemetry that phones home. The plugin makes no network calls by design.
• Anything outside the daily-tribe loop. Hunts, MSQ, hunt logs, treasure maps — out of scope. The line is "daily allied-tribe quests"; anything outside it should go in a different plugin.
• Stealth / anti-detection features. Auto Daily Tribes is what it is — an automator. If you want it discreet beyond running it on alts off-hours, this isn't the plugin for that.

Questions on direction or priority? Reply here.