UEFN can not publish finished game

General Issues and Bug Reporting
, , ,
1

Summary

Unable to publish game because of persistence issues; however, there’s no live/published version of the game yet (just a reviewed version)

Please select what you are reporting on:

Creative

What Type of Bug are you experiencing?

Assets

Steps to Reproduce

Hi,

I’ve created a UEFN project (Grow the Farm), which I wanted to publish. However, when I go to publish the project, I get a verse persistence incompatibility error. However, I have no live/published version of the project yet. So I don’t understand why I get a compatibility error.

I did submit a previous version for review, but it’s not published.

Is it possible to remove the existing reviewed version of the project so I can submit the new version? Reviewed version’s game code:
3772-8406-0284
, the one I want to publish is:
4088-3144-3912
. If possible, please don’t publish any versions. I’d like to control the timing when it goes live.

Error message when trying to publish:

VerseBuild: Error: C:/build/FortniteGame/Plugins/GameFeatures/0745b712-4dfc-26f0-9121-bdab6ebec0c0/Content/Components/player_persistence_system.verse(168,43, 173,2): Script error 3643: Missing definition in source package that corresponds to published definition (/zloppygames@fortnite.com/GrowTheFarm/Components/player_persistence_data_plants:)PlantDataRegion2. errors.com.epicgames.cookplugin.versebuildscripterror

Expected Result

Being able to publish the project - There’s no published/live version yet.

Observed Result

Unable to publish

Platform(s)

PC

Island Code

7145-1181-9075

Upload an image

brave_0zGQpHWwnm.png
brave_0zGQpHWwnm.png803×498 50.3 KB

2

There is something you need to do to fix this, but I don’t know how, there are a few posts that can help here and show you what to do, try a few different keywords if you can’t find them straight away.

The first version of the game you published, made it’s island code, the public island code that will not change.

Private version map codes, are only private version codes and on a successful publish will use the existing public island code, but still keep their own private codes for your reference.

The map your trying to publish, is an update for the current published map and will replace it under the same public island code.

3

I found a nasty workaround by restructuring my serialized data . So please consider this topic resolved