MediQuest

When I first worked on the dialogue system, it was just a simple 1D array storing all the dialogues. With the introduction of the save/load mechanism and more storylines coming up, the leader and I decided to come up with a hierarchical dialogue system which allows dialogues to act as checkpoints, thus users can pick up from where they left off.

I wrote a small algorithm that allows the programmers to input the storyline and let the program sort out how they can be stored as dialogues in the hierarchy. Storing in a hierarchy meant that when we switch scenes, it allows dialogue to be temporarily saved and thus, can continue the game from the last scene. Also, when a player quits and resumes again, the hierarchy can retrieve the last checkpoint.

I worked on two aspects of patient documentation: a patient chart and a test chart. A patient chart involved different sectors which are related to other parts of the game. For example, a function of patient chart is to order tests for patients which is done via a test chart.

Actions from test chart have to be stored correctly so the doctor can order the correct tests. This whole process required understanding of the relationship between different components of the game and made me read all the code related to the charts. The same thing applied when I had to extract data from the patient to fill up the charts.