The Unity meltdown sucks for students and educators, too

gamedeveloper.com:

As of late Monday evening, everything was going according to plan in week 12 (of 12) of my game design course. I currently (and typically) teach two sections of Game Design Fundamentals online at the Berklee College of Music each quarter, where students interested in game development learn about the history and current landscape of games, study a number of design principles, and workshop their own ideas into a fleshed out Game Design Document.

We do weekly lectures, often with sessions of a particular game, highlighting player experience goals, design, production and aesthetic considerations that went into it. We also do lots of demos with accessible game engines, and plenty of tutorial content. Since Unity is the engine I've made almost all of my own (small) games in since 2009-2010, the engine is usually a big part of this, and features heavily in the list of suggested resources I leave students with each quarter.

That list includes specific Unity Learning courses that I've taken myself and found especially helpful, Unity tools that I personally use and love (like Yarn Spinner, which is currently Unity-based but Godot and Unreal versions are in the works), and favorite tutorials for making small games or features from various genres. I have years and years of collecting these resources and recommend checking them all out to my students, so they have viable next steps after the class is done.

This is not to say Unity is the only tool I usually shout out (I do a lot of live sessions with the likes of Bitsy, Narrat, etc), but it features heavily. Since the announcement Tuesday, I've been frantically pruning that list and trying to figure out what I'm going to tell my students before our short time is up (and tearing my hair