Overview
UEPluginManager is a desktop tool for browsing and managing local UE plugins. It displays project and engine plugins together, fixes garbled directory names, and moves plugins between the project and the engine Marketplace directory. Bundled engine plugins are available for browsing and state inspection only; they cannot be moved or deleted.
For actionable project and Marketplace plugins, it also supports moving, sending to the recycle bin, and correcting directory names.
Background and goals
Plugins may be installed in different project, Marketplace, or engine locations. When names conflict, enabling fails, or dependencies are unclear, inspecting one directory can miss the version actually in effect.
The work first displays plugin sources and relationships, then provides explicit actions for .uproject changes or directory organization, helping users understand the scope before changing it.
Core capabilities
Aggregating and searching sources
The tool brings together project, Marketplace, and engine plugins, supports searching by name, author, dependencies, and other information, and flags duplicate-name conflicts. It can detect installed and source-built engines.
Dependencies and state management
Users can inspect what a plugin depends on and which plugins depend on it. Enabling or disabling modifies the project’s .uproject configuration; the interface asks for confirmation when dependencies cause cascading changes.
Restore defaults removes explicit project settings so plugins return to their default states, useful when reviewing configuration left by temporary toggles.
Directory organization
Project and Marketplace plugins can move between permitted locations, be sent to the recycle bin, or have garbled directory names corrected. Opening directories and reloading the list help compare with disk state.
Bundled engine plugins are available for browsing and state assessment, not moving or deletion.
Use cases
It helps investigate why a plugin is ineffective, where a same-named plugin came from, or which dependencies an enable-state change affects. Before adjusting installation directories, users can confirm targets through source and relationship views.
Scope and limitations
Run the tool in the target UE project directory. Close the editor before moving, deleting, or correcting directories to avoid inconsistencies between an open project and disk state.
Enabled-state changes, read-only attribute handling, and directory operations affect the local project. Inspect .uproject, plugin directories, and project startup afterward.
For operation steps and parameter details, see the user guide.