One of the silver linings of being bed-ridden 70-80% of weekends for the past 5 months is being able to play video games guilt free. When you don't have the mental focus to do anything productive, and don't have the physical ability to do much of anything period, working your way through your Steam backlog feels like a solid option.
During this mass-play of games, two games lodged in my designer-mind for similar reasons: The Witness and Vampyr. While these two games are very different from each other, they share a common design flaw: design choices that distract from the game's core elements.
A speaker at GDC (unfortunately I can't remember the specific speech) made the argument that we shouldn't aim to please everyone with our games; that tactic often leads to more bland, middle of the road game design. Instead, we should design in a way that sparks conversation and controversy. If a game mechanic is polarized between "loved it vs. hated it", your design is more interesting than "everyone said it was fine."
This speech crystallized some of my dissatisfaction with certain aspects of team advancement. In v3.1 of Karma, team upgrades often follow a similar pattern: get the ability that increases our action skill, get an ability to make training xp more efficient, etc. Even the upgrades that were less optimization focused felt...dull?
So I decided to rework almost all of team advancement around a few principles:
I'm known for going on tangents. The only consistent thing in my life is that I spend most of it creating things: novels, games, graphics. I love taking apart how art and games work, then reconstructing my own version from the pieces. I'm also enough of a layout perfectionist to adore eraser shields.