Skip to content

visual-change-discord-notice

Visual Change Notice: Post Every Visual Change to Discord

Section titled “Visual Change Notice: Post Every Visual Change to Discord”

Every change to what a player or user can SEE reaches the project’s Discord ui/art thread before the work counts as done.

  1. Visual change: anything that alters what is seen: a screen, popup, layout, copy, HUD; sprites, icons; 3D models, materials, shaders; VFX; animation; lighting, camera; scene layout; store art. Audio is out of scope.
  2. Decide, in order, and stop at the first outcome that fits:
    • SKIP (no post, no capture): not player-visible (refactor, data, logic, audio, debug-only UI), renders identically (float-format or import churn), sub-visible, or already posted in this PR or session. PR: visual-notice-waiver: <reason>.
    • OLD + NEW: the surface existed AND an old capture is cheap (an earlier image is on hand, or re-rendering the parent revision takes ~10 minutes or less without a full rebuild).
    • NEW ONLY: first capture of the surface, or the old one is expensive or impossible (a full rebuild of an older revision, or it no longer runs). Post First capture, no earlier version or Earlier version unavailable: <reason>. PR: visual-notice-old: first-capture|unavailable (<reason>).
  3. Never fake the old image (a mockup stays labelled MOCKUP). Several new surfaces: post the current version first, never hold it waiting on an old one.
  4. The post tags the owner, <@discord.tagUserId> from .claude/t1k-project-links.json in its top matter, like every post, and carries: which screen, asset or scene; one line on the change and why; the image(s) outcome 2 or 3 selects; the PR link; the undo (revert the PR).
  5. Where: the ui (or art) entry under discord.threads in .claude/t1k-project-links.json, else discord.threads.status. No thread recorded: tell the user, post nowhere else.
  6. Capture: NEW after the last edit, OLD only for outcome 2, by the owner’s own route (engine render, preview page, the asset file). No capture yet: post “screenshots pending: ” and keep the item open. Never show secrets or user data.
  7. Who posts: the owner prepares capture paths and draft text; the orchestrating session posts (project-status-thread.md: sub-agents never post).
  8. Gate: not done until the PR description links the post or carries the token outcome 1 or 3 selects. A reviewer blocks on a missing link or token as on a missing test. Layout per t1k-discord-message, voice per t1k-human-writing: no em-dashes, a Needs line.

Incident, rationale, capture routes: docs/visual-change-discord-notice.md. Related: t1k-discord-message, t1k-human-writing, project-status-thread.md.