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

Better GIT support #1080

Open
Gamer-XP opened this issue Mar 2, 2024 · 0 comments
Open

Better GIT support #1080

Gamer-XP opened this issue Mar 2, 2024 · 0 comments

Comments

@Gamer-XP
Copy link

Gamer-XP commented Mar 2, 2024

When multiple people work on the same project - there are a lot of issues, even with external levels options.

  1. UIDs. They may easily collapse when merging 2 commits, and there is no way to fix that but to manually change all uids used, and increase NextUID value in the project file itself
  • When loading, you can, likely, check which UIDs is used by which asset type. Use (Type, UID) key instead of just UID to store the link internally. With this you can check if UIDs collide in a lot of cases (as long as types were different) and fix UIDs by incrementing them.
  • Auto-increase NextUID to max(NextUID value, actual max uid value + 1)
  • Try to go away from UIDs to GUIDs. Json will bloat a bit though.
  1. Editing main project file may be tough to make right, but, at least, letting other people add new levels freely is very important point. As long as project file is not affected - can easily add new levels, then merge the project.
  • Can make LDTK auto-import level files it finds in the project folder. If it's a new level - check if UID is free. If not - assign a new one
  • Maybe, instead of auto-importing, can make it so you can drag-n-drop level file in LDTK window to import it
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant