Packaged plugins yield different results when opening a project it was added to depending on whether the Engine was built from source code or binary

Packaged plugins that are added to projects that were made with an Engine built from source code will indicate that the plugin .dll needs to be built. If the plugin was created and packaged using a binary Engine, and the packaged plugin is then added to a different project also created in the same version of the binary Engine, the project will open normally.

4.20 Bug Scrub

Setup:

• Have a binary and source built engine at the same CL

1. Create a new Basic Code project using a binary Engine.
2. Build the project in Visual Studio.
3. Open the project in the Editor.
4. Create a new plugin in the project.
5. Package the plugin (only the plugin, not the project with the plugin included).

    <Engine_Workspace>\Engine\Build\BatchFiles\RunUAT.bat BuildPlugin -Plugin=<path_to_plugin> -Package=<path_to_output_folder>

6. Create another new Basic Code project using a Source built Engine at the same CL.
7. Build the project in Visual Studio.
8. Place the packaged plugin in the new (source-built) project.
9. Open the project in the Editor.

Original

1. Create a new Basic Code project using an Engine built from source code.
2. Build the project in Visual Studio.
3. Open the project in the Editor.
4. Create a new plugin in the project.
5. Package the plugin (only the plugin, not the project with the plugin included).
6. Create another new Basic Code project using the same Engine.
7. Build the project in Visual Studio.
8. Place the packaged plugin in the new project.
9. Open the project in the Editor.

RESULT:
A notice appears that the plugin .dll needs to be built.

EXPECTED:
The project opens in the Editor.