Why every game developer is mad right now, explained

Andy Chalk
·8-min read
John Riccitiello, chief executive officer of Unity Technologies SF, sits before the start of a Bloomberg Technology television interview in San Francisco, California, U.S., on Monday, March 18, 2019. Riccitiello discussed the latest trends in the global gaming market. Photographer: David Paul Morris/Bloomberg via Getty Images
John Riccitiello, chief executive officer of Unity Technologies SF, sits before the start of a Bloomberg Technology television interview in San Francisco, California, U.S., on Monday, March 18, 2019. Riccitiello discussed the latest trends in the global gaming market. Photographer: David Paul Morris/Bloomberg via Getty Images

Yesterday, game engine company Unity announced changes to its pricing plan that will see developers charged each time someone installs their game after certain revenue and installation thresholds are met. Unity has been around since 2005 and is one of the most popular platforms for game creation, used for big-budget titans like Genshin Impact as well as games like Vampire Survivors, Pokémon Go, Cuphead, Among Us, Subnautica, RimWorld, BattleTech (2018), and Hollow Knight.

The reaction to the change, which is set to take effect on January 1, 2024, has truly been something to behold: Everyone is mad. And I mean everyone, with that classic Gary Oldman emphasis:

Gary Oldman in Leon shouting
Gary Oldman in Leon shouting

The backlash has been nothing short of furious: Individual developers and indie studios of different sizes all came together with the sort of unity—ahem—that's usually only seen during international sporting events. Some developers predicted Unity would very quickly abandon the new pricing scheme (so far, it has not), others suggested parts of the plan—specifically the retroactive contract changes—might not even be legal, and many swore they'd walk away from the Unity engine completely.

Who's mad?

A small sampling of great anger

Innersloth (Among Us)

Innersloth message on Unity's new Runtime Fee
Innersloth message on Unity's new Runtime Fee

(Image credit: Innersloth)

Aggro Crab (Another Crab's Treasure)

Aggro Crab message about Unity's new Runtime Fee
Aggro Crab message about Unity's new Runtime Fee

(Image credit: Aggro Crab)

Massive Monster (Cult of the Lamb)

See more

Devolver Digital (indie-focused publisher)

Definitely include what engine you’re using in game pitches. It’s important information!
Definitely include what engine you’re using in game pitches. It’s important information!

(Image credit: Devolver Digital)

Landfall Games (Totally Accurate Battle Simulator)

Our thoughts on the Unity Runtime Fee
Our thoughts on the Unity Runtime Fee

(Image credit: Landfall Games)

Garry Newman (Garry's Mod, Rust)

Here's a blog about our favourite game engine company
Here's a blog about our favourite game engine company

(Image credit: Garry Newman)

Mark Mayers (Desolus)

See more

Xalavier Nelson Jr. (El Paso, Anywhere)

ne of the most terrifying parts of the Unity news today is just how much the industry has pushed our dev cycles to become exponentially more complicated, lengthy, and prone to immense dependency. 3 years into a 5 year journey? Heavily reliant on existing tools? You’re fucked. When a decision like this gets announced, and you’re 3 years into a 5 year journey, you have little to no choice. You’re stuck with a partner who may be actively working against your interest, and who you likely increasingly feel you cannot trust. Dev cycles that trap their developers in the process are… the norm now, and not the exception, and we’re going to have to honestly reckon with how these corporate movements are going to impact the experiences we can deliver players without dying in the process sooner than later.

(Image credit: Xalavier Nelson Jr)

Cat Manning (Firaxis)

sorry I’ve been on planes all day
sorry I’ve been on planes all day

(Image credit: Cat Manning (Twitter))

George Broussard (3D Realms co-founder)

Heard from inside Unity that the blog post was reviewed for weeks and internal concerns about poor / confusing messaging, Game Pass, etc, were all ignored. It's resignation time for some folks. Hopefully we will see a walk back. I fear for Unity.
Heard from inside Unity that the blog post was reviewed for weeks and internal concerns about poor / confusing messaging, Game Pass, etc, were all ignored. It's resignation time for some folks. Hopefully we will see a walk back. I fear for Unity.

(Image credit: George Broussard)

Mega Crit Games (Slay the Spire)

Mega Crit Games tweets about Unity's Runtime Fee plan
Mega Crit Games tweets about Unity's Runtime Fee plan

(Image credit: Mega Crit Games)

inXile Entertainment (Clockwork Revolution)

See more

Joe Wintergreen, a designer and programmer whose recent credits include Weird West and Stray Gods, actually launched a website for developers who want to move from Unity to Unreal, called ughiguessiwanttomovefromunitytounreal.com.

Why are they mad?

The uproar is primarily driven by two factors: Unity is attaching a flat per-install fees to games that use its engine, and it's arbitrarily scrapping existing deals and making the changes retroactive.

The policy announced yesterday will see a "Runtime Fee" charged to games that surpass certain installation and revenue thresholds. For Unity Personal, the free engine that many beginning and small indie developers use, those thresholds are $200,000 earned over the previous 12 months, and 200,000 installs; one those marks are met, developers will be charged 20 cents every time someone installs their game.

That sounds like a lot of money, but as we noted yesterday, there are a lot of other factors that could come into play and cause real headaches for devs. "Install bombing," in which angry users spoof multiple installs in order to rack up charges against a target developer, is a risk under this scheme, as is simple piracy; the policy also calls into question how indie developers will want to deal with things like charity bundles and Game Pass, which can bring their games to very large audiences without the attendant revenue.

They've made it clear it's not safe to work with this engine.

Another big issue is that Unity has made this change retroactive: It supersedes any existing agreements with Unity that developers may have made, and it applies to games that were released even before any of this happened. The revenue threshold will be based on sales after January 1, 2024, when the new pricing system takes effect, but sales that occurred before that date will count toward the install threshold.  Aaron San Fillipo of Whisker Squadron developer FlippFly said that willingness to trash existing deals for new cash grabs "[makes] it clear it’s not safe to work with this engine."

We’ve used Unity for 11 years now at Flippfly, and I’ve been teaching kids how to make games with it at a nonprofit for 3. After today’s egregious announcement, I’m actively planning how to move us all to an engine with less hostile business practices. So disappointing. And at this point I don’t care if they 100% backpedal on this. They’ve made it clear it’s not safe to work with this engine.

(Image credit: Aaron San Filippo (Twitter))

Developers also criticized Unity for not answering some important questions about how this scheme would work, or for issuing statements that conflicted others. Details about the changes beyond the public statement weren't provided, and conflicting clarifications that came out after that statement only served to make matters worse. After Unity told Axios that developers will be charged for reinstalls of their games, for instance, a Unity employee said on Twitter that they would not be. Unity eventually nailed that point down in an ongoing thread on its forums, confirming that developers will be charged again if someone who owns their game reinstalls it or changes their hardware.

That thread is not smoothing the waters—if anything, it's making matters worse. Among other things, it says Unity will use its own "proprietary data model" to determine how many times a game has been installed, that early access releases, beta versions, and demos will count toward the installation threshold, that games that have already been out for years (and thus have likely passed at least one threshold) will be on the hook for the fee, and that for developers who feel they've been fraudulently or unfairly charged, "we will make available a process for them to submit their concerns to our fraud compliance team." To put it mildly, that's not a statement that inspires great confidence.

I love that there’s a stream of updates from 3rd parties that are all like I talked to Unity and they clarified that: 1) the bad thing is even worse 2) the less bad thing is the same amount of bad 3) there’s a new secret 3rd bad thing that’s the worst thing you’ve ever heard
I love that there’s a stream of updates from 3rd parties that are all like I talked to Unity and they clarified that: 1) the bad thing is even worse 2) the less bad thing is the same amount of bad 3) there’s a new secret 3rd bad thing that’s the worst thing you’ve ever heard

(Image credit: Josh Sawyer)

As bad as all this is, there's a good likelihood that it will get worse. Indie game developers are at the forefront of this controversy, but Unity is also used in major hit games including Genshin Impact, Pokémon Go, and Hearthstone. How likely is it that miHoYo, Niantic, and Blizzard will agree to fork over a percentage of their revenues (a much smaller percentage than Unity Personal users, yes, but money is money) based on a retroactively-applied contract rewrite?

This applies equally to Unity's reassurance that game developers won't be charged Runtime Fees for games on Game Pass because it's going to charge Microsoft directly: I respect the hustle but I think it's very unlikely Microsoft (or any other distributor) is going to start forking over money just because you said so.

Why is Unity doing this?

Unity presumably had some idea that people wouldn't like this, so why do it?

Some say CEO John Riccitiello is just a habitual rake-stepper: He is, after all, the guy who said developers who don't monetize their games are "f—ing idiots."

Industry veteran Simon Carless believes it's a straightforward business decision: Unity wants a "semi-trackable" way to more effectively monetize its biggest customers, most of whom are mobile games, and it's willing to sacrifice a relatively small part of its business—game engine revenues as a whole only account for about 23% of Unity's revenues, and the PC/console segment is just a small part of that—to make it happen. Unity also offers credits that can be applied toward the Runtime Fee charges for users of its Levelplay service, but that's only available on mobile devices—PC developers can't take advantage.

And even if the change doesn't impact the majority of small developers on Unity, Carless—like many others—said it's not just about the money involved.

"Ultimately, this is about trust. As a game creator, you have a deep relationship with your engine provider, because you're locked into it," he wrote on his GameDiscoverCo newsletter. "Perhaps most small and medium PC & console devs won't be affected significantly by these biz model changes—and we suspect this might be true. But the fact you could be, in unexpected ways that are untrackable or uncontrollable by you—is mentally untenable."

For now, this is how things stand: Unity has pulled the rug out from thousands of developers who use Unity and those developers are looking to get out. There may yet be a walkback, but the longer this drags out, the less likely that appears. Instead, it looks like Unity has made a decision and it's going to ride it out, good or bad—and game devs are going to have to make some tough decisions about what they're going to do as a result.

Update: In a tweet posted shortly after this story went live, Unity changed direction yet again, saying that developers will not have to pay for reinstalls, that trials and demos will not be subject to the fees (although early access releases still will be), and that web and streaming games will not count for fees either.  The thread on Unity's forums has also been updated to reflect these changes.

We want to acknowledge the confusion and frustration we heard after we announced our new runtime fee policy. We’d like to clarify some of your top questions and concerns: Who is impacted by this price increase: The price increase is very targeted. In fact, more than 90% of our customers will not be affected by this change. Customers who will be impacted are generally those who have found a substantial scale in downloads and revenue and have reached both our install and revenue thresholds. This means a low (or no) fee for creators who have not found scale success yet and a modest one-time fee for those who have. Fee on new installs only: Once you meet the two install and revenue thresholds, you only pay the runtime fee on new installs after Jan 1, 2024. It’s not perpetual: You only pay once for an install, not an ongoing perpetual license royalty like a revenue share model. How we define and count installs: Assuming the install and revenue thresholds are met, we will only count net new installs on any device starting Jan 1, 2024. Additionally, developers are not responsible for paying a runtime fee on: - Re-install charges - we are not going to charge a fee for re-installs. - Fraudulent installs charges - we are not going to charge a fee for fraudulent installs. We will work directly with you on cases where fraud or botnets are suspected of malicious intent. - Trials, partial play demos, and automation installs (devops) charges - we are not going to count these toward your install count. Early access games are not considered demos. - Web and streaming games - we are not going to count web and streaming games toward your install count either. - Charity-related installs - the pricing change and install count will not be applied to your charity bundles/initiatives.

(Image credit: Unity (Twitter))

It's fair to say that this latest turnaround has not made things better.

I would like to acknowledge any confusion and frustration anybody has felt as a direct result of reading and understanding my publicly stated, ill constructed and somewhat legally and technically unenforceable positions. I will be providing no further information at this time.
I would like to acknowledge any confusion and frustration anybody has felt as a direct result of reading and understanding my publicly stated, ill constructed and somewhat legally and technically unenforceable positions. I will be providing no further information at this time.

(Image credit: Mike Bithell (Twitter))

  • Up next
  • Up next
  • Up next
  • Up next

Latest stories