Ubisoft Mainz is doing something big publishers hate doing: explaining itself.
In a new developer blog about Anno 117, the studio finally addresses the gripe that’s been chewing up forums since the demo dropped—players think the user interface is a mess. And while they’re at it, they’re also defending a “controversial” gameplay mechanic they’ve decided to keep, complaints be damned.
That’s not a cosmetic squabble. In a management game, the UI is the game. If the menus fight you, the whole experience turns into spreadsheet-flavored misery.
The demo UI problem: when “functional” still feels awful
City-builders and economic sims live and die on friction. Not the “hard choices” kind—the “why does it take three clicks to find the thing I need” kind.
In Anno-style games, you spend a ridiculous amount of time reading tiny signals: production chains, shortages, logistics bottlenecks, population needs, trade flows. The interface isn’t window dressing; it’s the control panel. If it’s slow, cluttered, or weirdly organized, the game stops feeling like strategy and starts feeling like chores.
And demos are gasoline on that fire. They’re marketing, sure, but they’re also a public stress test. The moment players get their hands on a UI, they build muscle memory, they notice missing shortcuts, and they compare it to older Anno entries and whatever else they’ve been playing in the genre. Change it too much after the demo and you break people’s habits. Don’t change it and you look stubborn—or worse, oblivious.
Ubisoft Mainz clearly decided the silence was costing them more than the explanation would.
This blog post isn’t a promise—it’s a defense brief
Don’t confuse a developer blog with patch notes. This kind of post is usually about setting expectations and drawing boundaries: what might get tweaked, what’s too expensive to redo late in development, and what the team thinks players are simply wrong about.
Because here’s the unsexy truth: rebuilding a UI late isn’t “move a few buttons.” It’s navigation logic, screen consistency, tooltips, multiple resolutions, accessibility work like font sizing and contrast, and then a mountain of testing to make sure you didn’t break everything else. A blog that leans hard into “here’s why we did it this way” often signals targeted fixes—not a full redesign.
The subtext reads like: We heard you. We’re not agreeing with all of you. That’s risky with a detail-obsessed strategy community, but it’s also more honest than the classic corporate fog machine: “We’re listening” followed by nothing.
Still, talk is cheap. If the post doesn’t come with concrete examples—what’s changing, what’s getting clearer, what shortcuts are coming—then it’s just a well-written excuse.
Why keep a “controversial” mechanic? Because it props up the whole system
The spicier part of the blog, as reported by the gaming press, is Ubisoft Mainz openly owning the decision to keep a mechanic that players have been side-eyeing.
In management games, “controversial” usually translates to one of a few things: a constraint that feels arbitrary, micro-management that drags, a punishment that feels too harsh, or a rule that makes it hard to understand cause and effect. When a studio keeps something like that, they’re betting the long-term depth is worth the short-term irritation.
Developers typically justify these mechanics in three ways:
First, identity: the mechanic creates the pacing and pressure that defines the game.
Second, mastery: players hate it early, then learn it, then start using it to pull off smarter strategies.
Third, balance: remove one load-bearing rule and suddenly half the other systems don’t matter, and the difficulty curve turns into a pancake.
But here’s the catch: players don’t rage-quit because something is hard. They rage-quit because it feels unfair. And “unfair” in game design usually means “I can’t see what’s happening.” Which drags us right back to the UI. If you’re going to keep a demanding mechanic, the interface has to make it legible—clear warnings, readable thresholds, obvious levers to pull. Otherwise you’ve built a trap and called it “depth.”
There’s also the calendar problem. Late-stage mechanical changes can ripple through the economy, progression, AI behavior, tutorials, scenarios, and difficulty tuning. So “we’re keeping it” may really mean “we’re keeping the concept, but adjusting the numbers and improving the signals.” That’s the version players might actually accept—if Ubisoft Mainz is straight with them about what’s being tuned.
What this says about Anno 117’s strategy—and Ubisoft’s nerves
Ubisoft doesn’t usually spend this much time publicly justifying interface decisions. The fact that Mainz felt compelled to do it tells you the disagreement isn’t some tiny Reddit nitpick. It’s loud enough to threaten the game’s first impression.
And first impressions matter more than publishers like to admit. Reviews and user ratings punish friction immediately—often before critics even get deep into the systems—because the UI is what you touch in the first hour. If the interface becomes the headline at launch, it can drown out everything else the game does right.
There’s also a familiar tension here: accessibility versus depth. Big publishers love widening the funnel—simplify screens, hide complexity behind extra menus, reduce on-screen data so it looks “clean.” But Anno fans don’t show up for clean. They show up for numbers, comparisons, optimization tools, and the satisfying click of a well-oiled production chain. If the UI feels like it was designed to look pretty in trailers instead of helping you run an empire, the community will call it a downgrade.
Ubisoft Mainz is trying to convince players the interface is an instrument panel, not a showroom. Now they have to prove it—with actual iteration, customization options, and visible improvements the next time the public gets a look.
Quick answers
Why are people so hung up on the Anno 117 UI after the demo?
Because in a management game, the UI controls how fast you can make decisions and how clearly you can understand the system. If it feels off in a demo, that impression sticks—and players immediately compare it to older Anno games and genre standards.
What does keeping a controversial mechanic mean for balance?
It usually means the mechanic is structurally important. Removing it could break other systems. The more realistic outcome is keeping it while tweaking thresholds/costs and improving how the UI communicates what’s going on.
