Universe pathways Find a concept

Local universe index

Find a permanent concept

Search the public universe locally.

Website guidance

Self-service help without a fictional contact desk.

No verified public support address has been supplied for the root portal. This page therefore provides accurate website guidance and explains where product or purchase assistance must appear when a verified release is active.

Current guidance

Root website

Use this page for navigation, local preferences, optional audio, browser, connection, and scripts-disabled guidance.

Verified product

Product-specific help belongs on the product subdomain and in its accepted public release record.

Purchase or delivery

The verified checkout or delivery provider supplies the applicable purchase, receipt, download, and refund assistance.

No public mailbox

The site does not display an unverified email, “contact us” promise, or mailbox that does not exist.

01 · Start here

Identify which layer needs help.

Root portal

Navigation or display

Use the steps below for page loading, focus, sensory controls, local search, or scripts-disabled access.

Product subdomain

Demo or Full behavior

Use the verified product’s own support path. The root portal does not guess at product-specific controls, files, or compatibility.

Checkout provider

Payment or receipt

Use the provider identified by the verified product for purchase, receipt, refund, or account-related assistance.

Delivery record

Download or opening

Follow the exact file, browser, device, and opening instructions disclosed with that verified release.

02 · Navigation and display

Restore the clearest path first.

  1. Use the permanent links.The header, Universe pathways, breadcrumbs, Atlas, and footer are ordinary links. On mobile, the bottom dock adds shortcuts but is not the only route.
  2. Reduce the experience.Open Controls and set Motion to Reduced, Effects to Reduced or Off, or Quiet mode On. These settings do not remove required content.
  3. Use the list alternative.Atlas and studio-world pages include non-spatial list, disclosure, search, or step controls for the same permanent information.
  4. Use the scripts-disabled path.When JavaScript is blocked, use the visible header and footer links, native details elements, and direct page URLs.

03 · Optional audio

Sound never needs troubleshooting to understand the site.

Audio is off by default. Enabling it creates a browser audio context and requests local WAV files only when a cue or ambience is used. Mute, volume, calm audio, and Quiet mode remain available. If audio cannot initialize or a WAV file fails, the site reports a simplified or unavailable state and keeps the visual and text experience complete.

Browser autoplay policies may require a fresh click or key press before sound begins. The site does not use voiceover, microphone input, remote streaming audio, or audio-only instructions.

04 · Page loading and connection

Use a bounded recovery sequence.

  1. Reload the exact URL.Keep the trailing slash on route paths such as /privacy/ or /game-universe/.
  2. Check the connection.The site is static, but its HTML and local assets still require a network response unless already cached by the browser.
  3. Try a current browser.Core content uses standard HTML and CSS; some enhanced audio, dialog, and transition behavior depends on modern browser APIs.
  4. Reduce or disable optional layers.Turn effects off, keep audio off, or block JavaScript and use the direct static routes.
  5. Clear only when needed.Clearing site data resets locally stored sensory and audio preferences. It does not remove an ICU account because the root site has no account system.

05 · Useful issue record

Preserve facts, not secrets.

For any verified support path, include the page or product URL, browser and version, operating system, device, input method, assistive technology if relevant, expected result, actual result, exact steps, and whether reduced settings or scripts-disabled use changes the result.

Never include

Passwords, payment-card details, private keys, recovery codes, one-time codes, identity documents, private customer archives, or other sensitive information in a support message.

06 · Common questions

Permanent website answers.

Does browsing require an account?

No. The root website has no login or account system.

Where are my display and audio choices stored?

In local browser storage on the current device and browser. Temporary route-focus information uses session storage.

Does search send my query to a server?

No. Public concept search runs against a bundled local index and does not intentionally transmit the query to ICU.

Where is product support?

A product cannot be listed until its verified release record includes a working support path. Use that product’s subdomain rather than this general root guidance.

Where is purchase or refund help?

Use the checkout or delivery provider identified by the verified product. The root site does not process payments.

07 · Routing rule

No product-specific promise without a verified product-specific path.

This root guidance remains deliberately general. Controls, compatibility, data behavior, files, opening instructions, support, and purchase terms must be supplied by the exact verified release rather than inferred from another product.