{"id":70,"date":"2018-02-24T01:54:49","date_gmt":"2018-02-24T01:54:49","guid":{"rendered":"https:\/\/projects-old.etc.cmu.edu\/parallel\/?p=70"},"modified":"2018-04-23T19:41:14","modified_gmt":"2018-04-23T19:41:14","slug":"parallel-week-five","status":"publish","type":"post","link":"https:\/\/projects-old.etc.cmu.edu\/parallel\/index.php\/2018\/02\/24\/parallel-week-five\/","title":{"rendered":"Parallel: Week Five"},"content":{"rendered":"

Week five update:<\/strong><\/p>\n

In this fifth week of the project semester, we have been working towards getting a good progression of puzzles to begin playtesting with our core audience.<\/p>\n

\"\"<\/p>\n

Admittedly, we ran into a few bumps along the way this week – the biggest of which was issues in the specificity of our design rules. So moving forward, we’ve written down in more detail the rules we expect to work under in designing our puzzles:<\/p>\n

    \n
  1. The player can jump.\u00a0<\/span>One block high, and t<\/span>wo blocks far.<\/span><\/li>\n
  2. Player cannot program a block that has already been programmed (unless they reset the puzzle).<\/span><\/li>\n
  3. Player can ride on blocks.<\/span><\/li>\n
  4. Modules are restricted by energy.<\/span><\/li>\n
  5. Move costs energy based on the arguments – 1 unit = 1 energy.<\/span><\/li>\n
  6. Energy is based from puzzle to puzzle.<\/span><\/li>\n
  7. No gravity for blocks and energy balls.<\/span><\/li>\n
  8. Reset will set the puzzle and the player back at the beginning positions.<\/span><\/span><\/li>\n<\/ol>\n

    To go more in depth on these rules, we also worked out the specifics of the design constraints in a stand alone document<\/a>.<\/p>\n

    On Thursday, Feb 22nd, we were able to get a prototype of the game that had updated UI, as well as a progression of a few puzzles. The art\/environment is not in yet, but for now we wanted to see how the prototype would play like, and got it to a level of whiteboxing where we can test it.<\/p>\n