Summary
Trying to package a Plugin i updated in my Plugin_project, where the Plugin is in the ProjectFolder itself.
But Packaging also includes the EngineFolder Plugin (which i installed for my other projects), which breaks the packaged plugin.
What type of bug are you experiencing?
Plugins
Steps to Reproduce
- I installed my Dialog Plugin via Epic games Launcher to 5.7.
- I also have the DIalog Plugin in “Plugin_Project/Plugins/here”.
- I open Plugins-Project with updates in the sourcecode of the PluginFolder Dialog Plugin version.
- Packaging the Plugin from Plugins Panel/project/Dialog Backend
- The package now also contains the old files from the EngineFolder
Conclusion:
Packaging Plugin does not count ProjectFolder Plugins with higher Priority than EngineFolder ones.
Had to deinstall Engine Plugin > Package > Reinstall Engine Plugin
Expected Result
ProjectFolder Plugins, even when packaging, should count on higher Prio, ignoring Engine version!
Observed Result
Packaging Plugin does not count ProjectFolder Plugins with higher Priority than EngineFolder ones.
My Plugin update got not approved on Fab because it does not include the updated variables and links..
After deinstalling the EngineFolder Plugin and packaging the Prpjectafolder one, it got accepted on Fab without any changes to the code - suddenly it has all necessary variables and links, which were only missing in the outdated EngineFolder one.
Platform
PC
Operating System
Windows 11 (64Bit)
Running UE 5.7.2
Additional Notes
Found out through publishing update of my Plugin, receiving big error message via Mail from Fab support, about missing variables and links.. which are clearly inside the NEW Plugin i tried to package, but not inside the old Engine version one.