このサイトを正しく表示するには、最新のブラウザを使用し、Javascriptを有効化してください。

Spine Unity Github contains meta files

FelixW

Shouldn't you take out the meta files from spine-unity/Assets in github? 😮

Pharan

Unity serialization requires them to keep GameObject components in tact. Directly, they need to be there so the Example scenes work.
In other cases, if they weren't there, Unity would auto-generate them every time they are deleted or moved and that would break projects especially when upgrading.

This allows users who opt to use the repo instead of unitypackages keep their serialization.
They could also opt not to use them by deleting them on their end.

FelixW

Ok, I understand that upgrading could be a pita in certain cases.
I don't understand why the example scenes shouldn't work with self-generated meta files. How would any example scene work that doesn't have them? Also, what would happen in the case that a self-generated meta file id is the same as one of those in the Spine repo?

Pharan

The sample scenes use the .meta files of the other assets, particularly prefabs, scripts and scriptableobjects. Other scripts and ScriptableObjects use the meta files of all other kinds of assets it needs.
I'm not sure what .meta files of the scenes themselves are for.
In any case, this is how you would serialize your Unity project on a git repo. You include the .meta files or else connections between assets break.

Not sure what happens if the guid matches, but it looks like it's a 512-bit id. I'm also not sure what the chances are there.