{"author_name":"Mophs","cat":"LD #30","comments":[],"epoch":1408848000,"likes":1,"metadata":{"p_key":"27503","p_author":"Mophs","p_authorkey":"39312","p_urlkey":"62946","p_title":"Progress Report","p_cat":"LD #30","p_event":"LD30","p_time":"1408848000","p_likes":"1","p_comments":"0","p_status":"UPD5","us_key":"39312","us_name":"Mophs","us_username":"mophs","event_start":"1408665600","event_key":"24","event_name":"LD30"},"text":"

There is\u00a020 hours, 35 minutes, 45 seconds remaining. That means LD30 is over half way done.\u00a0I’ve been working on a 2D game in unity. There have been a few hiccups along the way but progress is good.\u00a0I’m taking a minute to recap before I go back to programming, I want to set this out in my head.<\/p>\n

2D Workflow<\/strong><\/p>\n

Going into this i’d never sprited, animated sprites, worked in 2d (let alone Unity’s “mostly there” 2D tools) or used mecanim. I love and hate state machines. Learning to drive animations via state machines and not direct state calls has made things much more manageable. In a spaghetti sort of way, see below.<\/p>\n

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

 <\/p>\n

 <\/p>\n

Pyxel<\/a>\u00a0edit is a fantastic tool that’s made animation and tilesets\u00a0very fun. I’ve had a few issues on the Unity end with imports, especially trying to tweak sprite sheets after setting them up. I’m probably messing up the export settings because I’ve had to manually re-setup animations and sprites more times than I care to admit.<\/p>\n

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

 <\/p>\n

 <\/p>\n

It also turns out that when you’re only working in 3+bg colours, things get a little confusing when taken out of context. With nothing moving the game looks like a red blob. I’ve implemented player movement, crouching, jumping, shooting, dashing, health, death, basic monster (slime), and a few back end things that I never really will use, unless I decide to go full puzzle game.<\/p>\n

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

 <\/p>","time":"August 23rd, 2014 9:40 pm","title":"Progress Report"}