Verse peristable data not backward compatible after V38.00

General Issues and Bug Reporting
, , ,
1

Summary

I can’t publish a new version of my map because verse persistable is not backward compatible(that happened only after v38)

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Publishing

Steps to Reproduce

go to creator portal, create release and see the verse peristence row

Expected Result

publish the version

Observed Result

can’t publish the version because verse persistable data is not backward compatible

Platform(s)

PC

Upload an image

bigprog.PNG
bigprog.PNG666×463 51.5 KB

VerseFailed.PNG
VerseFailed.PNG814×502 59.8 KB

2

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

3

It seems to be a problem with “updating” staged files. I deleted a verse file and modified another, but these changes do not appear in the staged files on the content service (the deleted verse file is still there).

4

me too.

5

Hi,

This is about the word which was changed to a reserved word in the 38.00 result

Ambiguous identifier;

could be (/yngmost3r@fortnite.com/Fortnite_Rewind/enchman_manager/

OnGuardEliminated:)result
or
(/Verse.org/Verse:)result

In another thread, the poster proved this was NOT a Verse peristable data problem.

This is a problem related to a reserved word, result, in the 38.00

See the thread which has some posters workarounds

Verse compiles but fails validation - General / Issues and Bug Reporting - Epic Developer Community Forums

See Known Problems

Fortnite Ecosystem 38.00 Known Issues Thread - Creators to update their scripts to avoid the use of word result