Submit your impossible demands to #ManifestoJam by February 13

Just a brief note that a bunch of folks are doing a "Manifesto Jam" (which is maybe possibly inspired by my survey of manifestos in games blog post from last year) and there's about 1-2 days left to participate.

I even participated myself, writing a short screed called "KILL UNITY; WE ARE ENGINES." It was fun to try to figure out a specific aspect of games that I cared about, and to try to distill that into entertaining hyperbole. Remember: no nuance, no relativity, just pure belief! Go ahead and let your flag fly, and perch it on the swollen corpse of the old world order!

Here's the inspiring blurb, copy and pasted from the itch.io page:

THIS JAM IS FOR COLLECTIVELY UNCORKING OUR UTOPIAN ENERGY IN 2018

In times of crisis, uncertainty, conservatism and even just standard personal disappointment people overwhelmingly retreat to saying “be practical!” This doesn’t necessarily imply a way that is meaningfully better than any other but instead coerces you to chirpily go along with the way others are already comfortable doing it, or comfortable with you doing it, and keep and alternatives or resentments on priv.

Manifestos are important precisely because they are impractical. Whether positive or negative, whether embracing potential worlds or outright rejecting the one you’re in. They are visionary, they demand, they refuse. Manifestoes can be of any scale, defining your personal aesthetic or how to fix the entire world, but they cannot be satisfied.

Postcards from Unreal, pt 3: on spaghetti monsters

Unreal Engine 4

We're now a few weeks into the Unreal level design class, and things seem to be going OK. Our students have enough familiarity with Unity that they're able to digest a lot of the 3D workflow without too many problems. People are happily grayboxing here and there, and we recently did an intro to Blueprint scripting.

In the past, I've been pretty skeptical of teaching visual programming methods to students. Teaching a specific visual scripting tool always felt like we were locking students to that toolkit, versus learning how to code in C# or Lua or JS, which is a generalized language useful across multiple engines and multiple industries. Visual programming was considered a relatively niche practice, where you might mock-up an art installation in MaxMSP but not much else, and even Unreal used to confine visual programming to its Kismet level scripting system. (The precursor to Blueprint.)

However, that criticism of visual programming is gradually losing its power as this type of practice becomes more common in the game industry. Many Unreal Engine 4 devs (as well as Epic themselves) make heavy use of Blueprint for making games, a lot of Unity devs rely on the third-party Playmaker plug-in, and even upstart engines like Godot support a visual programming workflow. AAA texture generating darling Substance Designer also has a heavy node-based workflow. It's everywhere!