DMD 1000 Lecture Notes - Lecture 1: Swarm Behaviour
Document Summary
I(cid:373)agi(cid:374)e your ga(cid:373)e audie(cid:374)(cid:272)e sayi(cid:374)g, (cid:862)wow! (cid:863) a(cid:374)d the(cid:374) just work (cid:271)a(cid:272)kward a(cid:374)d fill i(cid:374) the blanks. Whether spring systems, swarm behavior, gravity, etc, it never took (cid:373)ore tha(cid:374) a few hours to get the (cid:271)asi(cid:272) the(cid:373)e up a(cid:374)d ru(cid:374)(cid:374)i(cid:374)g. this (cid:862)toy(cid:863) should (cid:271)e the core mechanic of the game minus any goals or decisions. There is no win or lose state, just a fun thing to play with. Embrace the possibility of failure - it encourages creative risk taking. Enforce short development cycles (more time != more quality) Constrain creativity to make you want it even more. Gather a kickass team and an objective advisor mindset is as important as talent. Gather concept art and music to create an emotional target. Simulate in your head pre-prototype the prototype. Development: nobody knows how you made it, and nobody cares. If you can get away with it, fake it.
