Skip to content

Workflow — art

Submit when your work is ready to be seen. 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_art_<your Discord name> — rp_art_maddyma, rp_art_aniki. Artists share the _02 and _03 guest logins, so the login cannot tell you apart. The workspace name can, and it is what puts your name on the post.

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

Your changelist description

One line saying what changed:

Added torch and holder assets
Weapon material pass, second variant

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. Art 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 #art-submission, pings the art 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 see what moved before opening anything.

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, such as a rig that has not landed. The tag becomes [BLOCKED] and you are pinged with the reason.

Either the art lead or a producer can press the buttons. The post names whoever pressed, so it is always clear who signed off.

Where your work routes

Anything under Content/Rephrased/Art/ comes to art. So does any submit from someone carrying the Art role, whatever folder it touched.

One exception: Content/Rephrased/Art/Audio/ goes to audio, because it is the more specific folder.

Not announced

  • Content/Developers/<You>/ — your own scratch space. Import, test and throw away there without pinging anyone.
  • Content/Imports/ — vendor and marketplace packs.
  • __Builds/ — build output.

Reporting a bug

/bug → Art files into #bugs and pings the art lead. Use it for art that is broken in the build — a mesh that floats, a material that renders black, a missing texture — not for work that simply is not finished yet.

Change history

  • 2026-09-22 — Gabriel Li — Art 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 #art-submission, lead review buttons.