Since 43.00 we can’t publish an update. Verse validation fails with an “Ambiguous identifier” error in the CURRENTLY LIVE code (sys/published), not in our candidate. The candidate already fixes it, BuildAll returns no errors and the private version is created fine, but publishing keeps reporting the same file and line of the live version.
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Publishing
Steps to Reproduce
Our live version was published on 31 Oct, before 43.00. In it, HalloweenPortal/mummy_host_interface.verse has using { QuickTaskSystem } and, at line 41, Host<private>:Art.WBP_MummyHost = Art.WBP_MummyHost{}. Both HalloweenPortal and QuickTaskSystem have an Art content folder (an implicit Verse module).
In 43.00 we removed that using and moved the widgets to another folder (PortalArt). Line 41 of the new file is now a comment. BuildAll in UEFN returns no errors.
Upload a new private version and try to publish it in Creator Portal.
Expected Result
The candidate passes Verse validation and can be published, or the live version is validated with the compiler it was published with.
Observed Result
Publishing fails with the Verse validation error shown in the image below, also on candidate 9377-0335-9471?v=1, which was built from the fixed sources. The file and line it cites (sys/published/Content/HalloweenPortal/mummy_host_interface.verse, line 41) match the live version, not the candidate.
The backwards-compatibility check seems to recompile the live version with the 43.00 compiler. A published version can’t be edited, so we can’t fix this from our project. The UEFN upload log says “Verse backwards compatibility checking was disabled”, so the error only shows up on Epic’s side.
The island uses Verse persistence, so we don’t want to roll the live release back to an older version or create a new island.
Request: please let this update through, for example by not recompiling the live code with the new rules for this module.
[43.00] Publish blocked by “Ambiguous identifier” in the previously-published version (sys/published), the new candidate is clean
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Publishing
Steps to Reproduce
Live island 3007-3425-6195, published before 43.00. Its live version has a field “Notices” in money_rush_device.verse and an asset folder “MoneyRush/Notices”.
In 43.00, rename the field to “NoticesJoueurs” and the folder to “MR_Annonces”. The project compiles with no errors.
Upload a new version (candidate 9972-1862-0009?v=1) and try to publish it in the Creator Portal.
Expected Result
The new candidate passes Verse validation and can be published.
Observed Result
Publishing fails 4 times (lines 982, 985, 1350, 1352) with:
Ambiguous identifier; could be (/goratek@fortnite.com/MapTROT/money_rush_device:)Notices or (/goratek@fortnite.com/MapTROT/MoneyRush:)Notices
in file: C:/build/FortniteGame/Plugins/GameFeatures/c316d81f-858b-4e6c-9f2b-6f80b23c3362/sys/published/Content/money_rush_device.verse
The candidate no longer contains this identifier or this folder. The reported lines match the currently LIVE version, not the candidate.
Platform(s)
UEFN 43.00 (Windows), Creator Portal publishing
Island Code
3007-3425-6195
Additional Notes
The backwards-compatibility (persistence) check seems to recompile the previously-published version with the 43.00 compiler, which now treats “Notices” as ambiguous. A published version can’t be edited, so creators can’t fix this themselves. The UEFN upload log also says “Verse backwards compatibility checking was disabled”, so the error only shows up on Epic’s side.
This issue is not in the v43.00 Known Issues list. The same issue happened in 38.00 and was fixed server-side (thread: “[CRITICAL] After 38.00, it is not possible to launch the project”).
Module: c316d81f-858b-4e6c-9f2b-6f80b23c3362. We don’t want to create a new island, to keep players and their saved data.
Publishing a new version of my island fails Verse validation with an “Ambiguous identifier” error. The error cites the CURRENTLY LIVE code in sys/published, not my candidate. The new 43.00 compiler rejects a name clash in the live version. My candidate already fixes it on both sides (the local variable is renamed and the content folder is renamed), so I can’t clear the error from my project. This looks like the same issue as FORT-1160023 (live code made ambiguous by a newer compiler/API), which was fixed on Oct 19, 2026.
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Verse
Steps to Reproduce
Live island’s published Verse has a local variable LevelTags in hv_game_manager.verse (FindDevices), plus a content folder HV_Kit/LevelTags, which is an implicit Verse module brought in by using { /imbravo@fortnite.com/HussValley/HV_Kit }.
Under 43.00 that is now an ambiguous identifier (it compiled fine when it was published).
In the candidate: rename the local to FoundLevelTagFx and rename the folder to HV_Kit/HvLevelTagFx. BuildAll in UEFN returns no errors.
Upload a new private version and try to publish it in Creator Portal.
Expected Result
Validation compiles the candidate, or compiles the live version with the compiler it was published with, and the publish goes through.
Observed Result
Module caca706a-ce92-4fe4-9da2-a336b30ac9b7 in candidate link 0358-2966-9184?v=1 has error: “Ambiguous identifier; could be (/imbravo@fortnite.com/HussValley/hv_game_manager/FindDevices:)LevelTags or (/imbravo@fortnite.com/HussValley/HV_Kit:)LevelTags” in file: “C:/build/FortniteGame/Plugins/GameFeatures/caca706a-ce92-4fe4-9da2-a336b30ac9b7/sys/published/Content/hv_game_manager.verse” at line: 2652
verse_validate_publish_error
The same error and line number came back on every new candidate link, including ones made after the fix. The cited line doesn’t match the candidate’s current file.
Platform(s)
PC
Island Code
2965-8950-1846
Additional Notes
Only workaround reported on the forums (thread “Failing Verse Persistence after 38.0 for Ambiguous identifier…”) is reverting the active release to V1, which risks player persistent data. I’d rather not do that on a live island.
Request: allow this publish / skip the live-code recompile for this module, or apply the same fix as FORT-1160023.
