Build visual novels, animated scenes, and 2D game systems in Java.

Java Vector Nexus is a modular Visual Novel engine and 2D animation toolkit. It is built around source-first development, scriptable scenes, editor tooling, and a Java runtime stack that can grow past classic VN-only workflows.

Get Started

What It Is

A Java-native toolkit for VN creators who want more engine under the hood.

JVN is for projects that start with dialogue and character presentation but need room for animation timelines, custom interaction, menu systems, runtime packaging, and engine-level extension. The current distribution is intentionally source-first while the engine is still moving quickly.

The public docs here are copied directly from the engine repository. The website adds orientation: what to read first, which systems exist, and why JVN is shaped differently from a lightweight VN script runner.

Why Different

Not just a dialogue player

Source-native

The engine is designed to be inspected, extended, and shipped from code.

JVN uses a modern Java toolchain with Gradle builds, IDE-friendly modules, and clear extension points. Projects can stay close to the runtime instead of being boxed into a closed editor format.

Layered runtime

Story presentation and interactive behavior are handled as connected systems.

Dialogue, branching, scene state, entities, input, camera movement, UI, and timed events are modeled as parts of the same engine stack. That keeps narrative structure and real gameplay logic from fighting each other.

Data-driven staging

Visual composition is treated as reusable scene data, not one-off editor work.

Timelines, layered assets, lighting choices, transitions, and character placement can be authored visually, saved as structured data, and reused by scripts without hard-coding every shot by hand.

Build discipline

Production concerns are part of the workflow from the start.

The tooling and docs account for asset dependency scans, release manifests, runtime caches, portable archives, native packaging paths, and repeatable checks before a project leaves the development machine.

Wiki Scope

A static index over the engine docs

The documentation under docs/ is copied from the engine repository as-is. The site shell only adds navigation, filtering, and a cleaner public entrypoint for javavectornexus.com.

Task-based guides for new creators
Reference pages for VNS, JES, menus, layout, and runtime systems
Editor documentation for hub, sidebars, Puppeteer, diagnostics, and assets
Architecture notes for engine internals and renderer contracts

Current State

Useful context before diving in

Is JVN source-first right now?

Yes. The engine docs currently recommend using a source checkout with the wrapper commands and Engine Hub while the project is still in active preview development.

Is it only for visual novels?

Visual novels are the core use case, but JVN also documents JES scenes, entity components, timeline animation, physics, menus, UI layouts, RPG-style systems, and Java integration.

Where should new users start?

Start with the getting started guide, then choose between VNS, JES, Puppeteer, editor, or release docs depending on what you are trying to build.