It's better but I still wouldn't trust them. I will not be using Unity for any future projects.
I'd been using Unity off-and-on for more than a decade, even published two crappy mobile games back in the day
this recent kerfuffle led me to find Godot and I actually quite enjoy it. so even if Unity did a full reversal I can't see myself ever going back to it
I had no idea their CEO was from EA, so in a way I'm glad all this happened as I learned quite a bit
People pay for your software and do all the hard work. Why the fuck Unity want "revenue share"? You already got paid.
Link to the official post: https://blog.unity.com/news/open-letter-on-runtime-fee
It still doesn't return the broken trust or conformation that the people running Unity are insane, but this is a good move and devs don't need to alarmingly port their current projects to other engines.
I want to start with this: I am sorry.
Translation: damn, we really didn't get away with this.
The Runtime Fee policy will only apply beginning with the next LTS version of Unity shipping in 2024 and beyond.
We will make sure that you can stay on the terms applicable for the version of Unity editor you are using
Good. This is how it should've been from the start. If they bake that into the license I think people will be comfortable staying on Unity for the time being.
For games that are subject to the runtime fee, we are giving you a choice of either a 2.5% revenue share or the calculated amount based on the number of new people engaging with your game each month. Both of these numbers are self-reported from data you already have available. You will always be billed the lesser amount.
Also good. It should've been revshare from the start. I still don't understand how they would trust self-reported numbers but we'll see.
These are good changes. The damage isn't undone but at least current Unity devs won't be thrown under the bus.
Updated the link to link to the official unity post
Heres what I had originally posted: https://www.gamedeveloper.com/business/unity-apologizes-to-devs-reveals-updated-runtime-fee-policy