2.2.2: stadium block by block, half-time team talk and event calendar

12 October 2026: Version 2.2.2 of Anpfiff1 is on Google Play, Steam and itch.io. It follows on the App Store once Apple has reviewed it. Unlike 2.2.1 it brings three new features.

Stadium block by block

Instead of eight stands there are now 98 blocks, which you mark one by one or with the brush and expand, with zoom and panning and the aerial photo of your stadium underneath. A construction project locks the blocks being built on and, for spectators, the rows in front of them. Seats can be built roofed right away.

Half-time team talk

At half-time the dressing room waits: praise, criticism, tactics, motivation or a one-to-one chat with a player. The right talk lifts morale and team strength until the final whistle, the wrong one lowers them, and giving the same speech again and again wears off. If you say nothing, the team plays as before.

Event calendar

You can plan one event for every week, with 36 to choose from, from a forest run to an autograph session to dinner with the club management. Every event has an effect and a price, and planning the same thing again and again gives you less from it. If you like, the assistant coach plans along.

Also

• The laptop in the office runs a screensaver with eight patterns.
• Before the post-match interview there is a result board with club crests, the final score, goal scorers and cards. Plus over 100 new questions, and amounts of money appear in your currency.
• In the editor, images have a menu item of their own, five celebration screens can take your own winner pictures, and the help is a reference book with a table of contents.
• Offers for your youth players can be negotiated, the cloud backup only starts after you have agreed, and the matchday overview shows the match statistics of both teams.
• Fixed, among other things: the German league jumping to over 400 teams after renaming a club, the keyboard in the editor on iPhone and a crash of old saves in the cup.

The changelog lists everything in detail. What was measured, and what was dropped along the way, is in the Dev Log.