![\"Event](\"http:\/\/ludumdare.com\/compo\/wp-content\/uploads\/2016\/08\/Screen-Shot-2016-08-27-at-9.28.09-AM-550x349.png\")
<\/p>\n Previously, in LD36…<\/p>\n
The design\u00a0is simple. The mule<\/em>\u00a0creature in the center is basically a bio-mechanical caravan housing a family of post-apocalyptic pilgrims. (Mmm, bio-mechanical<\/em>. What a sweet\u00a0word, Mr. Giger.) Things happen to your people along the way — think FTL without real-time elements. The main challenge for the player will be resource management.<\/p>\n I made an events queue system. The game will be divided into days, and each day will be divided into time periods. Each of these time periods will constitute a turn. On each turn, an Event will take place. Events can be added to the queue as needed (e.g. if a trader appears, queue up\u00a0a Trade\u00a0event) but only\u00a0one\u00a0event will be played on each turn. If there are no events in the queue, a NoOp event is created, and the game renders that as “Nothing happens”.<\/p>\n Events\u00a0can be flagged as “major”; major events are immediately moved to the top of the queue. This is essential for critical events such as character deaths — after all, if you’ve got a bunch of minor events queued up and a character falls into the furnace, you’d want to get notified for\u00a0their death as soon as possible rather than watch\u00a0them burn for multiple\u00a0turns as the queue empties out.<\/p>\n As is typical of game jam entries, this is all driven by a GameManager god class.\u00a0It looks deceptively clean for now, but I know what’s coming. The bugs are out there, waiting to sneak into my haphazardly written, tightly coupled, singleton-oriented spaghetti code. And I shall\u00a0let them in, in the name of progress and speed, and in the hope that a few\u00a0of them manage to transcend their cursed nature and reveal themselves as… features.<\/p>","time":"August 27th, 2016 11:51 am","title":"Day 2: I can make spaghetti"}