top of page
Honkai-0ffd09fa-451f-446a-b4fa-8d44e3659f61.jpg

Honkai: Star Rail

Gameplay Engineer Intern @ HoYoverse (2026)

PROJECT

Honkai_Star_Rail_App.webp

Honkai: Star Rail

Live on PC, mobile and console

STUDIO

HoYoverse (miHoYo)

Shanghai, China

ROLE

Gameplay Engineer Intern, Client Team

TEAM

10+ people feature team on the Version 4.7 event

TECH

Unity, C#, Lua (XLua), Perforce

DURATION

May - Aug 2026 (3 months)

Event walkthrough by a community creator, shown for context. Not my footage.

WHAT I WORKED ON
Three months on the live client of Honkai: Star Rail, a turn-based RPG played worldwide. I shipped work in three versions:
Version 4.7 · Event gameplay and UI
Built my slice of "The Fluffy Movie: Overheated", a first-person dessert-shop minigame inside the story event: cooking stations on ECS, plus the event's progression screens in Lua.
 
Version 4.5 · Config-driven UI feature
Added a designer-configured notice to three end-game challenge screens, with one reusable C# check shared by all three.
 
Version 4.4 · Live-game bug fixes
Fixed three client bugs across pause handling, gamepad navigation, and character-list data, then studied 11 core client systems to ramp up.
INSIDE THE 4.7 EVENT
My slice of "The Fluffy Movie: Overheated"
In-level gameplay (ECS): On the team's ECS framework, I built the dessert shop's cooking stations: ingredient restocking, a multi-slot grill where each item cooks on its own timer, and assembled special dishes. The rules live in plain C# classes, so they run in unit tests without the ECS runtime.
Progression screens (Lua UI): Outside the level, I built the level journey page with dated stages and daily goals, the stage promotion page, and the comic gallery with a detail view. Gallery unlocks are derived from server progress, so nothing extra is saved on the device.
Data-driven content: I connected designer-owned config tables to both gameplay and UI, and moved a hard-coded tuning value into config so designers can adjust it without a code change.
bottom of page