-
Notifications
You must be signed in to change notification settings - Fork 253
Description
Description
This is a theoretical edge case I’m raising for consideration (not something I’ve tested yet).
When Rojo is already synced and a new non-folder instance is added inside a service (e.g., ServerScriptService.ScreenGui.Script), syncing results in two copies of the instance in Roblox Studio.
Steps to Reproduce
-
Start a Rojo sync.
-
Put it in ServerScriptService in Roblox Studio (.rbxm)
-
Use below to create a new non-folder instance inside a service (example: create
ScreenGui > ScriptinsideServerScriptService).- Put this in ServerScriptService in a Rojo project (this is a folder):
ScreenGui.zip
- Put this in ServerScriptService in a Rojo project (this is a folder):
-
Bug happens?
Expected Behavior
Only one new instance should appear.
Actual Behavior
Two instances of the same object are created.
Short Theory (Possible Cause)
This instance does not have an ID that Rojo can track, causing it to be instantiated and duplicated during sync reconciliation.
Why This Matters
Edge case to consider for two-way sync communication.