Veloria Skyrim Roadmap: From the Foundation to Our First Shared Adventure

Roadmap update: October 25, 2026. This article covers Veloria, our Skyrim-based project. Kingdom of Veloria, our original Unreal Engine game, has a separate development path. The status below is based on the latest recorded engineering checkpoint from October 24 and earlier documented work; it is not an announcement of a new gameplay test today.

Our immediate goal is simple: establish a dependable private multiplayer session before expanding the custom world. We want one player to connect successfully, then two players to join the same session, see each other, move together, and reconnect reliably. New characters, merchants, quests, and world patches come after that foundation.

How to read this roadmap

Prepared means that source, assets, packages, or automated checks exist. In testing means the work still needs direct verification in Skyrim or across the actual connection. Planned means it is future work. A successful build or a server health check does not, by itself, prove that players can enjoy a working multiplayer session.

Phase 1 — Preserve and prepare the development foundation

Status: substantial preparation completed; compatibility checks continue. We have an isolated Skyrim development client, native Veloria components, packaged client assets, and tools for checking required files. Earlier recorded checks passed for parts of this foundation. Backup and staging workflows allow changes to be reviewed without treating the original installation as disposable.

The remaining work is to refresh the compatibility checks against the exact client and server candidates used for the first connection. Skyrim updates, script extensions, native plugins, game data, and the multiplayer client must agree. An old passing result is useful history, but it is not a substitute for checking the combination we are about to run.

Phase 2 — Establish the private server foundation

Status: private startup milestone recorded; end-to-end player access remains open. The October 24 checkpoint records a completed Linux server build, successful loading of its native component, a responding resource service, and a healthy private test backend and database. These are meaningful steps beyond having server source code alone.

The next milestone is verifying the private network route and confirming that the client can reach the intended services. At the latest recorded checkpoint, device authorization for that private route was still pending. We are keeping this as a private testing stage rather than announcing a public server.

Phase 3 — Connect the first real Skyrim client

Status: next major gameplay gate. Once the route is verified, we will apply backed-up connection settings and test the actual game connection. The client must start correctly, reach the server, complete the required identity and session checks, and spawn the intended player character.

Success means more than seeing a menu or a connection message. We need to observe the player in the game, verify movement and camera behavior, check that the interface remains usable, and review the logs for failures. If a compatibility problem appears, it becomes a recorded issue to resolve before adding more systems.

Phase 4 — Prove the two-player session

Status: required before multiplayer readiness can be claimed. After the first client works, a second approved client joins the same private session. This is where we verify that both players can see one another and that their movement, location, and session state stay consistent.

The test should include joining, leaving, reconnecting, and checking that one player does not accidentally control or overwrite the other. We also need to distinguish actual two-PC gameplay from automated persistence tests. The project has earlier local test results, but those do not close this real-player milestone.

Phase 5 — Validate character creation and the interface

Status: implemented foundations with live acceptance still required. Earlier development records include work on character origins and classes, a controlled starting flow, character resume behavior, custom interface components, and the HUD. The HUD work includes a compass, player resource values, and target information.

These systems still need to be accepted as a complete player experience: create a character, enter the intended starting location, use the interface, move normally, and return to the correct state after reconnecting. Character appearance, input, first-person and third-person views, and transitions must all be checked together. A menu being built does not mean every connected feature is finished.

Phase 6 — Review the custom hub and restore content in stages

Status: authored and staged work exists; world acceptance is still open. Previous hub work includes market and waterfront areas, bridges, housing and interior elements, and preserved character placements. Record-level repairs and staged packages provide a starting point, rather than a declaration that every route is ready for play.

Once basic multiplayer is dependable, we can review the selected hub package in the editor and in Skyrim. Players must be able to cross bridges, enter supported interiors, move around obstacles, and follow intended routes. NPC navigation, collision, door connections, and shared-world behavior each need their own checks. We will introduce custom content as reviewed patches rather than mixing every feature into the first connection test.

Phase 7 — Expand roleplay and online systems

Status: later development, dependent on the multiplayer foundation. The longer-term direction is a Skyrim roleplay experience with characters, places, and systems that support a shared world. The exact order of additional features should follow what the working foundation can support.

There is already exploratory interface work, including a read-only Warfront-style shell. That is not a completed competitive mode: territory control, matchmaking, rankings, rewards, and synchronized campaigns are not established by a menu. Future posts will explain which systems are being designed, which are implemented, and which have been tested with players.

Phase 8 — Prepare a limited closed test

Status: future gate, with no release date announced. A limited test should follow evidence that installation, sign-in, joining, movement, reconnecting, and essential persistence behave reliably. We also need clear setup guidance, a way to collect useful bug reports, and a recovery path when something fails.

The purpose of a closed test is to learn from a controlled group, not to label an unfinished collection of systems as a finished release. Access arrangements and any required downloads will be explained when they have been checked and are appropriate to share.

Our order of work

The practical sequence is: verify the private connection route; connect one real Skyrim client; prove a two-player session; validate character flow, HUD, and reconnect behavior; review the hub and add content patches; then prepare a limited closed test. If testing exposes a problem, we will fix that foundation before moving forward.

We are not attaching a single completion percentage to the whole project. Different parts have different levels of evidence: a compiled component, an editor inspection, a healthy server, and a successful play session each prove something different. Our updates will focus on concrete milestones so you can see what has changed and what still needs work.

Follow the development

This blog will carry further Skyrim updates alongside clearly labelled Unreal posts. We will share screenshots and demonstrations when they illustrate real progress, and explain remaining limitations alongside them. Thank you for following Veloria as we work toward that first dependable shared adventure.