Dalamud test-build guide
How to install experimental plugins in Dalamud safely: enable plugin testing builds from the launcher settings, then install the listing through the in-game plugin window. Do not download a random DLL or paste an unknown repository URL just because a search result calls it experimental.
Start XIVLauncher and enter /xlsettings in FFXIV chat. Open the Experimental section, enable the option that retrieves plugin testing builds, save the change, and reopen /xlplugins. The test-build listing should then appear beside the normal plugin listings when a developer has published one.
This setting changes which builds Dalamud can show; it does not make a plugin official, risk-free, or compatible with every FFXIV patch. Treat the option as a controlled test path, not as a replacement for the official plugin directory.
Concept image
The important distinction is between the launcher, Dalamud, and a plugin build. XIVLauncher starts the supported FFXIV flow; Dalamud provides the plugin framework; the plugin author decides whether a build is normal, testing, or distributed through a separate repository.
If your goal is simply to find a normal plugin, use the regular plugin window first. This guide is for the narrower case where an author or official support discussion tells you that the testing-build switch is required.
| What you mean | Best route | What to watch |
|---|---|---|
| Normal plugin | Search in /xlplugins | Use the current listing and read the author notes. |
| Experimental or testing build | Enable plugin testing builds in /xlsettings | Expect bugs, missing features, and breakage after a patch. |
| Custom repository | Use the developer's documented repository instructions | Verify ownership and never paste an unknown URL. |
| Local development build | Follow Dalamud developer documentation | This is a development workflow, not a shortcut for players. |
Check the reason first. A test build may exist because the author is validating a fix, supporting a new FFXIV patch, or asking for a small group of testers. If the only instruction you found is a download link from an unknown mirror, stop and verify the project's owner before doing anything.
Use one change at a time. Write down the plugin name, the build channel you enabled, and the symptom you are testing. That simple record makes it much easier to disable the right thing later and prevents a broad reinstall from hiding the real cause.
Keep the normal recovery path available. Know how to reopen /xlsettings, disable the testing-build option, open /xlplugins, and remove or disable the plugin. Do not delete random FFXIV folders while the actual problem is still unidentified.
Controlled rollout
A good test has a narrow question: does this build fix the reported issue, work with the current patch, or restore one specific feature? It should not become an excuse to enable every experimental source at once.
After installing, play normally for a short session. Watch for launcher startup failures, missing UI, repeated errors, sudden performance changes, or a plugin that disappears after a game update. Record the first symptom rather than guessing which file to delete.
The testing-build switch and a custom repository solve different problems. A testing-build option changes which builds Dalamud can retrieve from its supported plugin flow. A custom repository adds another source maintained by a developer or community project. A local development build is different again: it is intended for people building and debugging plugins.
If a guide tells you to add a repository, verify that the URL comes from the plugin author's current documentation or repository. Check the owner, project status, and what the repository actually publishes. A search snippet, a copied Discord message, or a random file-hosting page is not enough evidence.
Do not present a custom repository as official Dalamud infrastructure. The page's safest recommendation is to start with the official directory and use a separate source only when the author clearly documents why it is needed.
Use this short check before and after the first test.
First check whether Dalamud finished loading and whether the game has just received a patch. Plugin availability can change during a maintenance window or while an author updates a build. A missing listing is not proof that a download mirror is required.
If the setting is visible but the plugin is not listed, return to the author's current documentation and confirm the exact name, supported game version, and source. If the setting itself is absent, use the official troubleshooting route instead of copying an old configuration file from a forum.
For Steam Deck or desktop Linux, keep the platform boundary in mind: use the site's Steam Deck/Linux guide for launcher setup, then apply the same Dalamud testing-build logic only after the normal plugin flow is working.
Recovery path
If FFXIV or Dalamud becomes unstable, disable the last experimental plugin and turn off the testing-build option if you no longer need it. Reopen the normal plugin window and test the game without adding another variable.
If the issue remains, separate launcher, game-client, patch, and plugin symptoms. The existing troubleshooting guides cover crashes, boot-version checks, and patch-file failures; use the page that matches the first failing checkpoint instead of treating every problem as a plugin problem.
Experimental or third-party plugins are not made official or risk-free by appearing in a testing list. Square Enix rules, account enforcement, and the behavior of a plugin are separate questions. Avoid plugins that automate actions, expose account data, or ask you to bypass normal security controls, and make your own informed decision before use.
This guide explains the supported settings path and safe troubleshooting habits. It does not guarantee that any plugin is allowed, stable, private, or compatible with a particular patch.
No. A testing-build option changes which builds the supported plugin flow can show; a custom repository adds a separate source. Verify each source independently and do not describe a custom repository as official Dalamud infrastructure.
Open /xlsettings after Dalamud loads and look for the Experimental section or the setting that retrieves plugin testing builds. Labels can change, so use the current UI explanation rather than an old screenshot.
A standalone DLL is not the safe default. Prefer the current plugin flow and the author's documented source. Do not run a file from an unknown mirror just because it has the right name.
The author may have withdrawn the build, the plugin may not support the current FFXIV patch, or Dalamud may not have refreshed. Check the current official or author-maintained documentation before changing files.
Disable the testing-build option in /xlsettings, save, then use /xlplugins to disable or remove the test plugin. Test the normal launcher flow before adding another plugin.
No. It only changes the build channel that can be displayed. Stability, privacy, account risk, and Terms of Service questions still require separate judgment.