Text

• Pikkis

#System

#Gameplay

#Group

#RTS

Details

System Designer

Gameplay Designer

UX/UI Designer

AI behavior will be the best!

After defining our game’s core pillars, I have begun designing unit behavior for both close- and long-range combat scenarios.The first challenge was creating functional behavior—units often ended up stuck in loops.That is why I found myself diving headfirst into crunching (I know, not my proudest moment—but I was so excited (੭˃ᴗ˂)੭ !) just to get us playtesting as soon as possible.

Let the fruits fight (๑•̀ᗝ•́)૭

Speaking of combat scenarios, this might have been my favorite part of the project—mostly because it was both fun and relatively easy to work on.The difficulty progression was continuously refined until the deadline to ensure a smoother challenge curve and better unit introductions for the player.I loved brainstorming all possible scenarios and outcomes (but of course, nothing can replace playtesting!!!).

Traumatic control scheme

One situation I’ll never forget was deciding on a gamepad control scheme.I don’t typically play shooter games with a gamepad. Naturally, I came up with an "innovative" control scheme that (in my opinion) would be intuitive for beginners… but no one on the team agreed with it.In the end, I had to let go of my idea and revise it, but it was a valuable learning experience
ᕙ( •̀ ᗜ •́ )ᕗ

I swear Excel is fun ദ്ദി ˉ͈̀꒳ˉ͈́ )✧

Excel was incredibly useful for balancing unit stats, including regular attacks and special abilities — especially given their rock-paper-scissors relationships.Tbh it had been a while since I last used Excel, and it felt great to dive back in — even if I had to google every function ദ്ദി ༎ຶ‿༎ຶ)

Our game is ... boring (˶°ㅁ°) !?

When you work on something for too long, your perspective becomes blurred — exactly what happened to me. After playtesting and Jury's feedback on alpha, I realized we’d overlooked many things.
That made design meetings longer and a bit stressful.We managed to solve the biggest design issues by adding a second resource pool and player attack with a cooldown, which made a huge difference in the gameplay loop.

Endless iterations on UX/UI

Because the gameplay and systems kept improving, I constantly was updating the UX/UI. Every week, we rolled out a new version of the layout or adjusted button functionality to match the evolving design.Thank Harsh Istalkar for his patience and for helping me tackle all the technical aspects of it. His support made navigating these constant changes so much easier! (๑'ᵕ'๑)⸝*

Observer effect simulator

Here’s a fun fact I discovered while tweaking the units’ stats: the combat outcomes were sometimes so unpredictable that I started questioning whether we were building a game or a physics simulator. (,,•᷄ࡇ•᷅ ,,)?Turns out, it was just a bug in the blueprints!

Patryk Aleksandrowicz

Product Owner, Narrative/Gameplay Designer

Anna Tsoy

Gameplay/System Designer, UX/UI Designer

Erik Lofving

Level Designer

Andie Larsson

Technical Designer, 3C Designer

Robin Zeitlin-Talamo

Lead Gameplay Programmer

Markus Vikmanis

Gameplay/Sound Programmer

Harsh Kashinath Istalkar

Gameplay Programmer, Technical Artist

Eero Mutka

AI Programmer

Ambar Troya Zapata

Concept/Character Artist, UI Artist

Vera Jonasson

Environmental Artist, Composer

Wilma Wiiand

Animator

Frode Nilsson

Animator

Karl Lindblom

VFX Artist

Morris Levin

VFX Artist

Text

• Pikkis

• Pikkis

• Sour Security

#System

#Multiplayer

#Prototype

#Brawler

Details

Server ❤︎ Client

I’ve been curious about how multiplayer works.So, I decided to dive in and learn about replication, authority, and how the server handles game logic while clients interact with the world.

• Blueprints

Rapid prototyping

Once I felt more comfortable with Blueprints in Unreal Engine 5, I tried rapid prototyping.I wanted to quickly turn ideas into functional gameplay, focusing on iterating and testing core mechanics without getting bogged down in perfection.

3D art /ᐠ•⩊•マ

For 2D artist (me) starting 3D modeling always sounded a bit intimidating.But for this project, I finally decided to step out of my comfort zone and try creating a 3D character myself.

Knock it!

For this quick and fun prototype, I took inspiration from cats knocking things off tables — but with a twist! /ᐠ. .ᐟ\ฅInstead of objects, players have to knock each other off. It adds a playful and competitive element, making it fast-paced and chaotic.

Why can't I replicate it? (≖_≖ )

During prototyping, I ran into some unexpected blockers.My original plan was to set random materials to all players, but material replication turned out to be more frustrating than I expected.I explored a few possible solutions, but due to time constraints, I went with a quick fix—spawning a random child of the player character instead.
_{P.S. It wasn’t the most elegant solution, but hey, if it works, it works!}

From concept to rigging /ᐠ｡‸｡ᐟ\ ⟆

For concept art, modeling, retopology, UV mapping, and texturing, I used an iPad, which was surprisingly effective for the entire workflow. The only time I needed to switch to Blender was for rigging.It was a fun challenge to see how far I could go using just an iPad, and it proved to be a great way to work on 3D art in a more flexible and portable way!

• Pikkis

• Sour Security

• Reberryon

• Mitti Kitti

#System

#Gameplay

#Prototype

#Sandbox

Details

How to move and rotate things around （╯‵□′）╯︵┴─┴

I started improving my technical skills about five months ago.
One of my first tasks was to learn and understand how rotators and vectors work, as they are fundamental to game development.I had some basic knowledge from high school, but applying math to game development was a bit confusing. However, it didn’t take me too long to grasp the concepts and create this prototype.

NO casting!

This project was part of the Advanced Visual Scripting course, where one of my biggest challenges was to avoid casting at all costs.This constraint pushed me to explore new concepts, such as Components, Function Library, and various useful nodes, ultimately deepening my understanding of visual scripting. ( ◡̀_◡́)ᕤ

What is TDD ∘ ∘ ∘ ( °ヮ° ) ?

This exercise allowed me to visualize the project architecture, practice translating abstract ideas into actionable steps, anticipate potential challenges, and streamline the development process by providing a solid foundation.Additionally, the Technical Design Document served as an easy introduction for others to my architecture, making it simpler to ask for advice or assistance when needed.

What does Link's Ultrahand have to do with this?

Right before starting the Advanced Visual Scripting course, I was playing Zelda: Tears of the Kingdom and was inspired by one of its core mechanics — Ultrahand, which allows players to grab, rotate, and attach objects together.Using this as my main reference, I designed my interactive system, which also lets players scale grabbed objects up and down.

• Blueprints

Blessing refactoring

One of my first mistakes was separating all interactions into different functions within a single component, which turned out to be unnecessary and a major blocker. ( ,,⩌'︿'⩌,,)Another mistake I made with the grabbing interaction was using Physics Handle component, which didn’t allow me to rotate objects relative to the player's axis. Instead, I switched to working directly with Scene Component, which gave me much more control.

Just a bug that brings so much joy (๑˃́ꇴ˂̀๑)

A spawner for interactable objects accidentally ended up with a confetti effect instead. Some people loved it so much that I decided to keep it as a separate feature.Warning! It might crash your PC — don’t try this at home!
_{P.S. The spawners have been fixed and now work perfectly fine.}

Potential development 🍰 (∩❛ڡ❛∩)

A first-person cute café arrangement game?
That sounds cozy and addictive! It will need some adjustments, polishing, and new mechanics, but it might be worth it.
For example, creating an inventory system for it can be fun and rewarding challenge!

Me

• Viktor Ganzha

(Level designer)

Edvard Stokstad
(Level Designer)

Lucas Hellberg
(System gameplay designer)

Mukund Narayan
(System gameplay designer)

A special thanks to

• Isak Åslund (technical designer)

for his valuable advice and guidance

• Reberryon

• Mitti Kitti

Soft

Hard

Collision Designer

Details

Product Owner

Gameplay Designer

UX/UI Designer

Anna Tsoy

Product Owner
Gameplay Designer
UX/UI Designer

Jan Björk

Lead Gamplay Designer

Emil Bernstorf

Level Designer

Hanna Wedmalm

Level Designer

Oscar Rosin

TechnicalDesigner

Kamila Kuźmiuk

Gameplay Programmer

Stevan Likusic

Gameplay Programmer

Vui Kent Chua

Lead Gameplay Programmer

Jonathan Ebsen Mäensivu

Systems Programmer

Tim Lindgren

QA

Mia Wall

Character Artist
Scrum master

Primus Engström

Environment Artist

Francesco Ortolani

Environment Artist

Jacob Segerdahl

Environment Artist
UI Artist

Melissa Prim

Environment Artist

• Mitti Kitti

#Group

#Gameplay

#Prototype

#Sandbox

Details

UX/UI Designer

Gameplay Designer

Technical designer

!!! ONE of the thee prototypes for this Game Project !!!

Three designers split up to explore different ideas for the "Antagonist" theme. One of the prototypes for Game Project 4 was Ogami, where I designed a boss fight-centered concept with response system based on the player's actions.

• Blueprints

"Adaptive" enemies

To create the illusion of smart enemy behavior, I designed a simple prototype for the system that tracks the player's actions during combat and applies specific changes to the next boss encounter.I also focused on establishing the core mechanics: 3Cs, player close-/long-ranged attacks, and a simple enemy AI for the first encounter.

Things to count ( ͡⎚— ͡⎚ )>✎

Why it is a good and BAD idea for our team (ó﹏ò｡)

+ Challenge: opportunity for designing complex progression systems
- Complexity: too many things to balance and make it work in time
- Novelty: not enough references to other games
- Iteration: not enough time to polish
- Skills: not enough C++ experience

Ok, let's see what I can do for the system here

Once the prototype was complete for the chosen concept (Sour Security), I began setting scenarios, and player's goals, also organizing everything to ensure it functioned within a unified system and that we had all the necessary elements.

Create gameplay problems and heroically overcome them

To maintain that sandbox feel and total freedom for the player, we,
as designers, ended up losing some control over certain elements.For example, with the limited level and so many mechanics for the player to grasp, the onboarding process itself starts to feel like
a boss-level challenge even with all the step-by-step guiding! \ (˚☐˚”) /

NPCs

Setting up NPC routes was a bit tricky, especially with the limited
open-space office layout. I had to make sure they actually looked like they were "working" at the office rather than just wandering aimlessly. (๑﹏๑)At the same time, their paths couldn’t overlap too much — otherwise, the player wouldn’t have the chance to knock them out without witnesses or find the perfect moment to hide their unconscious colleagues.

Multiple other hats 皿

Designed the minimalistic UI/UX with a clean interface while still providing all the necessary information to the player without overwhelming the screen.In addition to development tasks, I also worked on creating marketing materials to promote the game. This included designing posters, the gameplay trailer, and ensuring the visual identity aligned with the game's theme.For a week, I stepped into the role of Product Owner. I was responsible for prioritizing tasks, ensuring smooth communication between teams, and keeping the project aligned with its goals.

Alexander Busnyuk

Product Owner, Technical/System Designer

Anna Tsoy

Gameplay/System Designer, UX/UI Designer

Oscar Rosin

Technical Designer

Reyn Teru

Level Designer, Narrative Designer

Harsh Kashinath Istalkar

AI/Systems/Gameplay Programmer, Technical Artist

Jonathan Ebsen Mäensivu

Systems Programmer

Stevan Likusic

Systems Programmer

• Mitti Kitti

#Solo

#Level

#Narrative

#Coding

Details

First ever game project ٩(ˊᗜˋ*)و ♡

This project was part of the Introduction to C# course at Futuregames.Beyond learning the fundamentals of coding, I wanted to explore gameplay design — defining win and lose conditions, player motivation, level design, and narrative storytelling. I was particularly interested in how games communicate with players and evoke emotions, shaping their experience through mechanics and design choices.

A charming mix of adorable and eerie (˚ ˃̣̣̥⌓˂̣̣̥ )

Narrative, level design, and sound design were the core of this project.The touchy story provided emotional depth, while the level design ensured a balance of challenge and exploration, and the sound design reinforced the atmosphere to enhance tension.

Update level design

The level went through multiple iterations throughout the project, evolving from two simple rooms into a sprawling dungeon labyrinth.Each room was carefully designed to feature unique obstacles, adding variety and challenge while encouraging exploration and strategic thinking. ( • ̀ω•́ )✧

Potential development

I considered expanding this project into a larger game with deeper lore, additional side quests, more refined stealth mechanics, better sound design, and multiple levels. /ᐠ > ˕ <マ ₊˚⊹♡The goal would be to enhance player immersion by offering a richer narrative experience, greater gameplay variety, and more complex challenges.

#Solo

#FPS

#Prototype

#Kid

Details

3Cs for FPS

One of the requirements for the Prototyping course at Futuregames was to work within the FPS genre. ̸/̸̅̅ ̆̅ ̅̅ ̅̅ Since I don’t typically play FPS games, recreating 3Cs was a challenge and an opportunity to step out of my comfort zone and learn something new.

All grown-ups were once children… ʕ´•ᴥ•`ʔ

I'm not a big fan of violence, so I wanted to create an FPS with the playful, mischievous vibe of Untitled Goose Game or Rain on Your Parade.Instead of taking down enemies, the goal is to annoy them in the most wholesome way possible—by shooting plushies at them and spreading happiness!