Online companion-creature game built in Unreal Engine 5.7 on the
Gameplay Ability System. Players feed fruit to their companions,
which reshapes both their stats and their bodies and drops essence
byproducts back into the loop.
As Freelance Gameplay Engineer at Studio Revive, I own the
implementation of the core gameplay systems, working from the
studio's design direction and alongside its 3D artist.
Progression lives in GAS attributes and abilities, appearance lives
in artist-authored skeletal morph targets, and my systems connect
the two so new content can be added without touching code.
// primaryC++Unreal Engine 5
// systems & toolsGASGameplay AttributesMorph TargetsProgression SystemsData AssetsInteraction Systems
// project.info
studioStudio Revive
roleFreelance Gameplay Eng.
engineUnreal 5.7 + GAS
fromApr 2026
toPresent
// feature.showcase
[ FOOTAGE COMING SOON ]// project in active development
// systems.built
01 — GAS
Multi-Axis Morph System
Stat and appearance progression built on GAS. Creatures grow along
three opposing morph axes plus a neutral growth path, and each
axis maps attribute values onto artist-defined skeletal morph
targets so stats and shape evolve together.
02 — Feature
Companion Creature Demo
Sole engineer on the companion-creature demo feature. Appearance
changes are dynamic and combinatorial, driven entirely by GAS
attributes and abilities, so no two creatures have to grow the
same way.
03 — Loop
Feeding & Byproducts
The core loop: fruit fed to a companion applies its stat and morph
changes through GAS, and the feeding produces essence byproducts
that drop back into the world for the player to collect.
04 — GAS
Pickup & Equip
Item pickup and equip implemented as a GAS ability, routed through
a dedicated interaction component. The first feature milestone
on the project, and the base the feeding loop was built on.
05 — Arch
Identity vs. Behavior
Settled architecture rule for the project: the data asset defines
what an item is, and the C++ class defines what it does. New fruit,
items, and morphs are data; new mechanics are code.
06 — Pipeline
Artist-Driven Mapping
Morph targets stay in the artist's hands. The system binds what art
authors to gameplay data, so new looks can be added without new
engineering work.