{"author_name":"Tulrath","cat":"LD #21","comments":[],"epoch":1315536480,"likes":1,"metadata":{"p_key":"63550","p_author":"Tulrath","p_authorkey":"4703","p_urlkey":"99335","p_title":"Stranded Post-Mortem","p_cat":"LD #21","p_event":"LD21","p_time":"1315536480","p_likes":"1","p_comments":"0","p_status":"UPD5","us_key":"4703","us_name":"Tulrath","us_username":"tulrath","event_start":"1313712000","event_key":"7","event_name":"LD21"},"text":"

Since this is my first LD, I’ve been thinking a lot about my post-mortem, plus I’ve been working on “Stranded Again<\/a>“, that’s going be my enhanced version of Stranded with improvements as suggested by the LD community. \u00a0Plus my Twitter Followers count is going up steadily, so I’ve been keeping up the pace \ud83d\ude00<\/p>\n

WARNING! \u00a0Some minor story spoilers ahead…<\/strong><\/h3>\n

 <\/p>\n

\"\"<\/a>The Idea<\/strong><\/h3>\n

When the list of theme topics was down to 20 or so, I got out a notebook and came up with single-sentence game ideas for ALL of them. \u00a0My idea for “Escape” was:<\/p>\n

Escape: You are tiny brown spider, trying to escape from a research lab.<\/em><\/p>\n

After doing this for all 20, I went back and came up with a list of Actions<\/strong> and Challenges<\/strong>.<\/p>\n

Next, I asked myself, well what exactly do spiders do? \u00a0Thinking about Actions<\/strong>, I think, \u00a0is a good way to create core game mechanic ideas.<\/p>\n

 <\/p>\n

    \n
  1. \n
    Catch insects for food<\/address>\n <\/li>\n
  2. \n
    Spin webs to stop “bad guys” (bad insects?) from fleeing, or from attacking something or someone else<\/address>\n <\/li>\n
  3. \n
    Collect DNA from insects they catch<\/address>\n <\/li>\n
  4. \n
    Catch bad dreams<\/address>\n <\/li>\n
  5. \n
    Collect nanites, grid-bugs, software bugs?<\/address>\n <\/li>\n <\/ol>\n
    \u00a0<\/address>\n
    Next, I came up with Challenges<\/strong> a spider might face. \u00a0I thought that thinking about challenges was \u00a0a good way of coming up with a list of antagonists.<\/address>\n
    \u00a0<\/address>\n
    \n
      \n
    1. \n
      Web is destroyed by… fire, rain, people, wind, other insects<\/address>\n <\/li>\n
    2. \n
      Web decays over time<\/address>\n <\/li>\n
    3. \n
      Spider dies from hunger, or runs out of webbing<\/address>\n <\/li>\n <\/ol>\n
      \u00a0<\/address>\n
      \u00a0<\/address>\n
      \"\"<\/a>The Story<\/strong><\/address>\n <\/div>\n

      Then I took all this and wrote a tiny Story<\/strong>. \u00a0Every game, at its core, must tell a Story – no matter how simple it is. \u00a0This one I thought was about as simple as I could get. \u00a0I didn’t know this at the time, but keeping the Story simple made the programming much easier as well.<\/p>\n

      Escape: You are a tiny brown spider caught in a research lab. \u00a0You can collect DNA from insects. \u00a0Collecting DNA in the right sequence gives you special, but temporary, abilities. \u00a0There is a girl trapped in the lab too. \u00a0The girl is “dangerous” and “different”, but you don’t know why. \u00a0THEY have taken DNA samples from her too.<\/p>\n

      “I can’t leave here without getting them back — I can’t collect them all in time, but I know a little spider who can.”<\/em><\/p>\n

      I actually thought, of all my ideas, this one was \u00a0really \u00a0s-t-r-e-t-c-h-i-n-g<\/strong> \u00a0it to match the theme – probably the worst match-up of the 20 — and the LD community echoed these sentiments, but not in a mean way — the whole community has been awesome.<\/p>\n

      \"\"<\/a>The Ruleset<\/strong><\/h2>\n

      Next I started to think about rulesets. \u00a0Which came up with this list of rules:<\/p>\n

      These are the ones I was able to implement:<\/p>\n

        \n
      1. \n
        You win each level by collecting all the insects before you run out of web strands<\/address>\n <\/li>\n
      2. \n
        Your web strands do not carry-over from level to level, but are refilled when you start a new level<\/address>\n <\/li>\n
      3. \n
        You lose a level if you are unable to catch all the insects with the strand allotment you are given<\/address>\n <\/li>\n
      4. \n
        Levels can be replayed if they are lost<\/address>\n <\/li>\n
      5. \n
        When you lose a level, your strand allotment and all the insects for the level, are reset<\/address>\n <\/li>\n
      6. \n
        You will always have at least 1 more strand than there are enemies, but the ratio of strands to enemies gets smaller as you progress in levels<\/address>\n <\/li>\n
      7. \n
        The story of the game is told through dialog, that is “unlocked” as you complete each level<\/address>\n <\/li>\n <\/ol>\n
        These are the ones that I couldn’t implement because I ran out of time:<\/address>\n
          \n
        1. \n
          Change the ball colors and the fly colors so that you would have to jump from ball Blue to ball Yellow to catch Fly Green<\/address>\n <\/li>\n
        2. \n
          Create bonuses that you could catch that would change color of the ball you are either jumping from or jumping to in combination with 1 above.<\/address>\n <\/li>\n
        3. \n
          Create obstacles that you don’t want to have your web touch — like fire. If your web touches fire, the fire goes back and disintegrates the ball you just came from.<\/address>\n <\/li>\n
        4. \n
          Create “safety” bonuses that you can catch — like water. Water and other bonuses could be caught and stored for later use.<\/address>\n <\/li>\n
        5. \n
          More of all of the above, but with other opposites. Might be quite challenging to get the right combinations.<\/address>\n <\/li>\n
        6. \n
          Mutations! Each bug represents a different DNA code, catch the bugs in the right combination and your spider gets a temporary mutation.<\/address>\n <\/li>\n <\/ol>\n
          \"\"<\/a>What Worked<\/strong><\/address>\n

          Prioritizing the rule-set from the design above helped tremendously. \u00a0When I initially came up with the list of rules, they weren’t in the order shown above. \u00a0It took about 2 hours to work out all the inter-dependencies between them all. \u00a0Each time a rule was identified as a prerequisite for another rule, it got a +1 — the rule that it relied on it got a -2. \u00a0When I sorted this list from highest score to lowest score, I had my to-do list in order of functional dependency. \u00a0This really worked because at each step of the way I had a “working game”, so I could stop adding features almost at any point in the list as soon as I ran out of coding time — which is exactly what happened.<\/p>\n

           <\/p>\n

          Creating a schedule in a spreadsheet ahead of time and marking off hours for “sleeping”, “eating”, “family time”, etc… \u00a0I had one row for every hour of the compo, and for the most part stuck to that schedule. \u00a0My development time went into just a little bit more detail (but not much more) and had rows for “Game Artwork”, “GUI Artwork”, “Sound Effects”, “Music”, “Coding Win\/Lose Conditions”, etc… \u00a0I also had two hours each day (one in the afternoon, one in the evening) allocated as “DO NOTHING” where I had to get up from my computer and take a break. \u00a0That had a HUGE positive impact on my productivity, my mood, and I think I solved a half-dozen coding issues “in the back of my head” each time I did this. \u00a0Also, writing down any “hairy” coding issues during the day and then reviewing them before I went to sleep really worked — I woke up knowing the solution \":)\"<\/p>\n

           <\/p>\n

          Leaving LOTS of time at the end. \u00a0I left a full 6 hours at the end to run final bug-testing, upload my game, ask friends and family to play to make sure it worked, make any last minute fixes, write my forum post ahead of time, write my entry, announcing via all the social media channels, IMing with people about it, etc… \u00a0I think those last 6 hours were the most busy and I may actually allow myself more time in future compos.<\/p>\n

           <\/p>\n

          Using classes for everything. \u00a0I have a class for “spider”, another for “bug”, another for “strand”, etc… \u00a0I used my UML\/OOP books as guides and came up with a complete list of objects I’d need for the game, and then attached all the methods to them as I went along. \u00a0This worked exactly the way it’s supposed to and it made the actual coding a breeze (which in total I think was only about 8 hours).<\/p>\n

          \"\"<\/a>What Didn’t Work<\/strong><\/h2>\n

          Thinking that GUI programming would be easy. \u00a0It wasn’t! \u00a0GUI programming ended up taking nearly 4 hours more time than I had initially thought. \u00a0And in the final product you can see that there just aren’t a lot of GUI controls to help with gameplay. \u00a0There’s a reason why most AAA game studios have entire teams dedicated to GUI programming (even when using a “GUI engine”) — it’s very tedious work. \u00a0Unity GUI makes it as easy as it can possibly be, but it still just takes a set amount of time to create all that GUI functionality — GUI systems are inflexible in their time demands. \u00a0In the future, I’ll be able to estimate this better I think.<\/p>\n

           <\/p>\n

          Using the dialog system as a means to control the game progression. \u00a0Such a bad idea! \u00a0This is where I really fell down in my technical design. \u00a0I should have created dedicated and separate classes for “game” (to control the game state) and created instances of a “human” class (one for the male scientist and one for the female scientist). \u00a0I realize now that I was so focused on the game mechanics (which mostly involved the spider, the strands, the anchors, and the insects), that I simply forgot about these classes. \u00a0I ran into some problems about mid-way through that I solved with a “gameManager” class that contained all the variables and methods to handle the gamestate and dialog… but it was all mashed up together. \u00a0In the future, I need to be more thorough with my technical design.<\/p>\n

           <\/p>\n

          Not leaving enough time for additional levels. \u00a0The final product has 6 playable levels (and then a 7th level that can be replayed as much as the player wants). \u00a0Seven levels might seem like a lot for a Ludum Dare compo entry, but in my case, levels only took 5 to 30 seconds to solve. \u00a0So, all-in-all I had maybe 5 minutes of gameplay — that is IF the player stopped and read the dialog \":)\" \u00a0 \u00a0I should have done those calculations ahead of time to know how many levels I would need to create. \u00a0Originally I wanted to provide about 30 minutes of solid gameplay. \u00a0So using that calculation, it should have told me that I would have needed 60 or 70 (!!!) levels. \u00a0That, of course, would have been a big Red Flag telling me that the gameplay is too easy and goes by too fast.<\/p>","time":"September 8th, 2011 9:48 pm","title":"Stranded Post-Mortem"}