Distributing source code with user-created plugins?

[anonymous_user_e5c32abf]

@BrUnO XaVIeR;245749

Well, think again. It happens all, aaalllll, the time. But Unity’s marketplace is so large that people quit jobs when selling plugins that are well received there. Thus fixes are pushed very fast;
However I ensure you none of a dozen plugins I’ve done for Unity 4.5.x are working 100% on 4.6 and also barely work on Unity 5 if at all. I can’t keep investing time on them anymore so I’ve made them free for 4.5.x users. If they want a fix they do itself because source is all there.

And, well, I can only speak for myself; I won’t ever buy anyone’s for UE4 if it is closed source.
I already regreat I paid for RadiantUI

You’re conflating a major engine version change with point releases. I wouldn’t expect an Unreal Engine 4 to work with Unreal Engine 5 in the future. Unity 4 plugins may not work with Unity 5. However Unity 4.X plugins almost always work when Unity upgrades to 4.Y.

A point release from Unreal 4.X to 4.Y should endeavor to maintain API parity using deprecation, just like Unity 4.X to 4.Y does and this would solve many of the issues.

BTW: RadiantUI provided the full source code to licensees. I don’t know what your particular plug there is with it but in the context of this thread that doesn’t make sense since you got the full source code.