Save with Versioning

Fantastic tool for project management with one massive flaw: Library Assets!

If you set something as an asset, this tool will lead you to having an Asset Library entry for every save version. A work around is not setting the asset mark in the versioned files, opening the published file after pushing it and setting the asset there but then you have to reclassify it each time.

This is very frustrating—and dangerous as it increases human error in a project. I'm not sure of a technical solution other than the already mentioned feature request to be able to publish to a different folder. This could allow for a "published zone" in a project that isn't an Asset Library path and so won't introduce duplication from the working versions.

Some thoughts for improvements:

• It would be nice if there was no suffix required for the published version.
• The ability to branch is not implemented in the UI, and requires you to manually add an extra _v001 to the end.
• I don't know how complex this is would be, but it would be cool to use the Bone Collections style UI for the file list. It has support for a nested/tree list.