Accent families and editor schemes

Match palette and scheme#

Choose the full theme through Appearance, then inspect Editor → Color Scheme. A retained custom scheme can make Olympus UI surround unrelated syntax colors. Select the supplied matching scheme before deciding whether the pack’s palette is wrong.

Make a named copy#

Duplicate the scheme and name the copy for its source variant and purpose. Change a targeted category, such as comments in the language you use most, then test it beside strings, types, and diagnostics.

A scheme copy changes editor colors. It does not create a new registered Mythos UI variant or retheme every third-party panel. Use a different supplied theme when you want a different overall accent family.

Inspect the whole state#

Check focused/unfocused tabs, Project selection, completion, text selection, and diffs. A warm or cool accent can serve several UI roles, so evaluate it with actual focus and selection rather than an idle editor screenshot alone.

Use Editor → Font for typography, or an explicit scheme font override. Hold those values fixed when comparing a darker palette with Elysium or another dark family.

Recover the supplied result#

Select the original theme and matching scheme. If only icons or a specialized tool window remain different, inspect other appearance providers and that plugin’s own settings. Platform UI scale and layout settings also affect the visual result.

Include the exact Mythos variant, selected scheme, IDE version, language, and affected UI state in a report. Those details distinguish a deliberate custom color from an unintended theme resource.