4 ms·
> 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. IAN
by MichaelDickens 3y ago
> 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.
IANAL but isn't this how it works by default? If two parties agree to a contract, one party doesn't get to unilaterally change the contract after the fact. The only way they get to change it is if they put some wording in the contract to the effect of "As long as the game runs on the Unity engine, Unity has the right to charge whatever it wants." So it would simply be a matter of removing this language from the TOS.
- philipov 3y agoAnd who's to say that they don't just put that language back? They've demonstrated willingness to do that.
- wlesieutre 3y agoUnity's position is > Our terms of service provide that Unity may add or change fees at any time. We are providing more than three months advance notice of the Unity Runtime Fee before it goes into effect. Consent is not required for additional fees to take effect, and the only version of our terms is the most current version; you simply cannot choose to comply with a prior version. Further, our terms are governed by California law, notwithstanding the country of the customer. https://forum.unity.com/threads/unity-plan-pricing-and-packaging-updates.1482750/page-45#post-9297488 https://forum.unity.com/threads/unity-plan-pricing-and-packa... They're saying "the terms of service say we can add whatever new fees we want whenever we want." I'm not sure whether the original fee structure that people had agreed to was outlined in the earlier version of the ToS or not. If people agreed to allow Unity to unilaterally change the pricing structure then they may be stuck with it. But if they need to actually change the ToS to make these fees, then I'm skeptical it would stand up in court (IANAL). They made very definitive public statements that people would be able to use the existing agreements with your current engine version, and saying "you simply cannot choose to comply with a prior version" now can't possibly hold water.