Killing the Walk Monster

A custom engine is never _needed_ technically speaking since COTS engines are often customizable to the point where you can do anything you want with them. That doesn't mean that they don't influence the design of games, though. There's a talk that Casey gives where he explains how he implemented the movement system for The Witness, in which he shows examples of Unity-based "walking simulator"-type games dealing with limitations of the engine in ways that The Witness was able to totally avoid. This allowed the game's artists to be creative with set design without worrying as much about performance issues or collision bugs, thus potentially opening up more design space. ▶ this video Here's some praise of The Witness by Fabien Giesen: > That’s where I am right now. I have never seen another game as cohesive as this. Not even close. Without getting into specifics or spoiler territory, I have never seen a game with such manifest intention behind every single detail, nor one where all the details cohere this well into a whole. This goes for the design and gameplay itself, but also across traditional hard boundaries. Game design and art play off each other, and both of these are tightly coupled with some of the engine tech in the game. It’s amazing. There is no single detail in the game that would be hard to accomplish by itself, but the whole is much more than the sum of its parts, with no signs of the endless compromise that are normally a reality in every project. link

I feel the same about Casey and his work, and like another commenter said, his simple, practical and honest approach to his work is refreshing in an era of languages, environments and tools that feel bloated, slow and ineffective (IMHO). > That being said the whole network idea, and the fetishisation of his particular coding philosophy was always cringe. And I agree with this too. The point of Handmade Hero to me was always to show that the complex software systems that you interact with can be understood despite their size and complexity, and that it's still possible (though perhaps in a lot of cases impractical) to recreate these from the ground up. Also that there's tremendous value in understanding how something works from first principles (see also Casey's 'How to Open a Black Box' lecture, link ). Having said that, while I feel it's important to aspire to some level of simplicity and solving-the-actual-problem that Casey's coding style embodies, it also feels like an approach that works best only when a) the number of people working on a single program is relatively small and b) the expertise is deep and so the need for abstractions is low or non-existent. With Casey's background in game tools it makes a lot of sense, but this approach doesn't seem like it scales up, and he's essentially the only contributor to Handmade Hero too. > It took him and his team 8 years of dedicated work to make The Witness, and it's just not a very technically impressive game. I'm a big fa

▶ this video Here’s a game developer talking about the problem and how they solved it in The Witness, but note well the limitations he describes. It’s not directly useful if the player can jump, for instance.