Summary
Some previously published maps are currently missing a Verse path, which prevents us from submitting updates to the project.
This issue appears to affect FNC maps that were originally published before the IARC rating system was integrated into UEFN, and were never republished after IARC was introduced. As a result, the project now shows no Verse path in both FNC and UEFN.
When attempting to manually assign a new Verse path in Project Settings, the system returns the following error:
“This Verse path is not valid for project ‘Project Name’ – Reason: Cannot change the primary Verse path of project ‘Project Name’ because it has been published.”
If we attempt to submit the project without a Verse path, we receive this error:
“service.verse_path_cannot_be_changed_after_publish”
This creates a loop:
- The project does not have a Verse path.
- The system treats it as if it already has one (because it was previously published).
- The system then prevents assigning a new Verse path due to the prior publication state.
As a result, the project becomes effectively locked and cannot be updated or resubmitted.
This is a significant bug. Thousands of maps were published before the IARC update, and any of those projects that were not republished afterward are now affected. If unresolved, this could render a large number of legacy maps permanently inaccessible for updates.
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Verse
Steps to Reproduce
-
Identify a Creative 1.0 (FNC) project that was originally published before the IARC rating system was introduced, and has not been republished or updated since IARC integration.
-
Convert the project to UEFN.
3.Upon opening the project, the system prompts the following message:
“The default Verse path for this project cannot be used.
Reason: Cannot change the primary Verse path of this project because it has been published.
Please enter the project Verse path.”
Note: If you click Cancel, the project opens and can be edited normally.
-
Attempt to manually assign a new Verse path in Project Settings.
-
The system rejects the change with:
“Cannot change the primary Verse path of this project because it has been published.” -
Attempt to submit the project without assigning a Verse path.
-
The submission fails with the error:
“service.verse_path_cannot_be_changed_after_publish”
- Result:
This creates a circular validation conflict. The project does not have a valid Verse path, yet the system prevents assigning one because it has already been published. As a result, the project becomes locked and cannot be updated or resubmitted.
Expected Result
Projects originally published prior to IARC integration should remain fully updateable in both Creative 1.0 (FNC) and UEFN.
If a legacy project does not have a valid Verse path, the system should either:
- Automatically retain or generate a valid primary Verse path, or
- Allow the creator to assign a primary Verse path, even if the project has been previously published.
Legacy projects should not enter a locked state where:
- No valid Verse path exists,
- The system prevents assigning one due to prior publication,
- And submission is blocked because the Verse path is missing.
Legacy projects should remain maintainable and editable without requiring backend intervention.
Observed Result
The project does not have a valid primary Verse path in either FNC or UEFN.
When opening or converting the project, the system prompts for a Verse path but prevents assigning one because the project has already been published.
Attempting to manually set a Verse path results in the error:
“Cannot change the primary Verse path of this project because it has been published.”
Attempting to submit the project without a Verse path results in:
“service.verse_path_cannot_be_changed_after_publish”
As a result, the project enters a circular validation conflict:
- No Verse path exists.
- The system blocks assigning one due to prior publication.
- Submission is blocked due to the missing Verse path.
The project becomes effectively locked and cannot be updated in either FNC or UEFN.
Platform(s)
windows
Island Code
6608-1347-1638
