Game Design Gallery

Billy Saves the World

Assisted with boss battles, portions of map construction, minigames, mission progression, and puzzle design.

Boss Battles Context All three encounters inspired by Space Invaders were assembled and adjusted to refine gameplay flow and visual timing. Highlight Pre-programmed movement and firing patterns were activated and fine-tuned to keep enemie

Boss Battles

Context

All three encounters inspired by Space Invaders were assembled and adjusted to refine gameplay flow and visual timing.

Highlight

Pre-programmed movement and firing patterns were activated and fine-tuned to keep enemies within the camera frame. Counter logic was added to track how many times enemies were damaged by being jumped on. Difficulty increased gradually by speeding up enemy actions. Cutscenes were also created to introduce, accompany, and conclude each fight.

Invite

The screenshot above shows the initial moment before Bleep and Bloop begin their descent. They are about to shift into formation and start sweeping side to side across the screen. As they do this, they will rain down bullet on the player who is seen standing below.

Maps Context The editor was occasionally used to shape the layout of various stages. In this case, the director requested a level that required close observation and memory in order to complete it. Highlight After producing a few rough sket

Maps

Context

The editor was occasionally used to shape the layout of various stages. In this case, the director requested a level that required close observation and memory in order to complete it.

Highlight

After producing a few rough sketches to establish ledge placement, a basic white-box layout was constructed. The design loosely followed a grid where each column gradually ascended, creating a sense of vertigo as the player progressed. Logic was added so that pressing a button would zoom the camera out, revealing the full view of possible paths. From left to right, one ledge in each column would glow, showing the correct sequence the player needed to remember to reach the goal. This pattern was randomly generated each time to keep the experience different across attempts. If the player stepped on an incorrect ledge, all others would disappear and they would fall, forcing a restart of the puzzle section.

Invite

The screenshot above shows the final version of the level. At this moment, the top platform in the second column is glowing. The entire colour palette and the meteorites in the background were added later by another team member.

Minigame Context The task involved creating a subgame where the player enters a simulated reality space for a brief period. This was an opportunity to experiment creatively while working within the limits of existing assets and mechanics. Hig

Minigame

Context

The task involved creating a subgame where the player enters a simulated reality space for a brief period. This was an opportunity to experiment creatively while working within the limits of existing assets and mechanics.

Highlight

Since the main game featured many references to retro video games, it made sense to design the subgame in a similar style. Given the limited time, inspiration was drawn from the eight-bit era. The currently implemented boss fights already focused heavily on the top portion of the screen, so it felt natural to shift attention to the bottom. The gameplay was influenced by Missile Command, but with a unique spin. Three bases were coded for the player to defend against falling threats. By using existing running and sliding mechanics, the player could move between the bases, each of which could fire rockets. These incoming objects spawned at random positions and targeted the bases. Destroying all of them allowed the player to move on to the next wave, where difficulty increased as falling speed accelerated.

Invite

The screenshot above shows the player in the middle of the subgame. The four blocks at the bottom, shaped similarly to pieces from Tetris, represent the bases, each equipped with a turret. A grid overlay was added to help align incoming meteorites with their corresponding base. Several meteorites have already spawned above and are falling straight down.

Mission Progression Context All necessary variables were created within the editor to maintain consistency throughout gameplay. This included managing the ones responsible for updating the player’s to-do lists which tracked objectives for both

Mission Progression

Context

All necessary variables were created within the editor to maintain consistency throughout gameplay. This included managing the ones responsible for updating the player’s to-do lists which tracked objectives for both main and side quests.

Highlight

Variables were implemented to monitor actions and choices across the game. Since the experience was set in an open-world role-playing environment with frequent backtracking and branching paths, these values ensured that events stayed consistent. Many tracked dialogue choices, while others controlled the appearance of world assets such as gaining access to a new area. For example, if a bridge was activated, it would remain accessible even upon returning later. Additionally, logic was used to trigger notification messages that helped guide the player to their next goal, based on decisions made within specific quest lines.

Invite

The screenshot above shows the to-do list found within the player’s inventory interface. At the top is the current main quest, Anniversary Date, with each completed step listed beside it. Side quests and completed tasks appear in separate sections below.

Puzzles Context Contributed to assembling all logic tests found throughout the game. Most were built by creatively repurposing existing assets to reduce the workload for backend programmers. Highlight One sequence involved the player being

Puzzles

Context

Contributed to assembling all logic tests found throughout the game. Most were built by creatively repurposing existing assets to reduce the workload for backend programmers.

Highlight

One sequence involved the player being trapped and needing to escape a locked cell through one of two approaches. The first was a hidden vent in the ceiling, which required careful observation and platforming. The second relied on using a special ability to activate a wall switch. To do this, the only moveable asset compatible with the force push was reused. It was made invisible and strategically placed nearby. Area triggers were positioned around it to detect if it moved. Once displaced, the mechanism would activate and the cell door would open.

Invite

The screenshot shows the player inside the cell with a non-playable character. On the wall is a switch with a red handle. This marks the location of the invisible interactive object.

Return to Previous Page Section