Matching and customizing a Noctis scheme

Apply a complete baseline#

Choose the intended Noctis theme under Appearance and select its matching supplied editor scheme. Confirm both before comparing a dark relative with Lux, Hibernus, or Lilac.

An editor scheme and the surrounding UI theme are related settings. A retained custom scheme can intentionally combine them, but that combination no longer represents the supplied palette shown in a theme screenshot.

Duplicate before editing#

Make a copy under Editor → Color Scheme. Adjust a language-specific category or general text attribute, then inspect several file types. A color chosen for one language’s keyword may have a different role in another language.

Keep comments and inactive text readable without making them indistinguishable from normal source. Check warning/error and selection overlays after changing foregrounds.

Tune fonts separately#

Use Editor → Font for family, size, and line spacing, or deliberately enable a scheme-specific override. A light/dark variant does not substitute for adjusting tiny text or an unsuitable font weight.

Compare popups and diffs#

Open completion and documentation, select a row, and inspect a diff. These show focused states and semantic backgrounds that a plain editor view omits. If one panel differs, inspect that tool’s own appearance settings and any additional appearance plugin.

Return to the pack#

Reapply the supplied theme and scheme to restore their baseline. Keep custom copies clearly named so Settings Sync or a manual selection does not accidentally make a future comparison misleading. Record the exact variant and scheme when reporting a problem.