21 Junk Street
A PSX-aesthetic raccoon cooking game made by a 21-person team — as Tech Co-Lead I built the C++ audio and Niagara subsystems, the full UI suite, rain weather, a Day-Night Cycle and NPC chatter.
- Type
- University Assignment
- Module
- GDEV50001
- Engine
- UE5
- Year
- 2025–2026
- Team
- 21 People
- Role
- Tech Co-Lead
- Doc Pages
- ~36
What is 21 Junk Street?
21 Junk Street is a raccoon cooking game built in Unreal Engine 5 as a module-wide group project for GDEV50001 — Junior Collaborative Development at Staffordshire University. A team of 21 people across disciplines worked together across nine weeks to ship a PSX-aesthetic isometric game where a raccoon runs a street food stall — customers queue, place orders, the player cooks, and a second dungeon zone opens for exploration. The project was developed using GitHub for version control, with tasks tracked in Microsoft Planner.
// 21 Junk Street — in-engine screenshot
My Role & Contributions
The role here was Tech Co-Lead — shared with Charlie Hollingsworth. Responsibilities covered foundational C++ subsystem architecture, full UI implementation, a rain weather system, a Day-Night Cycle, NPC chatter, cross-discipline technical support, GitHub management, and formal technical documentation for the shared team. Namaan's personal contributions were awarded 100% independently of the team submission.
C++ World Subsystems
UAudioSystem — C++ World Subsystem
The audio subsystem is a UWorldSubsystem singleton accessible globally via a static GetAudioSystem() getter — no
Blueprint reference required. Internally it manages an SFX component pool and four dedicated UAudioComponent BGM channels (Generic,
Exploration, Combat, Boss) with crossfade support between them.
Blueprint-exposed functions include: PlaySoundAtLocation, PlaySound2D, PlayBGM, PlayBossBGM,
SwitchBGM, volume management, per-audio lifetime configuration, looping toggle, fade in/out, audio component getter, and BGM shuffle
with proper looping. A debounce mechanism prevents the same sound firing multiple times in a configurable window.
// UAudioSystem API — PlaySoundAtLocation node
An AudioEvent data table integration was added in Week 6/8 for fully decoupled sound triggers — designers trigger events by name, the subsystem resolves the asset. Sound Attenuation Debug Spheres were added as an optional parameter (at Morgan Hellsing's request) to aid attenuation asset creation.
UAudioComponent after the attenuation setting was applied, causing attenuation to override playback parameters on the same
tick. Correcting the assignment order restored all attenuation behaviour. The audio listener was also overridden from the camera to the player
pawn so spatial distance is calculated from the correct origin.
// Audio attenuation debug spheres
UNiagaraVFXSystem — C++ World Subsystem
A second C++ UWorldSubsystem for Niagara effect spawning. Pool entries use TWeakObjectPtr to avoid garbage collection
conflicts when effects complete mid-tick. Supports SpawnVFXAtLocation and SpawnVFXAttached with socket name support for
bone-attached effects.
A pre-warm pass runs on system load to force shader compilation for all pooled effects upfront — eliminating the visible
first-frame stutter that Niagara systems otherwise cause when triggered cold. The static GetVFXSystem() getter mirrors the audio
subsystem's access pattern. The public API was renamed from VFX→Niagara in Week 4/5 for naming cohesion across the codebase.
Subsystem Architecture
Both core systems — Audio and Niagara — use the UWorldSubsystem singleton pattern with static getter functions, mirroring how Epic Games documents preferred global services in UE5. This architecture eliminates Blueprint reference invalidation issues and makes both systems frictionless for any team member to access without needing manual subsystem lookups.
The initial choice to use UGameInstanceSubsystem was revised in Week 1 to UWorldSubsystem after the former caused
Blueprint reference invalidation on level transitions. The correction, though time-consuming upfront, prevented that friction from hitting every
team member across nine weeks of development.
This is structurally comparable to how audio middleware like Wwise exposes its Unreal integration — wrapping low-level sound calls behind a global singleton with pooled audio objects and an event-driven dispatch model — at a lighter, project-appropriate scale.
Menus & Interface
The full menu suite was built across Weeks 6 and 7 in close collaboration with Belle Farhan (UI art) and Sofia Chernetska (Main Menu artwork). Every widget includes slide/fade-in animations, hover tint visual cues, and audio cues hooked into the Audio Subsystem. Graphics settings persist via SaveGame across sessions; volume sliders are bound directly into the Audio Subsystem's channel volumes.
Full UI Suite
All menus share a consistent animation language: slide-in transitions, hover tint visual feedback, audio cues from the Audio Subsystem, and a fade-to-black loading screen on Play to mask the level load.
Main Menu
Graphics Menu
Sound Menu
Controls Menu
Pause & Options
Notification Toast
Post-Process Outline Material
A screen-space post-process material rendering coloured outlines around interactable objects. Uses Unreal's CustomDepth stencil pass — objects set their custom depth stencil value, the material reads it and composites the outline on top of the scene. Supports three modes: mesh colour, custom colour, and blend.
// Post-process outline material — in-engine
Designer-exposed parameters include Outline Width and Outline Opacity (clamped to a min/max range to prevent engine crashes from extreme values). A one-sided rendering bug was fixed in the initial version. Later in Week 6, support for internal geometry edge outlines was added at Matthew Hall's request — the material became the standard interactable visual language for the art team.
// Outline material node graph
Additional Systems Built
Beyond the primary subsystems and UI suite, the following systems were prototyped or shipped during development:
Rain Weather System
Day-Night Cycle (C++ AActor)
UGamepadUtilities (C++ BFL)
BPC_NpcChatter (Blueprint Actor Component)
BP_LootSource
Save/Load System (C++ UGameInstanceSubsystem + BFL)
Checkpoint Actor + Widget
Post-Process Outline Material
Development Recordings
What Went Wrong
The single biggest ongoing problem was GitHub management at scale. From Week 7 onwards, the entire team worked in one branch, causing constant conflicts, silent reverts of committed work, and repeated loss of changes without notification. Several week's worth of features were unknowingly reverted before the issue was identified.
The Voice-Over Component was designed twice. The Week 5 prototype was built before the NPC Blueprint actors it depended on were testable. It had to be redesigned from scratch in Week 8 as the NPC Chatter Component. An inter-system dependency map at project start would have flagged this risk immediately.
Controller support was scrapped entirely — gamepad detection, button icon display, and controller rumble were all implemented and confirmed working but cut from the final build due to time pressure. These were peripheral features pursued before the core game loop was stable.
A Week 2 absence due to personal circumstances disrupted progress. On return, the team had not documented what had changed. The game's direction was still in flux. In future projects, a shared "current state" document would let any returning member reorient immediately.
Gallery
