{"author_name":"hexagore","cat":"LD #31","comments":[],"epoch":1417905180,"likes":3,"metadata":{"p_key":"23718","p_author":"hexagore","p_authorkey":"34027","p_urlkey":"59117","p_title":"Update #2 \u2013 End of Day One!","p_cat":"LD #31","p_event":"LD31","p_time":"1417905180","p_likes":"3","p_comments":"0","p_status":"UPD5","us_key":"34027","us_name":"hexagore","us_username":"hexagore","event_start":"1417737600","event_key":"26","event_name":"LD31"},"text":"

What a day… this Ludum Dare I wanted to use Blender as a level editor for my Three.JS engine to play with:<\/p>\n

It worked!<\/p>\n

\"Screen
\n <\/a>
\n It’s super, super hacky but I was able to use bones as entity data, where the first bone in a chain had the type and location of an entity, then I used child bones to indicate other parameters. This way I could configure the size of doors, the paths of entities, the size of things etc.<\/p>\n

This is the end of the first day for me and I am ecstatic to be able to say I have my game’s level fully designed and playtested. It takes about 10 minutes to beat so that feels about right.<\/p>\n

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

Tomorrow morning I’ll be doing the sound effects and music first (so easy to overlook), then it’s polish time – as much shiny as I can squeeze in in the time remaining. It’s taken all my willpower not to try to do something about the dreadful graphics today. I added no shaders, no parallax effects, no particles, no textures, no lights. The geometry, other than the collision mesh, is just what Three.JS lets you generate procedurally. I am growing as a person by embracing my inner programmer artist.<\/p>\n

TIME FOR SLEEP.<\/p>\n \n

Tags: blender<\/a>, development screenshot<\/a>, development update<\/a>, three.js<\/a><\/p>","time":"December 6th, 2014 5:33 pm","title":"Update #2 \u2013 End of Day One!"}