Installing Plugins

xPilot client plugins are optional add-ons that extend the xPilot client. These are different from the X-Plane Resources/plugins/xPilot plugin installed by the xPilot installer.

Only install plugins from developers you trust. Plugins run inside the xPilot client and are loaded when xPilot starts.

Open the Plugins Folder

Enter .plugins in the xPilot command line to open the xPilot plugins folder in your system file explorer.

If you need to open it manually, use this folder for your platform:

Platform	Plugins folder
Windows	%LOCALAPPDATA%\org.vatsim.xpilot\Plugins
macOS	~/Library/Application Support/org.vatsim.xpilot/Plugins
Linux	~/.local/share/org.vatsim.xpilot/Plugins

Install a Plugin

Close xPilot before copying plugin files.

Most plugins come as a folder named after the plugin, such as MyXpilotPlugin, containing the plugin .dll and any files it needs. Copy that whole folder into the xPilot Plugins folder so you end up with Plugins/MyXpilotPlugin/MyXpilotPlugin.dll. Follow the plugin author’s instructions if they differ. Plugins that come as a single loose .dll can be copied straight into the Plugins folder.

Start xPilot again after the files are in place. xPilot only loads client plugins during startup, so restart xPilot to add, update, or remove a plugin.

Each plugin keeps its own copy of the libraries it needs, so two plugins won’t conflict with each other. A plugin that misbehaves is logged and skipped, but plugins run inside xPilot, so only install plugins from developers you trust.

Troubleshooting

If a plugin does not load, confirm that:

• The files were copied into the xPilot client Plugins folder, not the X-Plane Resources/plugins/xPilot folder.
• Each plugin is in its own folder, and the main .dll has the same name as that folder (for example Plugins/MyXpilotPlugin/MyXpilotPlugin.dll).
• xPilot was restarted after the files were copied.
• You copied every file included with the plugin, including any dependency .dll files.

If the plugin still does not load, open the xPilot logs with the .logs command and check for plugin loading errors. Each plugin that loads successfully is logged as Plugin loaded, and failures are logged with the reason.

For Developers

If you’re a developer looking to build your own xPilot plugins, see the Creating Plugins guide.