I don’t have a finished version of a BP market place i’ve been working on but it’s usually pretty simple to fix things between versions. For example I started in one version and to upgrade to the newer one it was just dropping a few lines off blueprints that no longer compiled cause a false branch never returned. All I had to do to get my WIP project up to 4.9 compatibility. Overall it’s simple things like that. I’ve done the same with several other packages I have, drop them in hit play get the X blue print has errors, cancel out then open up error log fix the issue. Half the time it’s just a warning on a node that got a rework. Other times it’s a process that got fortified by things like the not returning in a returning node improvements. Textures survive with like no work, but materials I have found had things change, or what usually happens is a new lighting scheme really blasts out the old material or such, and it needs adjusting. For the creator that understands probably not much work for me that tend to not dig into materials as much no chance in heck I could fix. So it’s good ot have the version protection but also like the aspects of older versions being available for adaptation by msyelf / fixing on newer versions.