Magicaffeine

Magicaffeine is a fantasy coffee-shop simulation game. Craving the familiar comfort of coffee in a magical world, you discover the local brew is dull and bitter. Determined to introduce real coffee craft, you open your own shop to introduce something new and real one.

Executive Summary & Role

As the Lead Artist & Technical Artist, I stepped into a multi-disciplinary team of artists, game designers, and programmers to bring this cozy magical brew-house to life.

My job wasn’t just drawing cute coffee cups and fantasy ingredients. I was responsible for establishing the entire art pipeline: unifying multiple illustrators who had completely different art styles, setting up asset standards for Unity, and creating a workflow so programmers wouldn’t sit around with their hands tied waiting for final artwork.

It was an exercise in turning creative artistic chaos into a smooth, well-oiled game development machine.

Key Features

Order Matching System: Customers arrive with distinct tastes and magical quirks; players must pick the correct cups, bases, and brewing recipes to satisfy them.
Ingredient Mixing Mechanics: Intuitive drag-and-drop brewing where balancing ingredients alters flavor profiles and customer stat boosts.
Dynamic Scoring System: Evaluates customer satisfaction based on brewing accuracy, serving speed, and visual presentation.
Cohesive Visual Identity: A unified, warm fantasy cafe aesthetic brought together from multiple distinct illustrators.

The Problem & The Solution

The Problem:

Clashing Art Styles: When you have multiple illustrators on a team, everyone naturally draws with their own flair. Left unchecked, the game would look like five different games mixed together.
Technical Knowledge Gaps: Several artists had never worked on game engines before.
Development Bottlenecks: Programmers were blocked from coding gameplay loops because they had to wait for final art assets to be finished.

The Solution:

Single Source of Truth in FigJam: I created a design board with color palettes, moodboards so everyone stayed on the exact same page under one guide.
Placeholder Asset Workflow: Instead of making programmers wait, I created mock sprites with finalized pivot points and dimensions. They could test the game logic in parallel while the artists polished the visuals.
Technical Mentorship: I ran quick internal workshops on game-ready sprite exports and automated the Unity 2D import process such as nine slices rule, picking colour palettes and PPI rule.

Challenges & Learnings

Leading an art team for the first time was an eye-opening journey:

Communication: Translating abstract design ideas from game designers into sprite sheets for artists and then into prefabs for programmers taught me how to speak clearly to make all team understand and aligned.
Balancing Leadership & Production: Mentoring teammates on Unity technical constraints while simultaneously doing my own art jobdesk need good time management skills.
Letting Go of Creative Ego: Learning to critique and unify styles without stifling the creative joy of other artists was the most rewarding leadership skill I developed.

Key Takeaways & Results

Harmonious Art Direction: Successfully aligned different artistic styles into a harmonic art style and tone.
Pipeline Efficiency: Programmers finished core gameplay systems ahead of schedule thanks to early placeholder integrations.
Published Game: Shipped a complete, polished fantasy simulation game on itch.io in time.