{"author_name":"GreaseMonkey","cat":"LD #24","comments":[{"author_name":"","time":"August 28, 2012 10:46 am","epoch":1346168760,"text":"Yes, scrolling was the hardest part for me too – even though I don’t need to load anything because everything is in memory. It was about 5 hours including the 2 hour bug hunting… \":)\"","spam":"N"}],"epoch":1346023140,"likes":1,"metadata":{"p_key":"52087","p_author":"GreaseMonkey","p_authorkey":"2396","p_urlkey":"87785","p_title":"Post-mortem.","p_cat":"LD #24","p_event":"LD24","p_time":"1346023140","p_likes":"1","p_comments":"1","p_status":"UPD5","us_key":"2396","us_name":"GreaseMonkey","us_username":"greasemonkey","event_start":"1345766400","event_key":"12","event_name":"LD24"},"text":"

Well, this is pretty much what I learnt:<\/p>\n

NEVER EVER IMPLEMENT SCROLLING DURING THE COMPO EVER AGAIN.<\/span><\/strong><\/h2>\n

I basically had 6 hours to make a game. Totally reusing this engine for next time, so I’ll have the whole 48, instead of spending a whole day on the bloody scrolling.<\/p>\n

But aside from a few last-minute hacks, it’s a fairly solid engine. It maintains a linked list of all entities, allows for adding and removing said entries, has a roughly O(n^2) collision detection method, scrolls a 128×128-tile\u00a0(64×64-chunk) virtual playfield in a 64×64-tile VDP playfield (I hope to extend this to double the size in each direction), has slopes (I COULD NOT RELEASE THIS WITHOUT SLOPES THAT WOULD BE WRONG), and that’s pretty much it.<\/p>\n

Oh yeah, I pretty much spammed twitter<\/a> during the compo. I cannot guarantee the whole lot will make sense.<\/p>\n

\"\"<\/p>\n

So there we go!<\/p>","time":"August 26th, 2012 6:19 pm","title":"Post-mortem."}