![\"devScreenie01\"](\"http:\/\/www.ludumdare.com\/compo\/wp-content\/uploads\/2012\/12\/devScreenie01-300x269.png\")
<\/a><\/p>","time":"December 15th, 2012 7:57 pm","title":"Time For Some Undeserved Sleep"}This Jam is going worse than the last one if I’m honest. Countless struggles with Visual Studio bugs, the general slow, demotivating process of writing a tile system in a framework I knocked together in the late hours of the previous week, and frustration with other roadblocks I’ve encountered. It’s not been a pleasant ride.<\/p>\n
What you see below is barely interactive. You can move the camera, and the tile your mouse is over is highlighted by a red outline. The likelihood of doing my original idea justice seems slim and I’ve spent the last two hours or so just trying to think of another way to continue from where I am. I’ve drawn a blank, so I’m going to sleep on it. Whatever I do I will be disappointed, but I said I was going to finish something this time, and I fully intead to do so.<\/p>\n
Things I’ve learned so far (and in my previous jam attempt):
\n 1. Don’t roll a tile system out during the jam.
\n 2. Singleton managers are best for fast development. None of this constantly accessing parents’ parents’ managers lark.
\n 3. Pick a SIMPLE idea. Do not forget this when looking at the list of uninspiring ideas in front of you and deciding to try the only interesting one. Pick a SIMPLE one.
\n 4. Don’t use C++. Not unless you’re really confident with the code-base at hand, and have a stable installation of an IDE to use.
\n 5. Don’t start the Jam burnt out. Staring at code at the office all week and my messy framework afterwards didn’t put me in great shape at the start.<\/p>\n
<\/a><\/p>","time":"December 15th, 2012 7:57 pm","title":"Time For Some Undeserved Sleep"}