
Welcome
to the Wyrdwoods
LEAD PROGRAMMER
2025–2026
A third-person PvP action game built in Unreal Engine 5 around inventory-driven progression.
I led a four-person programming team and built the systems connecting inventory, items, buffs, and player stats.
10-person team · Unreal Engine 5 · Blueprints · PAX East 2026
Building Progression Around Items
The game brief called for all player progression to come from the items they carried, with no levels, stat allocation, or manual equipment system.
I split that logic into three systems: the InventoryComponent owns items, the BuffComponent processes their effects, and the StatsComponent calculates final values before the character uses them.
This kept item logic out of the character Blueprint and made the system easier to expand.

InventoryComponent
owns items
↓
BuffComponent
processes effects
↓
StatsComponent
calculates values
↓
Character
uses results
Data-Driven Item Architecture
I built the item and effect systems around Data Tables, structs, and enums so new content could be added without creating separate Blueprint logic for every item.
DT_Items stores item definitions, while DT_Buffs stores the effects connected to them. E_ItemType, E_BuffType, and E_Stat constrain how that data can be categorized and interpreted.
S_ItemLite defines item data, S_BuffLite defines individual effects, and S_BuffRuntime adds runtime state such as remaining duration and the item that created the effect.
As the inventory became spatial, I expanded the item data to include SizeX/Y/Z, separate world and inventory meshes, preview transforms, and bounding-box information. The same data could now drive both gameplay logic and the 3D inventory presentation.
(Pictured: DT_Items and DT_Buffs Data Tables with related enum and struct assets.)
3D Grid Inventory
The designer wanted players to physically pack differently sized objects into a limited 3D container while looting under time pressure.
Each item stores an OriginX/Y/Z position and SizeX/Y/Z dimensions.
FindFirstFit searches the grid for available space.
CanPlaceItemAt checks grid bounds and occupied cells.
OccupyCellsForItem records the cells used after a valid placement.
The system supports multiple Z layers, allowing items to occupy real 3D volume instead of functioning as a flat inventory with a 3D appearance.
To control scope, I first implemented box-based bounds, fixed axes, Z-axis rotation, and automatic first-fit placement before moving toward more complex manual interaction.
(Pictured: Blueprints for grid placement and cell occupancy.)
Buffs, Stats, and Item Behavior
Effects are categorized as Passive, Conditional, or On-Hit and use shared data for stat changes, multipliers, duration, trigger chance, and gameplay tags.
ApplyOrRefresh adds or refreshes effects and tracks their source item. RemoveAllBySource removes the correct effects when that item leaves the inventory. RecalcStat centralizes final stat calculations using: (Base + Flat Bonuses) × Multipliers
This shared system supports movement speed, jump height, damage, defense, critical hits, healing, shields, burn, slow, knockback, stun buildup, and other effects without hardcoding each item separately.
Timed effects only enable Tick when they need it, avoiding continuous buff processing when no timed effects are active.
(Pictured: Functions from BP_BuffComponent.)
Translating Design Into Logic
Small Shield
The design called for a shield that activates below 50% health and blocks two hits. I treated it as a conditional, hit-count-based state using ShieldHitsRemaining instead of forcing it into a time-based effect.
Magic Beans
The item automatically restores the player from 25% to 50% health once. It reacts to health changes, checks the threshold, heals the player, and removes itself after triggering.
Golem Head
The item increases damage and adds critical-hit chance. Both effects use the shared stat system, while the attack pipeline reads the final DamageMultiplier and CritChance values during combat.
(Pictured: Small Shield, Magic Beans, and Golem Head item models.)



Technical Leadership
I documented the system in a 23-page programming handoff covering architecture, Data Tables, Blueprint responsibilities, implementation status, known constraints, and future development.
I also trained teammates on Plastic SCM, coordinated technical integration across disciplines, and documented procedures for resolving Unreal .uasset and .umap conflicts that could not be automatically merged.
(Pictured: Plastic SCM workflow reference.)
PAX East 2026
I represented Wyrdwoods at PAX East 2026, demonstrating the playable build, explaining our development process and beta timeline, and speaking with players and other game developers.
(Pictured: People playing a demo of our game at PAX East 2026.)




