Is this safe to use? — Safety, ToS, and what the plugin does

[XeldarAlz]

Is this safe to use? — Safety, ToS, and what the plugin does

Short answer: Auto Daily Tribes automates quest acceptance and play. That's against Square Enix's Terms of Service. Use at your own risk.

Long answer below — please read before turning it on.

What the plugin actually does

When you tick a tribe and press Run selected:

1. The plugin switches to a configured DoH / DoL / DoW-DoM job (if not already on one — see /adt config).
2. It teleports to the tribe's issuer.
3. It accepts the day's allowance of quests by walking the NPC dialog.
4. It hands each accepted quest off to Questionable, which plays the quest through (move, interact, fight, gather, craft, dialog).
5. It turns the quest in and moves to the next selected tribe.

This is automated input. The plugin sends simulated input to NPC dialogs and the journal, drives your character through quest objectives via Questionable, and walks turn-in flows. It's a quest automator. There is no "passive" or "hint-only" mode — it's all or nothing.

ToS

Square Enix's Terms of Service prohibit third-party automation of gameplay. Auto Daily Tribes does that by design — automating the daily allied-tribe loop is the whole feature. Turning it on is your choice.

Realistic risk: I'm not aware of anyone being actioned for using this plugin specifically. That's not the same as "it's safe." Quest automation is detectable in principle if anyone bothers to look — same as any input-automation tool.

If you're not comfortable with that trade-off, don't use this plugin. There is no middle ground here; it's an automator.

What the plugin does not do

• No network calls. The plugin reads game memory, draws a window, dispatches input into the local game process, and calls into Questionable via Dalamud IPC. That's it. Any outgoing traffic from this plugin would be a bug — and a security issue (see SECURITY.md).
• No persistence beyond config. Settings live in pluginConfigs/AutoDailyTribes/. The plugin remembers your tribe selection across reloads but doesn't write anything else durable.
• No reading of chat, party, or unrelated UI. It reads tribe state from the relevant addons (reputation, rank, allowance) and the journal — nothing more.
• No interaction with other plugins beyond the documented IPC into Questionable for quest execution.

Dependencies

Auto Daily Tribes is a scheduler / dispatcher. The actual quest play comes from Questionable — without it installed and enabled, the plugin can't play the quests it accepts. The Dependencies window (/adt deps) lists everything that has to be present and the install status of each. If something is missing, the main window grays out the affected tribes with a tooltip telling you what's needed.

"Will it get me banned?"

I can't promise that and neither can anyone else. Honest framing:

• Auto Daily Tribes is in the same risk bucket as gathering bots and combat rotation automators — third-party tools that drive gameplay actions on your behalf.
• That's a step deeper than the Hints-overlay / read-only-meter / map-pin-tracker tools that make up most of the Dalamud ecosystem.

If you want zero risk, don't use third-party tools at all. If you're already running gathering or rotation automation, this is in the same bucket. If you're only running read-only Dalamud plugins today, this is a bigger step than what you've already accepted — make it deliberately.

Common mitigations people use: alt characters, off-peak hours, supervised runs rather than overnight grinds. None of these make it safe; they just narrow the surface.

Source is open

This is AGPL-3.0-or-later. Read the code, build it yourself, audit what the plugin does. If you don't trust the prebuilt zip from the custom repo, building from source is the workaround — see CONTRIBUTING.md.

Questions

Reply on this discussion — happy to clarify anything. If you find behavior that doesn't match what's documented above, that's a bug; please report it.