Unable to Delete a Persistent Verse Code After Publishing

[matthieuftmytb22 (Matthieu FTM)]

Summary

When publishing a map using persistent data with Verse code, it becomes impossible to delete the Verse code. If the Verse code is removed and a new version of the map is published, an error occurs, preventing the update from being completed.

I want to delete the code: rank_manager

Please select what you are reporting on:

Verse

What Type of Bug are you experiencing?

Other

Steps to Reproduce

Create a Verse code using persistent data.
Publish the map with persistent data enabled.
Try to delete the Verse code.
Publish a new version of the map.

Expected Result

It should be possible to delete the Verse code and publish a new version without any issues.

Observed Result

An error occurs when publishing a new version after deleting the Verse code, making it impossible to update the map.

Platform(s)

all

Island Code

8530-0110-2817

[locutus]

I had the same issue today when I also wanted to delete Verse files for the older rank system that I am not using anymore, because for this feature I switched to the Stat Creator Device which we got in the end of 2024. But after I deleted relevant Verse codes, it was not possible to launch edit session because of some errors, so I had to add the old Verse code again to be able to continue with my work and do an update. I really don’t know what to do with a problem like this.

[Mineblo]

@matthieuftmytb22 From Using Persistable Data in Verse | Unreal Editor for Fortnite Documentation | Epic Developer Community :

After you have published the current version of your island, if you make updates to the persistable data, any stored data from a previous version of the island must be supported in later versions of the island.

To ensure this, a backwards compatibility check is run in UEFN and a compilation failure occurs if the Verse code is no longer compatible with the currently published version. This backwards compatibility check is run whenever you:

It seems like an intentional feature rather than a bug, I would like though some feature to reset weak_maps in case of a mess up.
However someone found this possible workaround as per this thread How To Remove weak_map From Project , I haven’t personally tested it myself but according to the thread creator they were able to revert to a published version from before the persistence data was added, and then the errors were not showing up, essentially letting them re-set and re-write a new weak_map, good luck.

Alternatively if you prefer to just recover the verse code you previously used that had the layout matching the one in the published version so the error can go you can follow the steps in this other thread Help pls problem with verse - #11 by Mineblo to find the different verse codes from different versions of your map and copy it back into your project

[Bug-Reporter]

FORT-858107 has been ‘Closed’. This is working as intended by design.