Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose scene unique id functionality in Resource #9057

Closed
Ryan-000 opened this issue Feb 8, 2024 · 0 comments · Fixed by godotengine/godot#88111
Closed

Expose scene unique id functionality in Resource #9057

Ryan-000 opened this issue Feb 8, 2024 · 0 comments · Fixed by godotengine/godot#88111
Milestone

Comments

@Ryan-000
Copy link

Ryan-000 commented Feb 8, 2024

Describe the project you are working on

I am making a Multiset plugin for collaborative scene editing, and I need to keep track and update resources over the network across different Godot editor instances.

Describe the problem or limitation you are having in your project

There is no current way to set the embedded resource ID before or when saving a resource. Also, the only way to get the ID is after saving the scene (id generated during save and is based on time!) and splitting the resource path to get the ID.

Not being able to set the scene_unique_id in Resource's is a massive road blocker when creating and keeping track of resources over the network.

When the host creates a new embedded resource in a scene, I cannot keep track of it at all across clients, because the scene unique id is created at save time, so for each client the resource will actually have a different scene unique id, or not one at all. This makes it practically impossible to keep all the changes synced, and will mess up git history, as everyone's will be slightly different.

Describe the feature / enhancement and how it helps to overcome the problem or limitation

Expose scene unique id functionality in Resource

Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams

I made a pull request godotengine/godot#88111

If this enhancement will not be used often, can it be worked around with a few lines of script?

Cannot be worked around its core.

Is there a reason why this should be core and not an add-on in the asset library?

Its Core.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants