{"id":60,"date":"2025-02-09T15:33:07","date_gmt":"2025-02-09T22:33:07","guid":{"rendered":"https:\/\/blogs.ubc.ca\/quinn540\/?page_id=60"},"modified":"2025-02-09T16:25:05","modified_gmt":"2025-02-09T23:25:05","slug":"task-5","status":"publish","type":"page","link":"https:\/\/blogs.ubc.ca\/quinn540\/task-5\/","title":{"rendered":"TASK 5"},"content":{"rendered":"

Task 5:<\/span><\/h1>\n

Twine Task<\/span><\/h1>\n

Access my Twine: Monday at the Office<\/a><\/span><\/h3>\n

\"\"<\/p>\n

I enjoyed this task. It was my first time working with Twine, and I noticed that my approach to story writing was different due to the type of story I was writing (choose-your-own-adventure) and the tool I was using to tell it (Twine).<\/span><\/p>\n

When it came time to draft my fiction game, I wasn’t feeling particularly inspired or creative. I knew I wanted to begin with a general outline that contained several different paths and that I wanted my story to center around an office setting, so I used Copilot to draft my outline using the following prompt:\u00a0<\/span>“Create an outline for a choose-your-own-adventure story set in an office with a missing lunch.”\u00a0<\/strong><\/span>View the full response from Copilot HERE<\/a>.<\/span><\/p>\n

I thought it would be best to draft my entire story and all the various paths separately in Word, then cut and paste the finished product into Twine. However, having never used Twine before, I downloaded Twine after Copilot generated my outline and started experimenting. Instead of returning to Word to write the story, I did all my drafting and editing in Twine. I found this easier because there was a visual representation of all the connections and links as they were being created. I didn’t work linearly, as I had done in previous story and game writing experiences, but I did a lot of jumping back and forth between the various story pathways.<\/span><\/p>\n

Task 5 offered a great activity to highlight hypertext. My fictional game was reminiscent of a printed story in structure and objective; however, introducing hypertext that allows the reader to actively choose how to progress changing their relationship to the text and their overall experience. As Bolter (2001) acknowledges, hypertext doesn’t replace traditional print but relies on it while altering it. In some ways, I can see how hypertext, allowing for fluid exploration between ideas and text, may more accurately reflect the human thought process. However, I can also agree with the arguments that traditional printed text is more natural based on how it can be interacted with (Bolter, 2001).<\/span><\/p>\n

Reflecting on hypertext, I couldn’t help but consider how overwhelming all the options and connections can sometimes feel. There is something comforting about a body of work with a definitive beginning and end. A sense of completion or finality, even if it is false and there is more to explore. In most instances, exploring every link or all facets of a topic is impossible, but that doesn’t stop me from feeling like all links should be explored or something might get missed. I recall a similar feeling reading choose-your-own-adventure books as a child. I often wondered which was the “right” ending to the story and if I had selected the “correct” options when, in reality, a correct option or singular story path was nonexistent and never intended.<\/span><\/p>\n

References<\/span><\/h5>\n

Bolter, J. D. (2001). Hypertext and the remediation of print. In Writing Space: Computers, Hypertext, and the Remediation of Print<\/em><\/span>. https:\/\/doi.org\/10.4324\/9781410600110<\/a><\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Task 5: Twine Task Access my Twine: Monday at the Office I enjoyed this task. It was my first time working with Twine, and I noticed that my approach to story writing was different due to the type of story I was writing (choose-your-own-adventure) and the tool I was using to tell it (Twine). When […]<\/p>\n","protected":false},"author":92151,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-60","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/blogs.ubc.ca\/quinn540\/wp-json\/wp\/v2\/pages\/60","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blogs.ubc.ca\/quinn540\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/blogs.ubc.ca\/quinn540\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.ubc.ca\/quinn540\/wp-json\/wp\/v2\/users\/92151"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.ubc.ca\/quinn540\/wp-json\/wp\/v2\/comments?post=60"}],"version-history":[{"count":8,"href":"https:\/\/blogs.ubc.ca\/quinn540\/wp-json\/wp\/v2\/pages\/60\/revisions"}],"predecessor-version":[{"id":78,"href":"https:\/\/blogs.ubc.ca\/quinn540\/wp-json\/wp\/v2\/pages\/60\/revisions\/78"}],"wp:attachment":[{"href":"https:\/\/blogs.ubc.ca\/quinn540\/wp-json\/wp\/v2\/media?parent=60"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}