{"author_name":"Mr. Wonko","cat":"LD #22","comments":[],"epoch":1324128000,"likes":0,"metadata":{"p_key":"61696","p_author":"Mr. Wonko","p_authorkey":"3631","p_urlkey":"97461","p_title":"So I started working\u2026","p_cat":"LD #22","p_event":"LD22","p_time":"1324128000","p_likes":"0","p_comments":"0","p_status":"UPD5","us_key":"3631","us_name":"Mr. Wonko","us_username":"mrwonko","event_start":"1323993600","event_key":"8","event_name":"LD22"},"text":"

I’m still not quite sure what my game will be like, but I’ve decided to keep it simple and do something where you move a player through a 2D environment. That requires levels, ideally a level editor (it probably takes less time to code that than to manually create the levels?) and some kind of physics engine. I don’t have any physics in my Renaissance engine yet. So I started from scratch after all, using SFML and Box2D.<\/p>\n

So far I’ve compiled Box2D (I’m always surprised when that works flawlessly on Windows), created a basic high-level architecture\/hierarchy for the game objects\/levels (keeping (de)serialization in mind for level editing\/saving\/loading), created an SFML window which can handle being resized and wrote a debug display class for the physics – I figured that’d help me debug physics better, but it’s basically not very important… I don’t even have physical objects at this point! (Besides some test objects to debug the debug drawing…)<\/p>\n

\"\"<\/a>

I have no game, but I've proven that Box2D is indeed a physics engine.<\/p><\/div>\n

Well, I suppose that’s just me doing the easy things first. And I fear I might end up having a nice level editor but no game to go with it. Oh well, we’ll see.<\/p>","time":"December 17th, 2011 8:20 am","title":"So I started working\u2026"}