Unity announced a new fee structure today, and developers are none too happy. “We are introducing a Unity Runtime Fee that is based upon each time a qualifying game is downloaded by an end user,” the company wrote in a blog post announcing the change.
I’m a dad with a full time job and 2 toddlers. If I wanted to dip my toes into game development for the first time and I wanted to use Godot, what kind of project should I do first? Something that’s great for starting out and learning the absolute basics.
Shoutout to Bevy as well. It's not as user friendly or polished as Godot but it's a lot more powerful. If you're a talented game dev I'm sure you could do some amazing things with Bevy.
Bevy is a very different kind of beast. It’s basically “here’s the ECS, have fun!” while it rides into the sunset.
My next project will use bevy, but mostly because its API is so ridiculously small that I can map it entirely into my own engine (which then exposes the ECS through my own API). That would be a lifetime's task with Unity (don’t know enough about Godot to say definitely, but I bet it’s the same, since it has the same architecture).
RIP Unity. First they partnered with Ironsource. Who are the people behind InstallCore it's a wrapper for bundling software installations. It tricks people into installing enough browser toolbars and other bloat to hurt their PCs. Windows Defender and MalwareBytes blocks it. Now Unity does this shit.
Wikipedia incorporates pay-to-win mechanics, lootboxes, microtransactions and cosmetics. There will also be a convoluted crafting system with decaying materials and several incompatible currencies for every purpose imaginable.
Yep, hopefully Godot ends up being the real winner, because with as many AAA studios that have started to abandon their own in-house engines in favor of Unreal, it's starting to feel a bit like Epic is going to end up with more than a healthy share of the market.
From a Cybersecurity point of view, I think this is a legit attack. Imagine a server that has many virtual machines, all of which automatically trigger the reinstall mechanism as fast as possible.
If there is not some kind of limitation on that rule, depending on how their mechanism works, you could cost the game creater a lot of money.
Do you know how many times I install and uninstall a game before I even play it? I could probably destroy a small game company on my own with this fee structure, and I'm sure I'm not alone with the constant installing and uninstalling.
I mean what are they going to do with xcloud plays? Is it just 1 install on the remote Xbox or does it count per player, which means it’s an install every single time someone plays?
I imagine a lot of the doomsday stuff people are saying are not going to come to pass (and some will!). But it’s this kind of ambiguity that always leads to this kind of speculation.
Finally, the company announced that it’s discontinuing Unity Plus subscriptions starting today to “simplify the number of plans we offer.” It says existing members on that tier will receive “an offer to upgrade to Unity Pro, for one year, at the current Unity Plus price” via email in mid-October.
It's kinda amazing how Unity shot themselves in the chest with this one. No, I don't mean foot, they are now actively bleeding from the torso.
No Dev or Publisher is going to be okay with this, none. This basically leaves Devs on the hook for unlimited liability. Even with their walk back of "only initial installs" doesn't help. I myself have both a Desktop and a SteamDeck. That's possibly two installs out of the gate from one customer. Then any time I make an upgrade in the future, or heck maybe even switch Proton versions on my Deck, the Dev could be on the hook for more cash. There's zero transparency with how these "installs" are detected or counted, so there is no way to budget or plan for the expenses.
Businesses hate unpredictable fees.
They'll deal with utilities upping rates, because who are you gonna switch to in a monopoly? But if you're just a tool for them, they'll ditch you as soon as they're able and never use you again.
And again, publishers will care about this too, since their whole job is distribution. Any Dev looking to sign with a publisher, even a subscription service like GamePass, will now be asked which engine they're using, and I bet you 9/10 times the Dev will get rejected if they're using Unity now. That puts even more pressure on Devs not to use Unity.
Unity will price gouge their existing customers(Devs), but will ensure that nobody ever buys their product ever again. At this point I doubt their reputation will ever recover even if they can walk this back. The fact that they believe they can unilaterally add enormous fees at the drop of a hat means they've ruined any trust their customers had in them.
Unity: I can charge you any fees I want, any time I want.
The real hit is free mobile games. Paying per install can be crippling when you naturally have low retention rates.
You can accidentally success yourself into debt if you don't have preditary monetization.
I'm building a game ATM that's meant to be fun and fair, monetization is really low. If it shot up as a front page item for some reason that now went from a huge success to a massive stress point as the number of installs would easily put me into hundreds of thousands of dollars of debt to unity overnight.
Who TF wants to take on that kind of risk? Does this not push mobile games into being even MORE preditary?? Since it's now impossible to build a mobile game with Unity, and just release it as something free.
How would they even track that it was "only the initial install", and what's the metric for that? If i need to reinstall my OS due to a crash, is that a second install for the game?
How about if I replace a piece of hardware that fails, is it considered a new system with a new install?
The whole idea that they can claim additional fees for an "install" is ridiculous.
As someone who's been following Unity's development since 2.0, this doesn't surprise me. They've always struck me as a company that doesn't care about developers. And while all companies are trying to make money, there's a difference between "pay for our product because we need money to operate" and "we love Adobe's subscription model and want to outdo them - and we will squeeze you as much as possible." Have a little heart, Unity.
This only makes sense. Unity is a very big part of what makes a game work and building and maintaining the Unity engine costs a lot of work. They deserve some share of the money made on a game. That share should ideally be proportional to how much money is made by the developer, which should be proportional to the amount of times the game is downloaded. And this is only one of their plans. There are other plans as well. So maybe someone can explain to me why this is not just a sound business decision apart from: I don't want to pay any money?
Unity already charges money once you hit a certain revenue from your game, it's only free if you don't get a lot of sales.
More importantly, according to the article, when questioned it seems Unity hasn't given any proper thought into this model.
If a user installs the game and then uninstalls and reinstalls, it counts as 2 installs that must be paid for. Not only is that unfair, it can lead to abuse. Angry with a change the developer made? Uninstall and reinstall 30 times (automate it) and you will actually cost the Dev money.
What about pirated copies? Unity will still "phone home" and the result will be a developer paying for 1mil installs that he earned nothing from.
What if your game is free to play?
There were some other issues like that mentioned too (in the twitter post in the article).
"This only makes sense. Ovens are a very big part of what makes food and designing and building the ovens costs a lot of work. They deserve some share of the food made in the oven. That food should ideally be proportional to how many edibles items are made by the chef, which should be proportional to the amount of times the food is baked. And this is only one of their plans. There are other plans as well. So maybe someone can explain to me why this is not just a sound business decision apart from: I don’t want to give away my baked food?"
By that logic Microsoft should also be able to charge for any software installation that happens on windows. That also means any and all installations for the customer should be single use, because now all installations cost money.
Would you be willing to pay a certain amount of money any time you want to install some software, doesn't even matter if you've already paid for it? Because that's the business plan you call "sound".
Yeah, you can call that stupid, but I am not stupid. But regardless of your insult, let me talk to you.
I am not sure which Microsoft product you are talking about, but certain Microsoft products are indeed charged this way. It is called an OEM license and while typically every OEM license is negotiated on different terms (per license, per revenue, per download, per install, per duration of usage, etc.), the basic idea is usually that some amount of money will be made by Microsoft proportional to how much use your product is getting. In the Enterprise world it is also common to charge by how much value the user is getting out of the product, which whole sales departments are trying to figure out on a case by case basis with complicated excel sheets. I mean, it is not like Unity invented this model. In fact, Microsoft got as big as it got by selling a pay per copy version of MS-DOS to IBM.
Unity is an ingredient that makes games work. The game is made with Unity and is shipped with the Unity engine packaged inside, just like any other ingredient. So explain to my why Unity can not define some metric which will highly correlate with the amount of usage and charge based on that metric?
So what I get from Unity's site is that they will charge per download. So yeah, potentially you can download a game three times to three different devices or even to the same devices you've wiped. But I would claim that generally speaking the number of downloads is a good indicator of how often a game is used. If you don't like a game you are generally going to download it only once. If you really like the game you are likely to download it again and again to new devices and after wipes. It isn't perfect for sure, but every other metric you can come up with also has a fair share of problems. Maybe you tell me which one is the one that does not have any problems and is still simple enough to bill upon?