We’re starting to get “uasset saved with empty engine version” warnings in our packaged build. I know the solution is to re-save the file. However, I was wondering if it’s possible to automate re-saving the file? For example, opening up the uasset binary and overwriting a couple bytes to update the engine version from bash.
Opening up the uasset in a hex editor shows that 4.14 is saved in multiple places, which would correspond to the statement that a uasset is, “a collection of individual serialised asset types without an overarching file format.” mentioned in this [answer][1]. Which, kinda sucks. I was hoping for a file header with a revision number at the top I could edit.
