Summary
After converting my published island from Creative 1.0 to UEFN, I can’t launch or sync the project. The Creator Portal shows the primary Verse path as “_” and I can’t change it because the island is published. Epic Support confirmed they lack the backend access to fix it.
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Creator Portal
Steps to Reproduce
- Have a published island originally made in Creative 1.0 (code 0736-1280-3933).
- Convert/import the island into UEFN.
- Click Launch Session / Play in UEFN.
- Open the Creator Portal and check the project’s primary Verse path.
- Try to assign a new Verse path in the portal.
Expected Result
UEFN syncs the project and launches. The primary Verse path should be /crc@fortnite.com/aftersevenyearss, bound to the active module 10508516-4d66-44ea-af97-ca6e891cece3.
Observed Result
UEFN blocks launch with: “Failed to sync project ‘aftersevenyearss’ with content service. Error: No project is currently associated with '/crc@fortnite.com/'".
The Creator Portal shows the primary Verse path as "/crc@fortnite.com/”. Changing it fails with: “Cannot assign new verse path to a published project”.
The Modules tab lists a legacy module (df92ea51…, 2021) and the active UEFN module.
Reverting to Creative 1.0 and converting again gives the same “_” path.
Platform(s)
pc
Island Code
0736-1280-3933
Upload an image
Additional Notes
- Epic Support (ticket #27144975) confirmed they don’t have backend access to fix this and referred me to the forums.
- This is a published island with an active player base, so I can’t recreate it under a new code without losing its stats and players.
- The issue is reproducible: reverting to Creative 1.0 and converting again produces the same “/crc@fortnite.com/_” path.
- Another creator reported the same error in the official UEFN Discord (#development-help), so this may affect other converted islands.
- The Modules tab shows two modules (a legacy one from 2021 and the active UEFN one), and I suspect the path binding is attached to the wrong module.
- Requested fix: manually clear the “_” path and bind /crc@fortnite.com/aftersevenyearss to the active module.