Settings Overview

Your account data below is loaded directly from the NEOQEX backend. Local appearance and accessibility preferences are stored separately in this browser.

—
Username
—
Level
—
XP
—
Activity records

Backend connection

Live authentication and account API status.

Checking…
Loading your account…

Recent activity

Loaded from /api/activity.

Loading activity…

Appearance

These settings are applied immediately and saved locally.

Theme

Select the visual theme used by NEOQEX.

Animations
Enable interface transitions and micro-animations.
Galaxy background
Show the large space background elements.
Cursor glow
Hide the cursor glow effect when disabled.

Accessibility

Local accessibility preferences that can be shared with other NEOQEX pages later.

Reduced motion
Minimize animations and transitions.
High contrast
Increase the contrast of secondary text.
Text size
Change the base UI scale.

Language & Region

Language infrastructure is not connected to the backend yet.

🌍

Language settings are not connected yet

The current NEOQEX interface is English. When localization is added, this panel can control the language and regional formatting globally.

Profile

These fields are connected to GET/PATCH /api/profile.

Your username is account identity data and cannot be changed here.
Email changes require the dedicated account/verification backend.

Sessions & Security

Session management requires the dedicated D1 sessions API.

🔒

Session management is not connected yet

NEOQEX already authenticates this page using the server session. The session list, revoke-session and logout-all controls will be connected after the D1 security endpoints are added.

Privacy

Current privacy information for this browser and your NEOQEX account.

Account data: Account/profile information is loaded from the NEOQEX backend. Appearance, accessibility and other browser-only preferences are stored locally under neoqex_settings.
Browser local preferences
NEOQEX uses local browser storage for settings that do not need the server.
Local
Server account
Authentication and profile data are handled by the NEOQEX backend.
Checking…

Data & Storage

Export the data currently loaded by this settings page or clear local NEOQEX preferences.

Export loaded data

This exports the backend data currently fetched by this page plus local settings.

Local settings

This does not delete your server account or server-side progress.

Local achievement cache

Only affects the legacy browser-side achievement cache.

Notifications

Server-side notification preferences will be connected to D1 later.

🔔

Notification preferences are not connected yet

The backend does not currently expose the notification settings API. This panel intentionally does not pretend to control server notifications.

Sound

This is the central NEOQEX browser audio configuration. Other pages can use window.NEOQEX_AUDIO to respect these settings.

Master sound
Master switch for NEOQEX UI audio.
Master volume
Volume used by the NEOQEX audio helper.
60%
UI sounds
Interface tones and general UI feedback.
Button sounds
Click sounds for buttons that use the audio helper.
Notification sounds
Notification tones for pages using the shared audio helper.
Ready

Game Preferences

Browser-side game preferences. Server-side game progress will be connected to D1 later.

Game auto-start
Save your preference for experiences that support automatic starting.

NEOQEX Experience

Global visual preferences that can be consumed by other NEOQEX pages.

Ambient particles
Allow pages that support the setting to show ambient particles.
Cursor glow
Allow supported pages to display cursor glow.
These preferences are intentionally stored in one neoqex_settings object so every NEOQEX page can use the same source of truth.

Developer & Diagnostics

Test the actual NEOQEX backend endpoints from this browser session.

API health check

GET requests only. No account data is modified.

GET /api/me Not checked
GET /api/profile Not checked
GET /api/xp Not checked
GET /api/activity Not checked
No diagnostics have been run.

Browser state

Local environment information.

Log Out & Delete Account

Account actions that are currently available through the backend.

Log out

This sends a real request to POST /api/auth/logout.

Delete account

Account deletion requires the dedicated D1 endpoint.

Why is delete disabled?
This page does not send a fake request to an endpoint that does not exist. Once POST /api/account/delete is implemented, this button can be wired directly to it.