Inconsistent Island Code and Session Conflicts When Building Private Versions Simultaneously in UEFN

Summary

When multiple team members build a private version at the same time using UEFN, several issues arise:

  • Same Private Version Codes: The popup displayed by UEFN sometimes shows the same private version code for all users, instead of generating unique codes per user.
  • Mismatched Island Content: The resulting island map can reflect the content of only one team member, even though others initiated their own builds (but it’s normal because we get the same code)
  • Incorrect Metadata on Creator Dashboard: The description shown in the Creator Dashboard may belong to one team member, while the actual map content corresponds to a different team member.
  • Session Interruption: If one team member is actively in a UEFN session, and another member builds a private version code, the first user’s session is disconnected. They are unable to start a new session until they restart UEFN.

One last information, we remark this behaviours when we build a private version code without having a session already launched, don’t know if it’s important or not.

Please select what you are reporting on:

Unreal Editor for Fortnite

What Type of Bug are you experiencing?

Publishing

Steps to Reproduce

Have multiple team members open UEFN and prepare to build private version.
Initiate the private version build process simultaneously or have one of the user alreay in a session.

Expected Result

Each team member should receive a unique version code or have his session still connected.

Observed Result

Duplicate version codes and mismatched content occur, session disconnected

Platform(s)

UEFN PC

Island Code

4819-0681-5878

Additional Notes

If you can look the build log of the shared island code, we are sure the issue appear at this moment.

We’ll get someone to check this out and we’ll let you know if we need more information.

1 Like

What type of information do you need? I can try make a video on 2 computers simultaneously, to show you what’s happening.

1 Like

Checking!

1 Like

Did you make sure all of your changes were synced with other members of the team?

Yes, a video would help.

1 Like

Thanks for the answer!
I’ll make a video at the start of next week.

The project isn’t currently synced across the team because we’re working on different UMAP files for various reasons (like faster issue fixing, using smaller map versions, …)

But that might be the problem, if the system is not designed to support building multiple versions of the game at the same time if the project is not sync.

FORT-886282’s status has changed to ‘Ready for QA’. A member of the QA department is investigating the issue.

Please ping me when you get the video done. Thank you!