Shape it with tools.
Use the WorldForge authoring direction to assemble content, define environments, and package a world’s identity. A visual path for creators who want to focus on the experience.
Authoring foundation in developmentWorldNexus · In development
Build worlds.
Define the rules.
A voxel universe shaped by its creators. We’re building toward a future where anyone can make their own world—with tools, code, or the help of AI agents.
WORLDNEXUS / A SHARED FOUNDATION. MANY POSSIBLE WORLDS.
One foundation. Your world’s identity.Original concept illustration · not gameplay footage
NUKIAL IS BUILDING WORLDNEXUSVoxel sandbox / Creator platform visionEarly-stage · Built with intention
01 / The vision
More than a world.
A way to make worlds.
Creating a custom world often means stitching together an engine, authoring tools, and content pipelines. WorldNexus starts with a voxel sandbox and aims to bring that foundation together—so creators can shape the landscape, the systems, and the experience.
A survival frontier.
A fantasy civilization.
A world no one has imagined yet.
The rules should be yours.
A fantasy civilization.
A world no one has imagined yet.
The rules should be yours.
A shared foundation
Reusable mechanics, world identity, and content contracts.
Distinct worlds
Each WorldPack owns its theme, content, and gameplay rules.
A creator ecosystem
A planned path from authoring tools to code and AI assistance.
02 / Creation, your way
Different starting points.
The same possibility.
Our goal is to make world creation approachable without putting a ceiling on what experienced developers can build. These are the creation paths we’re working toward.
Extend it with code.
Build deeper systems through WorldSDK extension contracts. The long-term goal is a documented public SDK and API ecosystem for packs, mods, and creator integrations.
Public SDK & APIs plannedImagine it with AI.
Work toward an idea with agents that plan, draft assets and content, assemble a WorldPack, and use test feedback to refine it. Inspect the output and decide what becomes part of your world.
AI-assisted creation planned03 / Planned agent workflows
From an idea
to a world you can inspect.
Our vision is a connected creator workflow: AI agents help carry an idea through planning, authoring, assembly, and testing, with fewer manual handoffs between tools. You review the content, see what failed, and choose what to refine or keep.
Give the idea a shape.
Describe the setting, how players live in it, and the experience you want. A planning agent would turn that brief into a world outline, content needs, dependencies, and achievable creation steps.
Make the building blocks.
With art and authoring tools, agents could help draft textures, material concepts, voxel models, and item and recipe definitions. Each output stays available to inspect, edit, or replace before it enters your pack.
Bring the world together.
Planned assistance could compose terrain, biomes, settlements, dungeons, and portal layouts between dimensions. WorldForge would be the content authoring path for assembling these pieces into a coherent WorldPack.
Define how life works.
Future agents could draft crafting and economy systems, abilities and progression, creatures, NPCs, quests, and spawn rules. A code authoring agent could propose extension code against WorldSDK contracts and planned public APIs, with each world's themes and resources owned by its WorldPack.
Let tests guide the next draft.
A QA agent would invoke validation tools to check content identities, dependencies, and resource references, then run builds and automated regression tests. Where applicable, save/load and server authority checks would help expose problems before a world is activated.
Review, revise, and package.
Agents would report failures and propose revisions, then repeat the relevant checks. You keep final control over assets, content, and code, and approve an inspectable WorldPack for packaging and use.
Creator agents build the world.
WorldForge and planned WorldSDK/public API interfaces would connect agents to authoring and QA tools. Creators would review assets, NPC roles, quests, and rules before approving a WorldPack. Development automation and test artifacts exist today; the integrated creator agent workflow is planned.
NPC agents live inside it.
Our agent vision also extends into play. In-game NPCs are designed as agents whose real-time conversations and decision intents are generated by AI language models (LLMs), guided by their role, goals, and the surrounding world. This runtime direction is planned alongside the creator workflow.
Worlds with characters that can respond.
The design gives NPC agents context from nearby players and world events, so they can decide how to respond and what to say in the moment. Imagine a merchant discussing available wares, a villager reacting to a changing situation, or a quest giver adapting a conversation to the player's circumstances. These are intended use cases for the experience we're building toward.
AI intent. World-approved action.
An LLM would generate dialogue and propose decision intent; the authoritative server would validate and execute gameplay actions through approved world rules and contracts. Each WorldPack would define the character's role and available actions, while WorldCore stays independent of any AI provider. The aim is responsive characters within a coherent, shared world.
04 / The WorldPack philosophy
Same engine.
Different laws of nature.
A world should carry its own meaning. Magic belongs to a fantasy pack. A survival loop belongs to its gameplay pack. The shared foundation stays reusable.
FOUNDATION
WorldCore
Generic mechanics and stable contracts that worlds can share.
IDENTITY
WorldPack
Themed rules, resources, content, and explicit dependencies.
EXPERIENCE
Your world
A distinct setting built on content that is validated before activation.
The AI vision follows the same boundaries: human-reviewed content before activation, and NPC agent actions validated against the active world's rules during play.
05 / Possible worlds
One idea can open
an entirely new world.
Survival and Isekai are the current gameplay pack directions. These illustrations show the broader creative possibility; they are concepts, not a catalog of released worlds.
The wild frontier
Gather, craft, build, and adapt. A survival world where the landscape sets the challenge.
Illustrative survival conceptBeyond the portal
Magic, settlements, and adventure. The Isekai direction gives its fantasy rules a home.
Illustrative fantasy conceptA new frontier
Imagine remote colonies, unfamiliar resources, and systems designed for life beyond Earth.
Illustrative sci-fi concept · Future possibility06 / Inside the build
The work behind
the possibility.
In-game screenshots from WorldNexus development builds. These are work in progress, not final art or a public release. Open any image to inspect the full capture.
Survival landscape
A view across voxel hills and water in a Survival development world. Terrain and visuals are still in progress.
Exploring the grasslands
A first-person view of a Survival development world, with grassy terrain, trees and the player hotbar.
House placement preview
A house placement preview in a staged development scene, with the building interface visible.
07 / Built from the foundation up
Creative freedom
needs solid ground.
WorldNexus is in active development with Unity and C#. The architecture separates reusable mechanics from themed content, with authoring and extension contracts as part of the foundation.
- WorldCore
- Generic mechanics, stable identity, and content contracts shared across worlds.
- WorldForge
- The authoring, validation, and content-packaging direction.
- WorldSDK
- Extension contracts in the codebase; a publicly available developer ecosystem is a future goal.
- WorldPack
- Survival and Isekai gameplay directions, with Standard and Creative modes independent of a pack’s theme.
- Play architecture
- An offline development path and dedicated server authority architecture. Multiplayer release readiness remains a separate development milestone.
Development research
Build. Observe. Refine.
A persistent world needs repeatable checks as well as creative ideas. These selected development results help us examine world variety, continuity and gameplay behavior.
Habitats across seeds
Development habitat tests sampled ten named biomes across two seeds: Bamboo Grove, Desert, Forest, Grassland, Savannah, Shrubland, Snow, Swamp, Taiga and Tundra. These are bounded test sites, rather than ten fully released biomes.
Continuity for creatures
Automated tests cover creature persistence, native agent pose restoration and selected combat interactions. The purpose is to check that creatures retain the expected state and behavior across supported scenarios; this does not establish LLM-driven intelligence.
World replay and lighting
Selected saved-world replay and lighting scenarios have passed development checks. Broader testing continues to examine how a world returns after loading and how visual conditions behave.
Diagnosing reliability
Development diagnostics investigate intermittent allocator file-commit failures. This remains an open investigation, with reproducible evidence guiding the next checks.
These results describe selected development scenarios, not release readiness. Public creator tools and LLM-driven NPC dialogue and decisions remain planned work.
Authoring explorations
Try the shape of an idea.
Explore three interactive interface studies for skill creation. These standalone browser prototypes investigate visual organization and editing interactions; they do not execute WorldNexus gameplay.
Magic circle topology
Explore a circular arrangement for connecting skill ideas and inspecting their relationships.
Explore prototype ↗Psi-inspired grid
Explore a grid-based approach to laying out skill components and their connections.
Explore prototype ↗Logic skill editor
Explore how an editor could make skill structure and configuration easier to inspect.
Explore prototype ↗08 / Where we’re going
A big vision.
A deliberate path.
We’re building the playable foundation first, then growing the tools around it. Public creator access, agent-assisted authoring, real-time NPC dialogue and decisions, and a broader API ecosystem are ambitions ahead of us.
The playable foundation
- Voxel sandbox and shared world architecture
- Survival and Isekai gameplay directions
- Building, content, save/load, and offline experience
- Authoring and extension contracts
More complete worlds
- Deepen gameplay and validate the player experience
- Advance co-op and dedicated server readiness
- Refine world authoring and content workflows
- Prepare clearer creator-facing documentation
Creation for everyone
- A public SDK and API ecosystem
- Agents for assets, world assembly, and system authoring
- Test-guided iteration and human-approved WorldPacks
- NPC agents with LLM dialogue and context-based decisions
- An ecosystem of independent creators
This is our direction, not a release schedule. WorldNexus is not publicly launched; public SDK/API access, integrated AI-assisted creation, and LLM-driven NPC dialogue and decisions remain future features.
Build the possibility with us
Let’s talk
about what’s next.
Nukial is an independent, founder-led project. We’re interested in conversations with startup programs, potential collaborators, and people who care about the future of world creation.
Founder based in Cà Mau, Vietnam.
founder@nukial.devPrivacy
This website uses localStorage to remember your language preference. It offers no accounts, forms or uploads. Email links open your mail app; messages are handled by the email providers involved.
Cloudflare delivers and protects this website and may process network requests and technical metrics, including website analytics. Read more in the resources below.
Website terms
This is an informational website about a product in development. Product directions, previews and interface prototypes may change. The website is not a game release and does not imply affiliation with technology providers or approval by a startup program.
Images and previews are shared for information; their display does not grant a redistribution license. For questions about the project or website, contact the founder.
founder@nukial.dev ↗