Can't publish any update since 43.00 – Verse validation fails on the currently live release (sys/published, Ambiguous identifier)

[raxiyai]

Summary

Since 43.00 every new private version of my island fails Verse validation on publish (verse_validate_publish_error). The error comes from VipShop.verse of the currently live release (sys/published), not from the uploaded code, so no update can be published.

Please select what you are reporting on:

Verse

What Type of Bug are you experiencing?

Publishing

Steps to Reproduce

1. My island 3727-5000-7711 has a live release that was built and published with 43.00 (01.11.2026, 19:55 CET). In that release, the VIP shop code (VipShop.verse) uses the RankSystem module and refers to a “Textures” folder. Both the VIP folder and the RankSystem folder contain a folder named “Textures”. Since 43.00 makes asset folders visible across the whole project, “Textures” is now ambiguous in that code.
2. Fix the conflict in the project (I moved the VIP textures to a uniquely named folder and updated the code), then upload a new private version from UEFN 43.00 (++Fortnite+Release-43.00-CL-59596594). The project builds in UEFN with no Verse errors.
3. In Creator Portal, try to publish the new private version. Verse validation fails with an error from the live release’s VipShop.verse (sys/published), not from the uploaded files.

Expected Result

The new private version passes Verse validation and can be published. It builds without errors and the name conflict is fixed in it.

Observed Result

Verse validation fails with: Ambiguous identifier; could be (/blejzs@fortnite.com/InfinityZoneWars/RankSystem:)Textures or (/blejzs@fortnite.com/InfinityZoneWars/VIP:)Textures in .../9d3f604e-71ed-4582-a203-a8eb7430f5be/sys/published/Content/VIP/VipShop.verse at lines 25, 34, 42, 51 (verse_validate_publish_error).

The validation checks the file of the live release, not the uploaded one:

• In one of my new versions, line 25 of VipShop.verse doesn’t contain “Textures” at all, but the error still points to line 25.
• Publishing an older private version fails with the exact same error.

I tried 6 different private versions, all with the same result (codes available on request).

Cause: the 43.00 change that made Verse modules with reflected assets accessible project-wide.

The live release passed this same validation when I published it on 01.11 (the release before it was built before 43.00). Since it became the live release, every update is rejected, and I can’t replace it, because publishing is exactly what’s blocked.

Platform(s)

Windows (PC), UEFN 43.00

Island Code

3727-5000-7711

Additional Notes

The island has active in-island transactions (VIP offers) and all updates are blocked, including a scheduled event. Module: 9d3f604e-71ed-4582-a203-a8eb7430f5be. Verse path: /blejzs@fortnite.com/InfinityZoneWars. This looks similar to FORT-1011852 (38.00, fixed in 39.00). Please fix the validation of the published release or unblock publishing for this island.

[Bug-Reporter]

FORT-1186328 has been created and its status is ‘Unconfirmed’. This is now in a queue to be reproduced and confirmed.

[Jimbohalo10]

hi @raxiyai

Please can you try clearing remote source as in picture

[giovauefn]

@Jimbohalo10 I’m pretty sure that clears the cache for edit session, but is unrelated to the Verse Validation in the portal. I’m having the same issue, and it’s the same as exactly 1 year ago ([CRITICAL] Cannot update my map with private versions made after 38.00).
From my understanding (and sadly, experience with this) it looks like the backend check uses an old/cached version of the module instead of the current one. Still a weird issue, as the error that comes there is never even listed in edit session/while compiling Verse. Who knows lol.

[raxiyai]

sadly it didnt fix my issue ;/