top of page

Nicholas Galjanic

Email: Ngaljanic@gmail.com

Phone: 631-901-7292

Back to Portfolio

Create Your First Project

Start adding your projects to your portfolio. Click on "Manage Projects" to get started

.pro-gallery-wix-wrapper {display: block !important;} .pro-gallery-wix-wrapper .gallery-item-container {opacity: 1 !important; display: block !important;}

Gameplay Programming Showcase

Places where I have worked directly on gameplay design and programming.

A user-facing data visualization tool which tracks gameplay stats in our HELO gamemode.

A user-facing data visualization tool which tracks gameplay stats in our HELO gamemode.

I was responsible for developing our character creation system, which includes controls for skin color, body type, and other customization options. Besides the UI, I also created the gameplay system itself, such that the player is given a "doll" copy of their character to view pending choices, which are copied onto their official character upon purchasing the change. We built a smaller version of the level where this system is available and manipulated the "doll" character to animate in specific areas depending on the nature of the customization the player was making (i.e., standing position for body customization, sitting for more facial-oriented customization)

I was responsible for developing our character creation system, which includes controls for skin color, body type, and other customization options. Besides the UI, I also created the gameplay system itself, such that the player is given a "doll" copy of their character to view pending choices, which are copied onto their official character upon purchasing the change. We built a smaller version of the level where this system is available and manipulated the "doll" character to animate in specific areas depending on the nature of the customization the player was making (i.e., standing position for body customization, sitting for more facial-oriented customization)

I was responsible for developing our character creation system, which includes controls for skin color, body type, and other customization options. Besides the UI, I also created the gameplay system itself, such that the player is given a "doll" copy of their character to view pending choices, which are copied onto their official character upon purchasing the change. We built a smaller version of the level where this system is available and manipulated the "doll" character to animate in specific areas depending on the nature of the customization the player was making (i.e., standing position for body customization, sitting for more facial-oriented customization)

I was responsible for developing our character creation system, which includes controls for skin color, body type, and other customization options. Besides the UI, I also created the gameplay system itself, such that the player is given a "doll" copy of their character to view pending choices, which are copied onto their official character upon purchasing the change. We built a smaller version of the level where this system is available and manipulated the "doll" character to animate in specific areas depending on the nature of the customization the player was making (i.e., standing position for body customization, sitting for more facial-oriented customization)

For most game mechanics in our game, I was responsible for the tutorials which appeared on screen as well as the system which determines whether they're needed and stores their saved state, if applicable.

For most game mechanics in our game, I was responsible for the tutorials which appeared on screen as well as the system which determines whether they're needed and stores their saved state, if applicable.

In our Expeditions gamemode, we have a "wiki" that contains relevant information for the given scenario. In developing this feature, we had multiple simultaneous needs of the text feature: "hyperlinkable" words with glossary descriptions, clickability for selecting to populate a form, and highlighting. To achieve this, I had to investigate the rich text block system as it exists in UE4's engine code and create alternative RichTextBlockDecorator classes that could support this functionality.

In our Expeditions gamemode, we have a "wiki" that contains relevant information for the given scenario. In developing this feature, we had multiple simultaneous needs of the text feature: "hyperlinkable" words with glossary descriptions, clickability for selecting to populate a form, and highlighting. To achieve this, I had to investigate the rich text block system as it exists in UE4's engine code and create alternative RichTextBlockDecorator classes that could support this functionality.

Research Activity

Research Activity

This is our Punnett Square minigame, in which the player must swap randomly placed gene cards to their correct positions to solve the puzzle before the time limit ends. All game mechanics are handled in the UI which I built.

This is our Punnett Square minigame, in which the player must swap randomly placed gene cards to their correct positions to solve the puzzle before the time limit ends. All game mechanics are handled in the UI which I built.

I was responsible for all of the UI involved in the minigames in our Expeditions gamemode.

In this case, the player has to scan inside of the Drakon and find select points to gather data. Those points are visualized here in a debug capacity, and are generated based on pre-placed sockets on the skeletal mesh of the creature.

For this mechanic, I had to implement a shader which allows the player to look at the skeletal structure of the drakon in an X-ray format. The size of the scanning tool around the cursor is used to configure the radius of the x-ray portion of the shader. I did not want to use an event tick-based system for detecting when the player was hovering over a point, so I created a UI system involving multiple canvas panel widgets which slide past each other in order to take advantage of UMG's OnMouseEnter events and keep the activity optimized as a ressult.

I was responsible for all of the UI involved in the minigames in our Expeditions gamemode.

In this case, the player has to scan inside of the Drakon and find select points to gather data. Those points are visualized here in a debug capacity, and are generated based on pre-placed sockets on the skeletal mesh of the creature.

For this mechanic, I had to implement a shader which allows the player to look at the skeletal structure of the drakon in an X-ray format. The size of the scanning tool around the cursor is used to configure the radius of the x-ray portion of the shader. I did not want to use an event tick-based system for detecting when the player was hovering over a point, so I created a UI system involving multiple canvas panel widgets which slide past each other in order to take advantage of UMG's OnMouseEnter events and keep the activity optimized as a ressult.

This is a minigame which I constructed for our Expeditions gamemode. Blood cell image widgets are generated based on the white and red blood cell counts of the animal being scanned. These widgets are then gradually scrolled to the right side of the screen, where the player must manually click on and count them in order to finish the minigame. If a cell moves off screen, it rewinds to make them click it. If the player is able to click them very quickly, they increase in speed. Click visibility is toggled off for irrelevant widgets, so that we can maintain separate red and white blood cell phases.

This is a minigame which I constructed for our Expeditions gamemode. Blood cell image widgets are generated based on the white and red blood cell counts of the animal being scanned. These widgets are then gradually scrolled to the right side of the screen, where the player must manually click on and count them in order to finish the minigame. If a cell moves off screen, it rewinds to make them click it. If the player is able to click them very quickly, they increase in speed. Click visibility is toggled off for irrelevant widgets, so that we can maintain separate red and white blood cell phases.

This is our Argument Builder mechanic. The player must choose a hypothesis and then prove it to the NPC using modular evidence pieces and logical "bridge" words. Cards can be clicked and dragged, hypotheses swapped, and past arguments are stored on the right hand side, so this mechanic involves frequent communication with the C++ networking backend for configuring activity parameters and displaying feedback.

It's worth mentioning that the NPC picture here is a render target texture "broadcasting" a live-animating image of the character from a render capture component inside of a "model viewer" actor, which is something that I created the systems for.

This is our Argument Builder mechanic. The player must choose a hypothesis and then prove it to the NPC using modular evidence pieces and logical "bridge" words. Cards can be clicked and dragged, hypotheses swapped, and past arguments are stored on the right hand side, so this mechanic involves frequent communication with the C++ networking backend for configuring activity parameters and displaying feedback.

It's worth mentioning that the NPC picture here is a render target texture "broadcasting" a live-animating image of the character from a render capture component inside of a "model viewer" actor, which is something that I created the systems for.

This gameplay system allows the player to add and customize an air mass for use in their planet's climate simulation. I created the interface and system which places and scales the air mass on the planet, controlling the visibility and visualization of other pre-placed air masses to de-clutter the experience.

This gameplay system allows the player to add and customize an air mass for use in their planet's climate simulation. I created the interface and system which places and scales the air mass on the planet, controlling the visibility and visualization of other pre-placed air masses to de-clutter the experience.

.pro-gallery-wix-wrapper {display: block !important;} .pro-gallery-wix-wrapper .gallery-item-container {opacity: 1 !important; display: block !important;}

bottom of page