TermsOfService

> The amount of mental gymnastics on display here (not to mention bloodthirstiness) to not acknowledge that the new terms are genuinely a huge improvement and likely palatable to the majority of game actual developers in crazy. A huge improvement relative to the current pricing policy in effect (the status quo), no. A huge improvement relative to the previous incoming pricing policy, yes. But that's only the half of it. The other half is that Unity cannot be trusted to abide by its own terms of service. I don't need mental gymnastics to decide that Unity will never be palatable again. Unity's terms as of October 2022 included the line: > If material modifications are made to these Terms, Unity will endeavor to notify you of the modification. [1] But in April 2023, Unity silently rewrote the terms, and one of the changes was removing that

Thanks, I'll use the delay feature. I accept that this has nothing to do with Godot. I did find the TOS in question, as expected, it's very old (from 2019): https://web.archive.org/web/20201111183311/https://github.co... So people saying "who's to say they won't do this again," if four years isn't enough for you to catch up, I don't know what to tell you. Edit: They have also brought the repo back, which was likely another unrelated change: https://github.com/Unity-Technologies/TermsOfService

> Even the apology misses the most important fact, which is not necessarily the cost of the change itself, but the demonstration that Unity is willing to change terms AFTER you've shipped software using their engine. That's a massive breach of trust as well as a massive risk. And the obvious fix to that is to put out an announcement saying "Sorry about that, you can trust us, and if you release a game using Unity you can stick with that version of the ToS instead of us being able to foist new terms on you whenever we want forever." Except.... Unity did that already last time they made company destroying ToS changes, and then just went back on the promise and said they're forcing the new ToS on everyone. So why the hell is anyone supposed to trust whatever apology they put out this time? https://blog.unity.com/community/updated-terms-of-s

For source code, I prefer the Software Heritage archive over the Internet Archive, because it archives the git history, instead of the HTML UI. This particular repo was saved there[0] and was most recently visited 24 Oct 2022, which has two more terms updates. I have created a mirror of this more up-to-date version at https://github.com/thaliaarchi/unity-termsofservice. Here's how to “cook”[1] an archive from the vault, if you want to do it yourself: curl -X POST https://archive.softwareheritage.org/api/1/vault/git-bare/swh:1:rev:28fdae008c61d9… wget https://archive.softwareheritage.org/api/1/vault/git-bare/swh:1:rev:28fdae008c61d9… --content-disposition tar xf swh_1_rev_28fdae008c61d98d0d9ec55b8cc016ce61809f58.git.tar git clone swh:1:rev:28fdae008c61d98d0d9ec55b8cc0

A more important issue that's not being considered here is that when they had their debacle with Improbable, they committed to a GitHub repo[1] with all the ToS changes and outright said that people could keep using the ToS of whatever major version of Unity they used[2]. They have now deleted the repo, so I wonder if they're just gonna pretend they never committed to that. 1. https://github.com/Unity-Technologies/TermsOfService 2. https://blog.unity.com/community/updated-terms-of-service-an...