Supporting Pre-Release Engine Builds
Compiling is not the, constantly adding to and updating two engine versions worth of updates every I want to add a node:
- victory plugin editor version
- victory plugin packaged binaries
- victory plugin editor + packaged on media fire
is what takes the 
It is the distribution of the software that is taking me the , not the software itself
The labor is in having to maintain two versions of updates. And I really am not getting very many donations at , so maintaining Victory Plugin for two engine versions is just beyond my capacity when offering whole plugin for free to the community.
Epic really needs to think about when it comes for marketplace plugins, because if everyone is so impatient to be on the not-entirely-stable-supposed-to-be-test branch, rather than the stable tested branch, it is going to bother everyone if plugin makers dont always upload for the test branch.
But as I said, having to maintain two versions of the plugin becomes ridiculous.
I wonder why everyone wants the unstable-declared-to-be-test branch more than the official release?
The point of a test branch is for testing, not mainline development!
Yet everyone seems to move over to the latest and supposedly greatest, even though it is just a test branch.
What to do?
Perhaps for certain pre-release builds that are highly preferred, I would simply stop supporting the previous engine version and move on to the pre-release version.
I am under the presumption that discussion will become a moot point within a few days, when 4.11 is released, but if it seems to be taking too long I will do the upgrade.