Fantastic Felica
2024
A short, 2D pixel JRPG exploring the destruction of the world based on player actions, which is heavily inspired by games like "There is No Game" and "Stanley Parable". Created for a short class prototype and explores unconventional game mechanics.
Our Goal
“Fantastic Felicia” experiments with breaking the 4th wall, where the main focus was creating a playful and fun experience.
Highlights
A simple rundown of what I worked on in this project.
Role: Unity Engineer, Game Designer
Engine: Unity
Team Size: 5
Timeframe: 2 Weeks
-
Implemented main mechanics and game systems, such as rotation mechanic, dialogue system, and interaction system.
-
Designed and implemented all main UI/UX, including dialogue pop ups, dialogue options, and intro menu sequence.
-
Assisted in rewriting and finalizing narrative flow and implementing narrative into dialogue system.
-
Polished level layout and game traversal to assist with gameplay and implementation…
Trailer
Challenges
Built for Change
As a the primary engineer for this project, one of the biggest challenges was keeping up with the evolving design needs. I built systems, reviewed them with the team, and iterated as the project took shape. Designs shifted constantly and required me to adapt the tools to make sure they remained efficient.
One of the most difficult tasks was creating tools that streamlined development for our short timeframe. In particular, the design system went through multiple iterations over just a couple weeks as our needs evolved. It had to be flexible enough to accomodate design changes while remaining easy for the team to use. Because of this, I focused on masking the system as user-friendly as possible so that the team could jump in engine and add dialogue without relying on my support.
Ambition Vs. Reality
From the very start, this project was ambitious for our limited timeframe. We wanted to accomplish as much as possibly from creative mechanics, branching dialogue, and multiple levels. However, as development progressed, it became very clear that we couldn’t accomplish everything we wanted within the short window we had.
To stay on track, we had to refine our initial plans. This meant reducing the branching dialogue, cutting unnecessary levels, and prioritizing polish over volume. By being flexible and willing to adjust our goals, we created a final project that was polished and cohesive within the time we had.
Important Takeaways
Future-Proof Systems
Understanding the core systems and how they might evolve is very important when implementing them under strict deadlines. Being able to understand possible design shifts and how your teammates will interact with these systems helps create a more adaptable and efficient workflow.
By considering the potential changes early on, the system can be built with flexibility in mind and reduce the need for major refactoring or overhauls. A well-structured workflow not only streamlines development but also helps teammates work efficiently without unnecessary technical burdens.
The Art Of Scoping
Understanding how much work can be accomplished within a given timeframe is essential for scoping. It’s easy to be ambitious, but without caution, it can to an unfinished or polished result.
Knowing exactly when to scale down in the process is just as important. Prioritizing core features, refining essential gameplay, and cutting anything that doesn’t serve the project’s goals can be the difference between a well-executed final product and one that feels incomplete.