Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Publishing
Summary
Hello Developer Forum Community,
I am reaching out for assistance with a challenge I’ve encountered while working with the Unreal Engine Fortnite (UEFN) system. I mistakenly uploaded an update to my map while logged into the wrong account, which led the system to create a copy project linked to the same project folder as my original.
Now, each time I try to upload an update, it’s registered as a new project rather than updating the existing one. I want to revert to updating the original project and need guidance on how to correctly merge the projects or assign the update to the original project.
Has anyone experienced a similar issue or knows how to resolve this situation? Any advice or instructions would be greatly appreciated. I’m looking for any suggestions that would help me fix this issue so I can continue working on the original project without further complications.
Steps to Reproduce
- Begin with a standard map and proceed to edit it within the Unreal Editor.
- Upload the edited map to create Version 1, and continue this process to create further versions, such as Versions 2, 3, etc.
- Accidentally log in to the Unreal Editor using the wrong account and start working as usual.
- Upon loading the project, a warning message appears indicating you are logged into the wrong account and asks if you want to continue and create a copy. Confirm with “Yes.”
- Continue editing the map and complete your modifications.
- Publish the completed map as a Private Version.
- Discover in the Creator Portal that this action has resulted in the creation of a new project and that the Private Version has not been added to the original project.
Expected Result
The expected behavior would be that even if logged in with a different account, the system would recognize the project files’ original ownership and link the update to the correct, original project. The warning about being logged into the wrong account should offer a clear option to switch accounts or confirm ownership before proceeding. Upon publishing as a Private Version, the update should be applied to the existing original project rather than creating a new project, ensuring continuity and avoiding duplication.
Observed Result
The actual result of following the steps was that the system failed to associate the update with the original project and instead created a new project. Despite the warning about being on the wrong account, there was no option to rectify the account mismatch or to confirm the original ownership of the project files. Consequently, when the map was published as a Private Version, it was not added to the existing project. Instead, a new, separate project was created in the Creator Portal, leading to confusion and a split in project continuity.
Platform(s)
PC
Island Code
1146-2400-5172