Nexus Evo S6 EMU

No reset. Real progression.

Nexus Evo is a no-reset Season 6 server built for players who want the classic long-form grind done properly: 3x experience, 1x drop, modernized visuals, cleaner movement and camera, and a fair progression path without fake multi-season noise.

No Reset
Long-form progression for true heads
3x / 1x
Experience and drop rates
S6 EMU
Modernized Season 6 direction

Season Identity

Nexus Evo is one no-reset Season 6 Episode 3 realm. The site should reinforce a single clear identity: classic progression, modern presentation, and no alternate season branches.

Auth Gatekeeper

Account login, session tokens, and recovery workflows stay in the Java service. The Next.js layer remains thin and safe.

Project Promise

The core pitch is simple: a fair classic experience with modern client work, strong account tooling, and visible operational trust instead of opaque private-server shortcuts.

Architecture

The site is framed around a simple boundary: PostgreSQL stores both game and auth data in separate schemas, Spring Boot controls trust and tokens, and Next.js owns delivery, rendering, and UI.

Database

One PostgreSQL database, two clean schemas.

Game entities live under the game schema while account, session, and web records stay inside auth. One connection pool, less duplication, clearer ownership.

Backend

Spring Boot handles trust boundaries.

The Java 21 auth service acts as the gatekeeper for credentials, tokens, recovery flows, and realm status, exposing a narrow REST API to the frontend.

Frontend

Next.js delivers the player-facing experience.

Server Actions can call the Java API from the server side while Zustand handles lightweight client state like launchers, realm selection, and UI flow.

Execution Roadmap

This keeps the project moving from wireframe to launchable web portal without mixing frontend concerns with auth and game runtime responsibilities.

Phase 01

Wireframes

Landing page, architecture framing, and initial CTA flow for accounts and downloads.

Phase 02

Auth Integration

Connect register, login, reset-password, and token refresh against the Spring Boot API.

Phase 03

Player Systems

Rankings, guild profile pages, server status widgets, and download center.

Phase 04

Operations

Telemetry dashboards, maintenance notices, and deployment hardening for production.