# \[CRITICAL\] Building Desync Between Players in Creative 1.0

**URL:** <https://forums.unrealengine.com/t/critical-building-desync-between-players-in-creative-1-0/2842231>\
**Category:** Issues and Bug Reporting\
**Tags:** unreal-engine, open, fortnite-creative, fortnite\
**Created:** [October 18, 2026, 6:10pm UTC](https://forums.unrealengine.com/t/critical-building-desync-between-players-in-creative-1-0/2842231 "2026-10-18T18:10:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![I\_Static\_Rust\_I](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@I\_Static\_Rust\_I](https://forums.unrealengine.com/u/I_Static_Rust_I)\
**Post date:** [October 18, 2026, 6:10pm UTC](https://forums.unrealengine.com/t/critical-building-desync-between-players-in-creative-1-0/2842231/1 "2026-10-18T18:10:32Z")

</div>

### Summary

There is a multiplayer synchronization issue in Creative 1.0 where changes to object placement are not correctly replicated between players.

When one player moves an asset, device, terrain piece, or other object, the other players in the session may continue seeing the object in its original location rather than its updated position. The same issue occurs in reverse when teammates move objects, as their updated placements may not appear on my side.

### Please select what you are reporting on:

Creative

### What Type of Bug are you experiencing?

Assets

### Steps to Reproduce

1. Open a Creative 1.0 island with multiple players.
2. Have one player place an asset, device, terrain piece, or another movable object.
3. Move the object to a different location.
4. Have the other players observe the object’s position.
5. Repeat the process with another player moving an object.
6. Observe whether the updated placements are synchronized across all players.

### Expected Result

Whenever a player moves an object, the updated placement should synchronize correctly and appear in the same location for every player in the session.

This should work consistently for all movable objects, including assets, devices, terrain pieces, and other building elements.

### Observed Result

- Players may continue seeing objects in their original positions after another player moves them.
- Updated object placements are not consistently visible to teammates.
- The issue affects assets, devices, terrain, and other movable objects.
- Returning to the hub and reloading the island temporarily resolves the issue by allowing players to see the updated placements.
- However, moving additional objects can cause the desynchronization to happen again, forcing everyone to return to the hub and reload the island to see the latest changes.

### Platform(s)

All Platforms

### Island Code

0000-0000-0000

### Video

[https://www.image2url.com/r2/default/videos/1792347005677-7c0f43e2-9c00-406f-9358-81b404e5771a.mov](https://www.image2url.com/r2/default/videos/1792347005677-7c0f43e2-9c00-406f-9358-81b404e5771a.mov)

### Additional Notes

This issue significantly disrupts collaborative building in Creative 1.0. Players cannot reliably see each other’s latest changes, making it difficult to work together on the same island.

The current workaround is extremely inconvenient because every time the desynchronization occurs, all affected players may need to return to the hub and reload the island. If more objects are moved afterward, the process may need to be repeated.

Object placement updates should synchronize between all players in real time without requiring everyone to leave and reload the island.

---

<div class="post-metadata">

**Author:** ![Bug-Reporter](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/bug-reporter/32/1223650_2.png) [@Bug-Reporter](https://forums.unrealengine.com/u/Bug-Reporter)\
**Post date:** [October 21, 2026, 5:00pm UTC](https://forums.unrealengine.com/t/critical-building-desync-between-players-in-creative-1-0/2842231/4 "2026-10-21T17:00:23Z")

</div>

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