I love the Victory library, but I must confess that I really do miss not being able to work with preview builds anymore. I understand the reason why, of course…
, is there usually a high labor cost associated with updating nodes to work with the newest engine versions? Obviously just the spent maintaining two branches isn’t ideal… But maybe when a new version preview release drops (just Preview 1, not updated), it would be beneficial to just quickly toss out a single compatible version of the plugin as-is? Keep updates to the main version (not the preview version) until it becomes official… But with the multi-month cycle on preview releases, even if it would mean that not EVERY new Victory node could be tested, people who are legacy-bound to Victory because they use existing nodes would be able to start testing in preview releases, even if it meant having to wait a little while for Victory to catch up.
I know for my own part 99% of what I want and need Victory for, at the moment anyway, isn’t the stuff you’re rolling out now, and I confess—sorry to say—I’d rather wait until “4.11 drops proper and Victory gets updated for it” for access to subtitles in sound cues than I would for access to the newest engine features. I (typically) only update Victory when it’s needed due to an engine update, and the extra nodes you’ve added are like a bonus at that .
And it would only literally be a single upload (the editor version) since I think the common-sense case could be made that nobody is attempting to package a game made in a preview release (certainly Epic cautions strongly against doing so). It would be a one- deal when the first version of a new preview release dropped to provide a degree of compatibility for testing projects, which is what the previews are FOR.
Just a thought.