Automatic Updates Disabled
Added 2024-08-04 01:34:02 +0000 UTCUntil a new build is made, automatic updates have been disabled for the latest builds at the time of writing this.
This is a result of people distributing the CaVE application and DisplayEx mods freely online without my approval, and refusing to remove the stolen content. I cannot continue to support people who are using such files that were not intended for them.
In the future I will try to take steps to allow me to better address this when it happens, with minimal impact to you supportive users of the community. I cant completely avoid impacting you, but I can try to minimize it as much as possible.
I will try to get a new version out as soon as I can, since without the automatic updates... there is no access to the latest stock databases. But ATM I have no time frame. There is a lot going on lately, a lot of stress, and a struggle to desire working on the projects.
...
I'm sorry to anyone that noticed this Patreon was unavailable for half a day. This was another direct result of such actions by the outside community. CaVE has always been a fight for me with retaining motivation to keep working on it, and specifically with people who I deem thieves and entitled leeches.
Again... this is not and has never been about money. It is simply about people showing support to encourage me to continue. And specifically about not supporting such entitled thieves/leeches. This Patreon has been great for that! It sucks that one person can ruin things for so many.
Comments
Someone posted it to reddit a couple weeks ago. It has since been removed there. But as a result of that, someone has taken those files and re-posted them elsewhere... and they are not removing them. All it takes is one entitled leech to see free unrestricted access, to then open the flood gates like that. At the very least, me disabling these updates like this, cripples that leaked build. It is barely more useful than v1.4.6 now. So any supporter here feeling effected by this Automatic Update disabling, at least take solace in that. That it has a significant effect on the entitled leeches leaked build. I have considered the registration key path. But its not really viable with a C# app. And just not worth the effort for a project I still intend to be fully public some day. This is just a private beta is all. Once its public, there will be almost no need for scumbags to leak and share such things. For now... I need to take that more seriously. Getting v1.5 to a point of public release. The public build will still be behind the Patreon build, but not as much as v1.4.6 is. Adjusting the Automatic Update feature to give me more options to disable leaked builds, should hopefully be comparatively less involved.
DarkAkuma
2024-08-04 02:10:40 +0000 UTCI am so sorry this has happened. your work is really amazing and I hope you find a way to mark it to figure out who stole it. Maybe require the username for each person in the build i.e. whatever the username is, it is required and built into the app with their name on top of the app when launched? or something.
B47M4N
2024-08-04 01:56:04 +0000 UTCWho’s even doing that in the first place?
Some idiot
2024-08-04 01:43:31 +0000 UTC
