Possible Workflow Issue on Projects with Persistence

There’s a commonly used workflow for duplicating UEFN projects that may be causing unintended issues for projects that have persistence. This workflow involves copying the Plugins folder from one project to a second project, and then modifying the second project’s .uefnproject file.

The process results in a new module on the content service for the second project. When the second project is published, it will not be backwards compatible with the published version if that published version contains any persistent vars.

It is possible to publish if the second project is reverted to a version without persistence first. Reverting will result in clearing any existing persistence data. Furthermore, the game may crash the server when played. This is being treated as a bug and our teams will fix this, but we recommend avoiding this workflow.