Getting help & reporting problems

Stuck, found a bug, or missing a feature? Two doors, both watched:

• Discord — discord.gg/j6hnJBFtXE — ask in #help; usually the fastest way to get unstuck. Share feature ideas in #feature-requests.
• GitHub — Issues — best for reproducible bugs and feature requests; the templates walk you through what to include.

The difference between a five-minute fix and a week of guessing is almost always the same four things:

1. Version — shown in Settings → Maintenance → Updates ("Current build").
2. Environment — OS, and whether you run API-only, full local, or Docker.
3. What you did → what you expected → what happened — three short lines beat three paragraphs.
4. The log — the last lines of the server log usually name the real error. Settings → Maintenance → 🪵 Server log → Copy all.

The diagnostic report button below assembles all of that in one click: version, OS, capability status, non-secret settings and the last log lines — formatted, copied to your clipboard, ready to paste into Discord or a GitHub issue.

What it deliberately never includes: your API keys or tokens (only whether each one is set) and your folder paths (only whether each one is configured). One caveat: the log tail can mention file names from your machine — skim the paste before posting if that matters to you.

Describe the job you were doing when you missed the feature — the problem is more valuable than the proposed solution. Post it in Discord #feature-requests or open a GitHub issue with the Feature request template.

LoRA Dataset Studio is built in the open, and the version you have stays free and keeps working. New LDS versions reach Patreon members (LDS Member) first, then everyone; exclusive plugins stay members-only.

Connect Patreon under Plugins → Purchases. Members-only plugins then install from the Store like any other plugin, and new LDS versions appear under Settings → Maintenance → Updates. Members-only plugins and the online Library require an active connected membership. Disconnecting locks them immediately; your installed files and data are kept. Public plugins and the installed LDS core remain usable. You can also support development through GitHub Sponsors; it does not include the Patreon membership benefits.

The small Patreon announcement on the datasets page can be dismissed. These links remain available through Help & guide → Support LDS. The best free ways to help are just as welcome: report bugs, share ideas on Discord, and star the repo.