Skip to content

Workflow — design

Submit when a change is ready for the team to play. Your lead reviews it in Discord afterwards, in a thread attached to the submit. Read Team workflow in Discord first for the parts every discipline shares.

Your workspace name

Name your workspace rp_design_<your Discord name> — rp_design_albert, rp_design_yanran. Designers share the _04 guest login, so the login says a designer submitted this and nothing more. The workspace name is what puts your name on the post.

Create it once, in P4V, before your first submit. Lowercase, letters, digits and underscores only.

Your changelist description

One line saying what changed:

main puzzle whitebox draft
Second room: rune order and hint timing

That line becomes the title of the post, so write it for someone scanning a list of submits. You do not need a task code. Design has no code to give you yet, and the changelist number is what identifies your work.

What happens after you submit

Within about a minute the bot posts in #design-submission, pings the design lead, and opens a thread. The thread is named CL <number> · <your description> and carries a tag showing where the review stands. The post lists the files you added, edited or deleted, so the lead can tell a blockout from a data change at a glance.

Every changelist gets its own thread and its own review. If you submit a fix for something that came back to you, say so in the description — the lead has the earlier thread and will connect them.

In that thread:

  • Looks good — you are pinged with approved, no action needed, and the thread tag becomes [APPROVED].
  • Needs changes — your lead writes what needs fixing and you are pinged with it. The thread tag becomes [CHANGES NEEDED]. Fix it and submit again; the new changelist opens its own thread, tagged [NEED REVIEW] so your lead knows something is waiting.
  • Block — your lead is waiting on something outside your work. The tag becomes [BLOCKED] and you are pinged with the reason.

Either the design lead or a producer can press the buttons, and the post names whoever pressed.

Where your work routes

Content/Rephrased/UI/, DataLayers/, Milestones/ and Content/2ndPlayable/ route to design by folder. So does any submit from someone carrying the Design role, whatever they touched.

Gameplay/, Levels/ and Input/ are shared with engineering. Your Discord role settles them: your submits there come to design, an engineer's go to engineering. This is why the role matters more than the folder — and why a typo in your workspace name cannot send your level work to the wrong lead.

Not announced

  • Content/Developers/<You>/ — your own scratch space. Prototype there freely.
  • Content/Imports/ — vendor packs.
  • __Builds/ — build output.

Reporting a bug

/bug → Design files into #bugs and pings the design lead. Use it when something plays wrong — a puzzle that cannot be solved, a hint that never fires, a door that opens when it should not.

Change history

  • 2026-09-22 — Gabriel Li — Design submits are identified by changelist number and description; no task code is expected. Notices state the tags a lead reads off the thread list.
  • 2026-09-17 — Gabriel Li — First version: workspace naming, submit notices in #design-submission, lead review buttons.