#chl1007

Before the work session on Tuesday 4/19, I did not know about the “Record ystem audio” feature. It’s a simple feature that I’d overlooked during my work with Camtasia. I found out about the feature after searching for it on the Techsmith FAQ page to improve the audio quality of a YouTube clip I was using.

Week 12: Anarchy and Disruption

Thursday 31: Project Proposal. Contract

·         Discuss more about topic

·         Thursday: Create a contract in class

·         Friday: Continue working on video through Camtasia

·         *Don’t forget to include credits for video (cite images, videos, etc.)

·         Saturday: complete 3 minutes of video

 Week 13: Anarchy and Disruption

Tuesday, 4/5: Project proposal due. Research Report.

Thursday, 4/7: Research Report Draft Peer Review.

·         Sunday: revise video

·         Monday: finish revising video and POST video

·         Tuesday: Continue research in class and start on rough draft, compile articles, essays that I will refer to in the report. Create an outline of the report

·         Tuesday night: get halfway done with rough draft

·         Wednesday: complete rough draft of research report

·         Thursday: Get report peer reviewed and revise

·         Friday: Keep revising

·         Saturday: more research to complete report

 Week 14: Boundaries of the Digital

Tuesday, 4/12: Research Report Due. Open workshopping

Thursday, 4/14: Open workshopping

·         Sunday: Keep revising

·         Monday: have final draft ready

·         Tuesday: submit Report

·         Tuesday’s Open Workshop: compile all images, videos, audio for Camtasia

·         Wednesday: plan out what the video will look like (create a story board)

·         Thursday’s Open Workshop: spend whole class putting together video, images and audio

·         Friday: keep working on rough draft of project

 Week 15: Boundaries of the Digital

Tuesday, 4/19: Final Project Peer Review. Open workshopping

Thursday, 4/21: Open workshopping. Prepping for Presentations.

·         Monday night: Complete draft of project

·         Tuesday: Get project peer reviewed and revise  

·         Tuesday: draft out presentation

·         Thursday: work on presentation content

 Week 16: Boundaries of the Digital

Tuesday, 4/26: Final Project Due. Presentations.

·         Saturday: Finish presentation

·         Sunday: Practice presentation

·         Monday: Get everything completely ready, practice a little more.

·         Tuesday: Present

http://www.philome.la/leechanho1007/hungry/play

Creating a Twine game was not something I was familiar with. I had never heard of Twine nor had I ever play a game that was created through the Twine interface before the start of this unit.

Through Twine, a user can create a game to persuade, inform, or simply entertain the players of the game on a topic through interactive story telling. For my Twine assignment, I decided to create a funny, playful game for the purpose of entertainment where the player is given the role of a hungry college student. There are multiple paths to the game, but there is ultimately only one path that leads to the “win” passage of the game (when the player gets to eat). If the players choose the wrong option, they will restart the game from the beginning.

When I first started to create the game, I thought Twine was a very easy program to utilize. However, that all changed when I was attempting to make the game more complex with the use of stylesheets and coding in the passages. The use of stylesheet was very frustrating and confusing for me. There was a lot of trial and error involved when I was attempting to change the look of the game to something other than the plain default look. After many failed attempts, I decided to use a piece of code that another user had created and modify the code to give the game the look I desired.

The idea of the GNU Manifesto is relevant to the creation of games through Twine. The creator of a Twine game has the freedom to modify the program any way he or she desires (as long as the coding allows them to) to create a game. The creators can also freely redistribute and share the code they used to input into the program.