should you prefab things you only use once?

I started unpacking prefabs from my scene that I only use in one place since I figured that gives me extra context for game objects and where they are at. But then I realized that it makes git commits a lot harder to read since you lose a lot of contextual information about what you have changed within the object and instead you get a big wall of text from the scene.

What do you guys do and why?

How often do you read git commit diffs?

1 Like

For code, I read them fairly often. For scenes and prefabs, not so much.

However, I prefer to make everything a prefab, even one-time objects. That way you can edit them without having to change the scene, which is especially helpful if more than one person is working on a project. You can also do processing on all prefabs, etc. But the big one is being able to change the prefab without touching the scene.

7 Likes

Also, if you make something a prefab it makes it very easy to export a complex object to a Unity package, in case you want to port the object to other projects.

1 Like

Personally I find separating things into prefabs often beneficial even when they’re only used once. For example, when multiple people are working on the same scene, there’s a high chance of conflicts. If they’re all working on separate prefabs, no problem.

1 Like