Request Description

Why can't you go after TLauncher since its only for pirating?

Question that just popped in my head: Would I get support if I used TLauncher?

No, piracy is not supported.

See: https://github.com/CaffeineMC/sodium/issues?q=is%3Aissue%20state%3Aclosed%20piracy

Ok then why not make sodium crash when used on TLauncher?

I will figure out something and make a PR if needed. I don't have a Windows machine or a way to use a Windows VM, but that won't stop me.

Please, stop this. I guess, you don't understand the background of the messages that brought you here, there's no need to escalate the drama. Also this approach won't change anything.

The crash is in response to technical issues with pojav driving a large volume of reports and support requests upstream. An earlier implementation that simply showed a warning doesn't even work due to said technical issues.

That many of these are from people who don't own the game is an aggravating factor, but the goal here is not to reimplement DRM for Minecraft and disingenuous use of the tracker is not welcome.

To be clear, we don't like TLauncher either, and if we figure out that you're trying to get free support from us while pirating the game, we will just ban you. Nobody likes dealing with pirates, and pretty much every other mod developer will agree. But you're missing the point by making this into an issue about piracy when it simply isn't.

We don't get nearly as many bug reports/support tickets for people using cracked launchers as we do for PojavLauncher. And those bug reports are always because PojavLauncher itself is broken, not because there is a defect with our mod. This is the exact same thing that the authors of VulkanMod have been saying since day one.

There are hundreds of videos on YouTube which are exacerbating this issue by misleading users into thinking they can get Sodium working on PojavLauncher, all of which are wrapping our downloads in ads so they can turn a profit. And none of these videos tell users the critical information they need to know, which creates support burden on us to explain these things to people.

Even more frustratingly, the average Android user seems to be clueless as to what information we ask for, and can't navigate a filesystem if their life depended on it. So all the bug reports we get are in-actionable and useless because they basically just read "my game crashed, sad face." We have to pull teeth to get useful information, and the hilarious part is, we still go out of our way to do that despite better judgement.

At the end of the day, this whole transaction is very one-way. PojavLauncher needs Sodium, not the other way around. Yet the expectation is for other mod authors to support a proprietary, closed-source renderer on devices that never receive software updates and for which have the most notorious, mindbogglingly broken graphics drivers. And when we ask for anything to make our lives easier, for there to even be the most basic diagnostic in the launcher to detect when incompatible renderers are being used with mods, we're turned down.

The problems with PojavLauncher being used for rampant piracy are supplementary to the technical problems, and really, they were just what broke the camel's back here. We obviously don't want to be associated with piracy, and believed in good faith they would eventually close the issue like they did on iOS. But it's evident after talking with ArtDev that piracy is an intended feature, and that they have no intention of doing anything about it, because their team is openly admitting that they benefit from it.