470
Unity apologises.
(www.pcgamer.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 18 Sep 2023
470 points (92.7% liked)
Technology
60123 readers
2642 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 2 years ago
MODERATORS
They went for a retroactive pricing change.
Imagine that you start a game project (which will cost you years and a lot of $$$ to develop) and at any point Unity just arbitrarilly changes the conditions (which can be of any kind, not just extra charges) that apply to your game, after you're too far into development to feasibly replace Unity, and do it retroactivelly, so after your game is already out it can still get impacted by it.
Suddenly a totally viable project might become unviable or, worse, an active drain on your company's finances or even your own (i.e. your company and, depending on how you structured it, even you yourself can go bankrupt), and all of that based on the fickle wishes of a higher up in Unity.
At this point it makes no business sense whatsoever to choose Unity: there is way, WAY, WAY too much risk involved by choosing it (new charges that apply retroactivelly as this one can literally kill your company) and at the same times there are viable alternatives out there without such risks.
For any project not yet deeply tied to Unity, from the day they came up with a retroactive change to their pricing, the obvious, clear as day, choice from a business point of view became to not use anything from Unity, even for shitty shit asset-flipping "near zero investment" projects.
Which in some countries could also be illegal.
Can you quickly tell me what's the applicable jurisdition for this if say, a gamedev company based in Uruguay sells a game made with Unity (HQ US) via Apple Store (HQ US) to a user in China who installs it 3 times?
At the very least it will cost you quite some legal fees to merelly figure out the jurisdiction because there are multiple legal angles to go after this (contract law, intellectual property) which might yield different jurisdictions (maybe it's contract law and then maybe its the US, maybe Uruguay, or maybe it's IP law and it's the copy of the game to the device local storage i.e. the installation - that is treated as requiring licensing of the Unity IP, and it defines the jurisdiction as China because that's were the user did it ... or maybe the US because that's what the IP owner is).
This "cleared up", next you'll have to figure out if it such retroactive pricing changes were legal there or not: maybe you're lucky, maybe you're screwed.
For new projects I don't think it's worth it for a small gamedev company to spend time and money pursuing the "let's clear the legal status every way Unity can screw me in the future so that I can use Unity" option rather than the "let's use something else" option.
It's really only worth checking it for companies with existing or advanced projects on top of Unity were the income/potential-income from those projects justifies it (vs the options of just pulling the project out from distribution or redo it with another framework).
I mean, sure, eventually somebody will have paid the legal costs of this and maybe the legal decision is broad enough and in the right jurisdiction for your company and it's applicable ... and then Unity just goes and comes up with some other shit that somebody has to take through the legal rigmarole to figure out if they can. Also, unless its illegal everywhere, some companies will be affected.
Meanwhile "Don't use Unity on any future projects" is a pretty straighforward way to minimize your project risks...
Then Urugauay, since the contract for Unity is between Unity and the game studio in Uruguay, and is the game studio that must pay Unity, not the Chinese buyer (not sure if applicable by Uruguay's law). In every country where you sell something, you need to follow the law applicable to the buyer, not the seller.
If you change Uruguay with Italy (where I live) then it is illegal, for example no matter where the seller has the HQ and no matter where I sell the game. And I suspect in most of EU. If you sell me something then we have a contract, then both of us cannot change it retroactively unilaterally, I am not even sure if it is legal if both of us agree. Many US based company tried and failed.
If Unity pull a stunt like this on an Italian game studio, the studio can simply avoid to pay and if Unity kill the current license agreeement the studio can sue them. Sure, Unity can then refuse to sell new or renew licenses to the studio, but that is another thing, the old license is still valid.
True, but that is the cost of doing business in a foreign country. Why did you think Apple (US based) put the USB-C on the new IPhone ? To be nice ? Or because EU imposed it ? Is not this a price for Apple ?
That is another problem and, at least in Europe, Unity is on very thin ice. From the game studio perpective is a problem only if their local law allow for a retroactive change in a contract, else the new terms are void and Unity can say what they want.
In Europe, if Unity can track retroactively the installations, then they tracked the users and if they (or the game studio ) did not notified the user it is a direct violation of the GDPR and all it need to is just one user that sue them. And before you say something, it is already happened before. The fines are pretty interesting btw...
Completely agree on this.
Again, nope. If it is illegal in the studio HQ country, then is not worth checking: the term cannot be changed.
What can happen, in Italy, is that Unity can change unilaterally the contract for the future and in this case the game studio can simply modify the selling price of an already released game or put a adeguate price tag in any future game in a too advanced development stage to be redone with another game engine. And of course change the game engine for all the other projects.
But there is no way that Unity can monetize past installation of a game based on a contract with certain conditions.
Are you a lawyer?
Because if there's one thing I learned from my own contact with the Law (not being a lawyer myself) is that sometimes it is indeed exactly as it makes logical sense (in which case it would basically be as you describe) and sometimes it's not and depending in the jurisdiction you might even have to end up in Court to figure it out.
I don't know about you, but I won't stake my company's future on presuming the applicable Law matches common sense, even with the assurances from a non-lawyer on the Internet.
My point being that we won't be sure until somebody gets legal clarification on this, maybe even gets their day in Court over this, and after that then all of us to whom that legal clarification does apply (and me being in the EU also, it would probably apply to my country as it does to Italy) can rest easy (or not, depending on what the clarification says) ... until Unity tries something else.
Meanwhile I'll keep on slowly decoupling the code from its Unity dependencies on the project I have and trying out Godot and the Unreal Engine, just in case and because I have to, as I pointed out, protect myself from the risk of them pulling some other bullshit in the future.
Even this does get reversed (or shown illegal in the applicable juridiction) and I do end up shipping the project with Unity, I'll always keep on "looking over my shoulder" with them and this has definitelly made it more likely that I will end up using Godot or Unreal on my next projects, if only because it has pushed me to properly put time aside to seriously try both out and I'm pretty sure they'll be better than Unity at least for some kinds of game.
I don't really even trust Unreal until Unity takes a legal hit for this. What's to stop Epic doing the same thing?
Considering how locked into an engine a project can get, why risk a corporate engine unless you absolutely have to?
Yeah, I've been thinking along the same lines.
Having been in the business of software since the 90s and following what's been done under the cover of IP Law (which would apply here given that the installation of software has been deemed a copy of copyrighted material), I've seen a lot of shit that would seem not to make legal sense be accepted by courts (notice how EULAs in shrinkwrapped software are deemed "an attempt at changing the implicity contract of a sale after the sale" in jurisdictions like Germany ut in others like some US states they've been found to be legally enforceable) so all this stuff has to be legally clarified in an iron clad way before it can be trusted.
I mean, even open source software with the most well written and ironclad license has been shown to have problems because of Patents (another bit of IP Law heavilly abused in the last 3 decades).
Nope, but I know my rights. And as a buyer I have rights.
I know, and I agree. But on this thing I am pretty sure for a couple of reasons:
Me neither, but I know what the law say in my country and I know that if I sign a contract, the seller cannot alter it after.
I know for a fact that if we agree that you sell me something at 1 euro/month, you cannot decide in 2024 that the charge for 2023 is 2 euro/month. You can ask 2 euro/month for 2024 and sign a new contract, but 2023 it a done deal. And if you put a clause in the contract that state "the seller can change retroactively the charge and pretend the difference on arrears" the clause is automatically void since it is a vexatious terms that are forbidden by law by default.
Maybe Unity can pull the trick in the US where, given the prohibitely high costs of the justice system, a small indie studio would pay and a big corporation can discuss, but in EU I don't think Unity can really pull the trick. Or any of these kind of tricks.
Yep, trust is way harder to gain and really easy to lose.
I would like to be a bit more certain that at point were the heavilly-rigged IP lLaw (with associated things like EULAs and "by using this software you accept it's TOS") crosses with Contract Law, obviously breaking of contract law with retroactive changes is laughed out of court even when the legal argument was made that the Unity Runtime is licensed separatelly from the Unity Editor and as the installation of a game that contains parts of the Unity Runtime is a copy of copyrighted material, then it's up to Unity to determine the licensing conditions.
However after watching the complete legal shit show that's been done around IP Law since at least the 90s (note how in almost 3 decades EULAs in software haven't been clearly and definitivelly thrown out everywhere, given that they're trying to "change the terms of the implicit contract which is a sale after the sale"), I'm not willing to risk my company until I'm sure.
I mean, if all this was for certainly ruled by Contract Law and only Contract Law, all you say makes perfect sense as that's pretty mature even in cross-jurisdiction trade relations. However this stuff overlaps with IP Law (as I said, the installation of software in a computer is considered a copy of copyrighted material) and that one has been heavilly rigged and abused for decades, including in situations where Contract Law would seem to apply (EULAs in software being a pretty big one).
You seem to be going from the starting from the point that the Law makes sense and is fair, which understandable ... if you aren't well acquainted with any lawyers ;)
Well, I obviously understand you and would say that it is the right thing to do.
And I only talk about my country and by extension think that maybe it is the same in all the EU even if I know that, while there should be an uniform law it is not always that way.
But even if the Unity Editor and the Unity Runtime are licensed separately, this just make 2 license so 2 contracts, nothing else. But both licenses must follow the law of the country they sell it.
Which is true.
What I am saying is that what Unity cannot do is to do a retroactive change to the terms of the license.
I am pretty sure that the EULA in Italy and EU is different from the one in US and the one in other countries.
So probably the EULA I accept is legal in my country and if there is some illegal terms they are void.
Let's say that I had to interact with lawyers more than I'd liked to.