Question on Git LFS and Blueprints (which are uassets)

like floats, not all uassets are the same

Blueprints often are similar to source code and are being changed quite often. When we add “uasset” to our git lfs tracking, what does that mean in terms of source control for assets like “Tank_BP” or “MainMenu_BP”?

Is there a way to differentiate between these, and should we within source control?

It is possible to write rules which are more discerning. The problem is that uassets are binary so they are inherently hard to diff and will always bloat a repo.

Privacy & Terms