{"assets":[],"author_link":"author\/abominas\/","author_name":"Abominas","cat":"LD #32","categories":["LD #32"],"comments":[],"epoch":1431300600,"event":"LD32","likes":4,"metadata":{"p_key":"83755","p_author":"Abominas","p_authorkey":"0","p_urlkey":"294495","p_title":"Slick: Post-mortem","p_cat":"LD #32","p_event":"LD32","p_time":"1431300600","p_likes":"4","p_comments":"0","p_status":"WAYBACK","us_key":null,"us_name":null,"us_username":null,"event_start":"1429228800","event_key":"27","event_name":"LD32"},"source_url":"2015\/05\/10\/slick-post-mortem\/","text":"

For my second Ludum Dare, with limited time, I did a pretty decent job. Slick was originally supposed to be a game about protecting your family\u2019s land from corrupt underground oil drillers. The unconventional weapon of choice is complicated to explain, but simple to understand. However, I had barely enough time to finish implementing said weapon with schedule issues. What I have to show for judging is a demonstration of some cool effects and code architecture.<\/p>\n

\"screen2\"<\/a><\/p>\n

What Went Right:<\/strong><\/p>\n

All the carefully planned design architecture and technology worked perfectly. The different systems function elegantly and independently. Each gear of the engine has its own workload.<\/p>\n

The effects are what I am most proud of in this entry.<\/p>\n

What Went Slightly Less Right:<\/strong><\/p>\n

It took some time to implement and maintain the design architecture.\u00a0 Had I instead gone for a more crude approach, I could have coded more gameplay and had even more to show for my limited time.<\/p>\n

Please help me achieve my goal of 100 people playing and rating my game! Play Slick here<\/a>! \":)\"<\/strong><\/p>\n

Tags: ld32<\/a><\/p>","time":"May 10th, 2015 11:30 pm","title":"Slick: Post-mortem","title_was_empty":false}