0.4.1 is bugfixes and performance work only. The public SDK API surface is unchanged, so mods built against 0.4.0 need no changes and no rebuild.

We shipped 2 major things in 0.2.0: the mod syncs a lot more of the game (see below) than it did in 0.1.0, and the server-side API is now a true API.

OblivionMP and WukongMP share the relay server and the core SDK, so everything that shipped in WukongMP 0.4.0 ships here too, against Oblivion's own components.

Mod authors: this release has breaking changes. Read Upgrading before you rebuild.

Most of the work in this release went into the server-side API. Server-side mods can create entities in any scope, subscribe to server events, kick players, and read their own config files. We used all of it to rewrite PvP.

Mod packages have a new layout too. The co-op fixes clear the three 0.3.1 known issues and the bugs people hit most.

Mod authors: this release has real breaking changes. Read Upgrading before you rebuild.

The WukongMP SDK is now on GitHub, across three repositories:

• WukongMP SDK: the SDK mods are built on.
• ReadyM Core SDK: the runtime underneath it, not specific to Wukong.
• Wukong mod loader: what gets mods into the game.

The README in each covers what it does and how to build it.

0.3.1 fixes the two resource problems people reported most, memory and CPU, along with a progression soft-lock and a batch of reconnect bugs. Binary packages and the Docker image are both up.

Mod authors: there is one small breaking change in this release, detailed under Upgrading below.

Server-side scripting is here. A mod can now run its own code inside the relay server: register components on server entities, tick systems on the server loop, and answer requests from clients over RPC. This is the piece we said was coming and the co-op mod already runs on it.

Custom components now sync both ways too, so a mod can put its own state on an entity and have the server and every client agree on it without writing any messaging code.

This release also adds a Network view to the admin panel, which shows what the relay is actually sending, broken down per ECS component. Alongside that, three co-op fixes, including NPCs that could turn hostile and block quests.

Update your server binaries to 0.3.0. Client mods built on 0.2.4 need a rebuild and a few small code changes, see the Migration guide.

Today we are shipping the first public preview of the OblivionMP SDK, version 0.1.0. OblivionMP is our community multiplayer platform for The Elder Scrolls IV: Oblivion Remastered: it turns the single-player game into a shared world you can host, and gives you a C# SDK to build your own multiplayer game modes on top of it.

This is an early preview, and we want to be upfront about what that means. A lot is not built yet. Some of what is here will have rough edges, and some of it will break. We are releasing it now anyway, because the fastest way to learn what the community actually needs is to get the SDK into your hands.

This release adds password-protected servers, several whitelist and admin panel improvements, and a redesigned join flow in the Launcher. It also introduces two new fields for the public server list.

To take advantage of the server-side features, update your server binaries to version 0.2.4. The new join flow and server list fields require the ReadyM Launcher version 0.30.0 or later, so make sure to update your Launcher as well.

The new 0.2.4 server and SDK should be compatible with mods built on the 0.2.3 SDK, but we recommend testing your mods with the new SDK to ensure compatibility.

With this version of the SDK, we are introducing a public server list feature. This allows players to easily discover and connect to public servers running WukongMP. It also includes some quality-of-life improvements and bug-fixes in the SDK.

To take advantage of these features, make sure to update your server binaries to version 0.2.3. The server list is only visible in the ReadyM Launcher version 0.29.0 or later, so make sure to update your Launcher as well.

The new 0.2.3 server and SDK should be compatible with mods built on the 0.2.2 SDK, but we recommend testing your mods with the new SDK to ensure compatibility.

This version of the SDK adds two highly requested features: mod caching and .pak file support.

To take advantage of these features, make sure to update your server binaries to version 0.2.2, and to use ReadyM Launcher version 0.26.0 or later when connecting to servers running this SDK version.

The new Launcher version is backwards compatible with all 0.2.x releases of the SDK. At the same time, the new 0.2.2 server can be connected to using older Launcher versions, but mod caching and .pak file support will not work.