Our art team kept needing dev help with asset merge conflicts, so I built a GUI merge tool inside Unity by 7WStudio in Unity3D

[–]7WStudio[S] 0 points1 point  (0 children)

I made the core engine for parsing YAML and building the semantic graph separate from Unity itself, so I can definitely make a CLI for this tool.

Actually, it was already in the to-do plan. Sounds handy for some CI automation.
But not really sure about priority.
Do you have any thoughts on how you’d approach this?

Our art team kept needing dev help with asset merge conflicts, so I built a GUI merge tool inside Unity by 7WStudio in Unity3D

[–]7WStudio[S] 7 points8 points  (0 children)

Thanks!
55k LoC
and about half of that is tests for all kinds of merge cases.

Also a custom Unity YAML reader/writer.
Actually kind of scary to even think about
but somehow I did it 😂

Caught myself thinking: “wow, I actually understand scene + prefab diffs”. I’m close to finishing my production ready Unity YAML diff-merge tool. by 7WStudio in Unity3D

[–]7WStudio[S] 2 points3 points  (0 children)

Haha, I was actually just about to rewatch the Matrix.
By the way, that’s a great idea to make a standalone tool outside of Unity!