Hello, and welcome. This site is my project portfolio, and also the long-term archive for the works I publish as Left Jun and develop under the Limenauts name.
I do not want it to be only a gallery of finished screenshots. For me, the useful part of a portfolio is also the path from an idea to a playable build: what I was responsible for, how the systems work together, what tradeoffs I made, and what later feedback revealed.
So this site is a project archive rather than a general personal blog. Project pages show results, retrospectives explain process and tradeoffs, development plans mark what is still planned or waiting for validation, and articles keep event records or technical notes.
How to Read This Site
The site is organized into four main areas:
- Project Portfolio: finished or playable works, with project goals, system structure, and my contribution.
- Retrospectives: process notes about how projects were built, what worked, and what needs correction.
- Development Plans: future-facing update plans based on feedback and project priorities.
- Articles & Columns: event records, site notes, and technical notes worth keeping.
If you want a quick view of my current direction, start with Emotion Mask, Elegy of Asherah, and UE5 Multiplayer PvE Demo. They show a solo 48-hour playable loop and public release, a 72-hour team gameplay system, and my first focused UE5 multiplayer gameplay demo.
If you want to see how the projects were tested in public, read the roadshow note. It records what happened when unfamiliar players tried the games in person, and why the site now separates project pages, retrospectives, and development plans.
Why Projects, Retrospectives, and Plans Are Separate
I used to put everything into one page: setting, screenshots, features, technical implementation, reflection, and future plans. That made the page long, but not necessarily clearer.
The current structure gives each page a job:
- A project page answers: what is it, what did I do, how does the system work, and what public result exists now?
- A retrospective answers: why was it built that way, and what did I learn?
- A development plan answers: what should be improved next, and how will I verify it?
- An article answers: what happened at a specific event or production moment?
This makes each work easier to read as a continuing process rather than a single frozen page. It also matches how I want this portfolio to work: not just proving that something existed, but showing how I keep making it more playable and more understandable.
What Comes Next
Short term, I will keep making key project pages more engineering-focused, keep the boundaries between implemented work and future plans clear, and improve the reading paths for UE5, web product, and embedded projects alongside the Unity work.