Workflow — audio¶
Read Team workflow in Discord first for the parts every discipline shares.
Your workspace name¶
Name your workspace rp_audio_<your Discord name> — rp_audio_aaron. Audio uses the _05 guest login, so the workspace name is what puts your name on the post.
Your changelist description¶
<TASK-CODE> [Your Name] what changed
Where your work routes¶
Content/Rephrased/Audio/ and Content/Rephrased/Art/Audio/ both route to audio. So does any submit from someone carrying the Audio role.
There is no #audio-submission channel yet, so audio notices post in #audio-main. When the channel exists, it is one config line and the notices move — nothing about your workflow changes.
What happens after you submit¶
The same as every other discipline: a post in the channel within about a minute, the audio lead pinged, a thread named after your task, and two buttons.
- Looks good — you are pinged with approved, no action needed.
- Needs changes — your lead writes the reason, you are pinged with it, and your resubmit joins the same thread.
Not announced¶
Content/Developers/<You>/, Content/Imports/ and __Builds/ are skipped. Audition and iterate in your own developer folder without pinging anyone.
Reporting a bug¶
/bug → Audio files into #bugs and pings the audio lead. Use it for sound that is broken in the build — a cue that never plays, one that plays twice, something mixed far too loud.
Change history¶
- 2026-09-17 — Gabriel Li — First version. Notices land in
#audio-mainuntil an audio submission channel exists.