{"id":2788,"date":"2026-02-12T21:59:10","date_gmt":"2026-02-12T21:59:10","guid":{"rendered":"https:\/\/sites.wsagames.com\/jr16g23\/?page_id=2788"},"modified":"2026-05-18T23:12:27","modified_gmt":"2026-05-18T23:12:27","slug":"sprint-four","status":"publish","type":"page","link":"https:\/\/sites.wsagames.com\/jr16g23\/sprint-four\/","title":{"rendered":"Sprint Four"},"content":{"rendered":"\n

27\/04\/2026-21\/05\/2026<\/p>\n\n\n\n

Wrapping up<\/strong><\/p>\n\n\n\n

The final sprint is finally here! although it’s gone by so quickly, there’s only a few more changes that need to be made and it’s done!<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

During our first class back after Easter, Izzy and I made a list of things that need to be completed by submission. The longest list in the top left. It looks like a lot, however these are all really small fixes\/implementations (which is why I’ve given myself 2 weeks to complete this).<\/p>\n\n\n\n

\n\n\n\n

\u2726\u2022\u2508\u0e51\u22c5\u22ef Week Ten \u22ef\u22c5\u0e51\u2508\u2022\u2726<\/strong><\/h4>\n\n\n\n

My task for this week is to replace old assets with new ones Izzy created, such as the new environments. I also need to begin adding in the voice lines for the player.<\/p>\n\n\n\n

Replacing 3D environments<\/strong><\/p>\n\n\n\n

\n
\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n<\/div>\n\n\n\n
\n
\"\"<\/figure>\n\n\n\n
\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n

Because Izzy wasn’t as confident texturing all the environments she added some colour to the existing assets to make it look less grey boxed. After she made them I replaced the old models with these. This was an easy task as I just had to put them in the same place as the last ones.<\/p>\n\n\n\n

The one that was slightly difficult has I had to add it as a texture so it would show up as CCTV footage but luckily I could just replace the old texture. This wasn’t something covered in any tutorial I’d looked at. I had to reframe the problem entirely, treating the environment as a texture rather than a model. Finding an unconventional solution independently, rather than following a prescribed method, is something I’d consider one of my stronger examples of innovation this semester.<\/p>\n\n\n\n

Player voice lines<\/strong><\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

Cutting up the voice lines was easy, however it was very time consuming so it took me a few hours to complete this and organise them properly but I managed to do it! To do this I used an app called Audacity which I had never used before, but the controls were easy to learn.<\/p>\n\n\n\n

I chose Audacity to cut and export the voice lines as it’s free and, despite never having used it before, the controls were intuitive enough that I was able to pick it up quickly without it eating into my production time. For what I needed, trimming clips and exporting them in the right format, it had everything required without any unnecessary complexity.<\/p>\n\n\n\n

\n
\n
\"\"<\/figure>\n<\/div>\n\n\n\n
\n
\"\"<\/figure>\n<\/div>\n<\/div>\n\n\n\n

Once I exported them I compressed them to a zip file to organise them better, and dragged them into my player folder in Unity.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n

Implementing the lines in the code itself was pretty straightforward, I had to make a reference to it in my AudioManager script where I could then implement instance lines below the narrative line matching it. <\/p>\n\n\n\n

It worked straight away after testing, however all the lines would overlap when the lines were skipped so I added a WaitForVoicedDialogue() line below each one. This stopped the voice lines overlapping completely. This was a problem I hadn’t anticipated and there was no direct solution I could find online. I had to figure out that the fix needed to sit at the code level rather than the audio level, which required me to think through how the dialogue and audio systems were interacting with each other before I could solve it.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

I repeated the same steps with all four scripts and then drag and dropped the audios in the right place. All of it worked perfectly until I got to case fours script. <\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

As you can see in the picture above, I ended up having to trial and error where each line had to go as I think I may have miscounted. This slowed down a lot of my production as it was very time consuming but I managed to fix the majority of it!<\/p>\n\n\n\n

There is still one part in scene 4 that says the wrong line at the wrong part but unfortunately I did not have time to figure out the problem so I continued with more important things in the game. <\/p>\n\n\n\n

\n\n\n\n

\u2726\u2022\u2508\u0e51\u22c5\u22ef<\/strong> Week <\/strong>Eleven \u22ef\u22c5\u0e51\u2508\u2022\u2726<\/strong><\/h4>\n\n\n\n

Creating the endings<\/strong><\/p>\n\n\n\n

Using the endings I wrote I began to implement them in the case 4 script. Originally there was supposed to be six endings, but after calculating what each risk outcome could take you to, it wasn’t possible to reach a low risk ending. This resulted in me cutting this out entirely. <\/p>\n\n\n\n

\n
\n
\"\"<\/figure>\n<\/div><\/div>\n\n\n\n
\n
\"\"<\/figure>\n<\/div><\/div>\n<\/div>\n\n\n
\n
\"\"<\/figure>\n<\/div>\n\n
\n
\"\"<\/figure>\n<\/div>\n\n
\n
\"\"<\/figure>\n<\/div>\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n

The endings are all contained in my scene 4 script and triggered by a single enum called FinalChoice, which can be Archive, PublishNow, or Stop. When the player hits one of the three buttons on the final decision panel, OnFinalDecision() fires, adds the appropriate risk value, hides the panel, and hands off to the relevant coroutine.<\/p>\n\n\n\n

The most complex branch is Option A. Rather than one ending, it routes into three different coroutines: EndingA_MidRisk(), EndingA_HighRisk(), and EndingA_MaxRisk(). These are based on the player’s total accumulated risk at that point. The risk thresholds are checked inside Ending_ReleaseFullArchive() right after the +15 risk from choosing Archive is added, which means a player right on the edge of a threshold can tip into a harder ending just by making that final choice.<\/p>\n\n\n\n

Each ending coroutine is a linear sequence of yield return calls including dialogue lines, camera swaps, fade ins, and audio triggers all chained together. For example, the max risk ending opens on Frank’s unfinished email with a blinking cursor running as a separate coroutine (BlinkCursor()), plays three narration beats, then calls PanCameraToTV() which shifts the camera across to Marie’s press conference playing on a screen in the corner.
The high risk ending uses AnimateFrankInbox() to populate Frank’s email inbox row by row in real time, each one triggering an email notification sound, building up the picture of everyone trying to reach someone who isn’t there anymore.<\/p>\n\n\n\n

Ending C has an interactive moment before the rival newspaper reveal. The player has to physically click the recycle bin to delete the files themselves. The recycleBinClicked boolean is set by the button, and the coroutine sits in a WaitUntil loop until it flips. That was a deliberate choice to make the player own the action rather than just watch it happen.<\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

All three endings feed into the same ShowCredits() coroutine at the end, which fades in the credits panel and waits eight seconds before the game considers itself complete.<\/p>\n\n\n\n

Creating the documentary and trailer <\/strong><\/p>\n\n\n\n

\n