/* Primary UI typeface — Rajdhani, a geometric/technical sans that reads as more "futuristic HUD" than Exo 2 while staying highly legible at small sizes. Share Tech Mono stays a SEPARATE, deliberate choice for fixed-width numeric readouts (combat damage numbers, countdown timers, admin migration filenames, etc.) — it is NOT part of this swap. */ @import url('https://fonts.googleapis.com/css2?family=Rajdhani:wght@400;500;600;700&display=swap'); @import url('https://fonts.googleapis.com/css2?family=Share+Tech+Mono&display=swap'); *, *::before, *::after { box-sizing: border-box; margin: 0; padding: 0; } :root { --bg: #090c07; --bg-sidebar: #0c0f08; --bg-card: #0e1209; --bg-card2: #121709; --border: #1c2512; --border-hi: #2e3e18; --accent: #8da020; --accent-hi: #aac424; --gold: #c9a42c; --gold-hi: #e8c030; --purple: #6530b8; --purple-hi: #9060e0; --text: #c8d2be; --text-muted: #8e9e7e; --text-bright: #edf3e6; --green-ok: #40c020; --sidebar-w: 218px; --header-h: 52px; --bg-input: #0b0e08; --red: #c03020; --red-bg: #c0302015; } html, body { min-height: 100%; font-family: 'Rajdhani', sans-serif; font-size: 15px; font-weight: 400; background: var(--bg); color: var(--text); /* Light text on this UI's near-black background renders heavier/blurrier under default subpixel anti-aliasing — pronounced with Rajdhani's tight, tall letterforms at small label sizes, where it reads as smudged-together characters. Force grayscale AA so strokes stay crisp instead of fuzzy. */ -webkit-font-smoothing: antialiased; -moz-osx-font-smoothing: grayscale; text-rendering: optimizeLegibility; } /* Form controls don't inherit font-family from body by default in most browsers — set it explicitly so buttons/inputs/selects/textareas actually render in Rajdhani instead of the OS UI font. */ body, button, input, select, textarea { font-family: 'Rajdhani', sans-serif; } /* Base link styling — themed accent instead of the browser default blue/purple (and no * purple "visited" state). Wrapped in :where() so the ENTIRE rule contributes ZERO * specificity (0,0,0): it still colors every bare , but ANY scoped style overrides it * automatically — base AND :hover. This is the genuinely "low specificity" default the * comments below assume. Previously the literal `a:link, a:visited` selectors were (0,1,1) * and silently beat single-class button rules (0,1,0) — e.g. a `.travel-btn-go` link got * accent-green text on its accent-green background and the label vanished. (Author origin * still beats the UA :visited purple regardless of specificity, so the visited state is * covered too.) Any button-styled with a class that sets `color` now wins on its own. */ :where(a, a:link, a:visited) { color: var(--accent); text-decoration: none; } :where(a:hover) { color: var(--accent-hi); } /* Inline player-name links used across pages */ a.profile-link { color: inherit; text-decoration: none; border-bottom: 1px solid transparent; transition: color .13s, border-color .13s; } a.profile-link:hover { color: var(--accent-hi); border-bottom-color: var(--accent-hi); } /* ─── Keyboard focus ─────────────────────────────────────────────────────── * One global focus ring for keyboard users. The file had ZERO :focus-visible * rules while stripping outlines in two places, so tabbing through the app gave * either no visible focus at all or a ring at 12.5% alpha that is invisible on * the near-black --bg. That matters more now that the combat controls are real *