We have ran into a little snag with our usual Hype pipeline. The usual behavior is that we are able to make batch changes to existing Hype Scenes in a Document by having a consistent naming convention, and then when we want to change all of the XXX elements in a Hype document, we simply drag all new same-name assets into the Resources panel and accept the Replacement prompt, thus making batch edits.
However, a file in use today has mysteriously stopped being able to accept batch edits this way. Despite being authored by the same user off of our remote drive as other Hype files which have successfully accepted batch edits, this file asks for a Replacement prompt, but then adds "-1" to all of the filenames on clicking Accept, effectively breaking the batch edit process.
Any tips on how to ensure the original behavior works would be greatly appreciated!
I see that there is a similar post from 2016 requesting this feature, so I am assuming that the original behavior is the intended behavior and this is some sort of error!