HN Theater @HNTheaterMonth

Last year at GDC, Nintendo's Hidemaro Fujibayashi, Satoru Takizawa, and Takuhiro Dohta broke down the creation of the game in a full length session with video of the original top-down 2D prototype: https://www.youtube.com/watch?v=QyMsF31NdNc

⬐ rendaw

At 18:12: https://youtu.be/QyMsF31NdNc?t=1092

Yes, they talk about it in the GDC talk[1] and that's what I was referring to: That I can see how even in such a simple prototype the fun seemed evident.

[1]https://www.youtube.com/watch?v=QyMsF31NdNc

In their GDC talk (https://www.youtube.com/watch?v=QyMsF31NdNc) one of the core concepts they present is "multiplicative gameplay", which sounds a lot like what NetHack and Dungeon Crawl Stone Soup aim for as well.

It's a surprising amount of fun to have multiple ways to solve puzzles and try to come up with one that was or was not intended to solve it.

⬐ BHSPitMonkey

Here's a direct link to the timestamp where they talk about this, and show off an internal 2D prototype of their "chemistry engine":

https://youtu.be/QyMsF31NdNc?t=1067

⬐ HeavenBanned

After playing 10+ hours on the Wii U, I can safely say the addition of the weapon fragility mechanic (after 20+ years of Zelda not having that mechanic) is the most frustrating aspect of this game. It's just not fun. I hope the next Zelda incorporates the expansiveness with more direction and zero weapon fragility.

⬐ stonesixone

Their "Chemistry Engine" model (described starting at 39:55) includes Rule 3, which says that materials can't change another material's state. But what about a player (a material) eating an object like a poisonous mushroom (also a material) that makes them sick? Or eating a magical mushroom that heals them? It seems like there are cases where you would want to model materials changing another material's state.