First day — engineering¶
Shared install: Today is your first day. Work from the Perforce depot (client GL_Main_PC). Do the required block. Stop there unless a row below matches your current task.
Your assignment¶
Read the assignment from your lead, then open Engineering home and use its Systems, Authoring, or Reference section for the area you are changing. Read only the pages needed for that work.
When you need the original design wording, open Design source documents (Google Drive). If a Drive document and the wiki disagree, raise it with your lead instead of changing the wiki silently.
Required¶
- Rephrased MCP — install,
/onboard. Ask your lead for this week's assignment, then tell the agent what you are working on. - VS and Unreal — UE 5.8, VS 2026.
- Build —
Rephrased.sln, Development Editor | Win64, F5. Open LV_2ndPlayable, Play, then duplicate it intoContent/Developers/<Discipline>/<Name>/LV_<Name>_Playgroundfor personal experiments. Failures:Saved/Logs/.
Weekly workflow¶
Talk normally in your coding agent. Rephrased MCP runs the rest (sync latest, start task, convention check, team review, devlog, submit). You compile and PIE. No extra steps.
Assignment from your lead → open the relevant system or authoring page on Engineering home → get latest → work → you compile → you PIE → say you are done → agent reviews and submits.
If you need it¶
Skip any row that is not this week's task.
| Need | Read |
|---|---|
| The pages for your system or content area | Engineering home |
| Original design wording | Design source documents |
| Unreal C++ | C++ extensions · Actors, components, subsystems |
| Content / Blueprints | Project layout · Blueprints in Rephrased · Data assets |
| A rune | Making runes · Rune authoring · Adding a rune |
| Design context | GDD · Pillars and loop |
| Look / VFX | Visual direction |
| A shipping system | Only that page on Engineering home |
Ask your lead if you are unsure.
Personal playground map¶
After LV_2ndPlayable works in Play In Editor, duplicate it into your own developer folder before experimenting. Use Content/Developers/<Discipline>/<Name>/LV_<Name>_Playground. Your playground is for learning, reproduction steps, and local experiments. Do not edit the shared playable or PreProShowcase directly unless your assigned task is to update it.
Change history¶
-
2026-09-17 — Gabriel Li — Routed assignments through Engineering home's system and authoring sections and linked the Drive source documents.
-
2026-09-05 — Gabriel Li — Work is on Perforce (
GL_Main_PC); weekly workflow names the Perforce MCP flow (sync/start_task/submit). -
2026-09-05 — Gabriel Li — Updated to the shipped hybrid Content structure (PR #19): PreProShowcase sandbox under
Content/Rephrased/Levels/Prepro/, Art/Gameplay/Levels layout, Imports isolation,Content/Developers/<Discipline>/<Name>/scratch space. -
2026-08-27 - Gabriel Li - Updated first-day sandbox wording to PreProRuneShowcase and added the personal playground expectation where relevant.
-
2026-08-26 — Gabriel Li — Clarified org repo as daily source and old demo repos as historical only.
- 2026-08-14 — Gabriel Li — Merged engineer onboarding here. One path for every engineer: setup + weekly workflow. Role tracks removed. Optional pages listed by need.
- 2026-05-23 — Gabriel Li — Engineering-only routes on Engineering tab; open questions replaced with ask-your-lead line; shared content remains on Start here FirstDay.md.