Skip to content
LOCEN/Ontario · CAStandbyOK/--:--:--EST
M4M4RK_YUportfolio
  • Projects
    ProjectsOverview
    • WorkSelected case studies and write-ups
    • GamesPlayable prototypes and game-dev logs
  • Gallery
    GalleryOverview
    • ArchivePhoto collections and visual experiments
    • ShopPrints, posters, and one-off objects
  • Logs
    LogsOverview
    • BlogLong-form devlogs and field notes
    • NotesShort observations, links, snippets
  • Resources
    ResourcesOverview
    • Tools38 in-browser developer utilities
    • LinksDaily-use dev and design bookmarks
  • About
  • Contact
中文
← projects
Game development · 2021Ready

Unreal Battle Royale Prototype

A UE4 battle-royale prototype built with Blueprints — inventory, weapon handling, and core match systems.

Role
Solo developer: gameplay systems, Blueprint scripting, and integration.
Stack
Unreal Engine 4BlueprintsC++
Links
Source
Unreal battle-royale safe-zone map cover

Context

Problem

A deep dive into Unreal Engine systems: how a battle-royale match actually holds together — inventory, pickups, weapons, and player state — built primarily in Blueprints.

Approach

Solution

Implemented in Unreal Engine 4 with Blueprint visual scripting and some C++, the prototype assembles inventory management, weapon handling, and the moment-to-moment systems a battle-royale loop needs.

Features

  • Inventory and pickup system
  • Weapon handling and switching
  • Blueprint-driven gameplay systems
  • Battle-royale match scaffolding

Architecture notes

  • Gameplay logic lives in Blueprints for fast iteration, with C++ where it matters.
  • Systems are componentized so inventory and weapons stay decoupled.

Challenges

  • Keeping Blueprint graphs readable as systems grow.

Outcome

A UE4 prototype exploring inventory, weapon handling, and Blueprint-driven battle-royale systems.

What I learned

Lessons learned

  1. 01Blueprints are great for iteration but need discipline to stay readable.
  2. 02Even a prototype benefits from componentized, decoupled systems.

Next steps

Next steps

  1. 01Document the Blueprint architecture
  2. 02Capture gameplay footage
  3. 03Port key systems to C++

Related work

Game development

Descent Into Madness

A 2D pixel-art roguelike shooter built in Unity — descend, fight, and survive escalating runs.

PreviousPurecreateA 3D apparel customizer that designs your shirt in real time and generates decals from a text prompt with DALL·E 3.
Back to archive
NextDescent Into MadnessA 2D pixel-art roguelike shooter built in Unity — descend, fight, and survive escalating runs.
Back to archive
open channel·say hi anytime · 2026
--:--:--EST
get in touch

Saw something here?Tell me about it.

It's a portfolio, not a service · but I read every note — drop a line if anything here resonated, or just to say hi.

Start a conversation

Newsletter

Get the occasional dispatch

Notes and logs from m4rkyu.com — short, dated, no noise. Unsubscribe anytime.

Work

Production builds, games, and visual archives.

  • Projects
  • Games
  • Archive
  • Logs

Resources

Daily-use tools and a personal link library.

  • Search
  • Latest
  • Tools
  • Links
  • Notes
  • Topics
  • RSS
  • JSON feed
  • Shop

Studio

Background, contact, and channels for collaboration.

  • About
  • Contact
  • Changelog
  • Colophon
  • Resumepending

Socials

Find me on the usual feeds.

  • Facebooksoon
  • Instagramsoon
  • YouTubesoon
  • LinkedInsoon
M4RKYUM4RKYUM4RKYUM4RKYUM4RKYUM4RKYUM4RKYUM4RKYU
Crafted since 2024
ZhenXiao Mark YuZhenXiao Mark Yu
© 2026 ZhenXiao Mark Yu·Ontario, Canada
  • Email
  • GitHub
  • dev.to
  • LinkedIn (soon)
  • Twitter / X (soon)
  • Instagram (soon)
Built with Next.js 16 · React 19 · Tailwind 4

Built with Next.js 16 · React 19 · Tailwind 4