Thank you for your interest in Mitrapunk and for wishlisting the game. It means a lot.
Two years ago I went quiet on updates while I rebuilt the foundation. I was balancing a 9-to-5 and offline life, so I focused my time on hands-on experimentation. That stretch let me test many mechanics, drop the weak ones, and strengthen the vision step by step.
Today I have a solid working concept of the core systems. The core loop is the clearest it has ever been. You still feel the complexity, the ambiguity, and the pressure to make dense decisions with imperfect information. The loop is clearer and the choices are sharper.
I also refreshed the visuals, while keeping the core promise intact: this is a management sim about running software development inside a big organization. You are not a coder. You are the engineering manager, negotiating priorities, architecture, and people dynamics to ship real features.
I made a short video to show where Mitrapunk sits between the two extremes: one game that abstracts everything into a few clicks, and another that makes you write real code. Mitrapunk lives in the middle, where you think like an engineering manager and navigate real interesting tradeoffs. Watch it if you want the clearest picture of what this game is trying to be.