During the ongoing restoration process, we found that the next popular area to focus on should be Waterbirth Dungeon. Although the dungeon was partially updated during the HD overhaul, it mostly included terrain and atmospheric changes that were largely out of place and were seemingly unfinished.

The difficulty and complexity of an area restore is highly dependent on the level of overhauls the area has had past the 2007 era (Oldschool). This should normally make the dungeon relatively easy to restore, however, we felt this area deserved a bit of extra love due to its popularity and symbolism in Oldschool RuneScape. These so called remasters can be much more complex, as we try to replicate overhauls as Jagex would have done it.

It wasn’t long until we realized that a simple restore wouldn’t be enough to make this area truly come to life. One of the prime components to an area overhaul are upgraded wall-kits (the models that make up the cave walls in this case), something even the restored version seemed to lack.

Secondly, the terrain (everything that makes up the landscape such as overlays, underlays and tile heights) appeared to be updated to a grey-ish style. This style is similar (but not identical) to the Lighthouse dungeon terrain.

As a third point, the atmosphere had a strange orange tint. We can only assume this was a design choice, but one that didn't really work with the improved render distance and the modernized style of caves.


Part of the restoration process means we have to be able to add, manipulate and erase the objects on a map. Our so-called Map Builder is able to generate these new map files and insert them into our cache (meaning areas are preprocessed just like any other).

As you know, RuneScape consists of tiles that your character can stand on. Each region contains a grid of 64x64 tiles. If a region has 4 floors, it can consist of 4096 tiles. When looking at the game on a fundamental level, it is not much more than each of those tiles having a set of 'rules', which the player navigates through. In a restore and remaster we can modify the objects present on a tile, whilst still having to adhere to the collision rules that Jagex determines.

Modifying the existing map is done using our own hybrid tools. If you have ever played a game such as Minecraft or Terraria, then you may be familiar with WorldEdit mods. Although editing tiles by hand can be very useful, particularly when making small changes, a combination of manual edits and code can be especially powerful when targeting a large area while retaining detail.

The first major obstacle in remastering this area is upgrading the wall kits mentioned earlier. To accomplish this, we need to create new walls. We began by drawing inspiration from the already restored Lighthouse dungeon, as the two dungeons are interconnected and share a similar fantasy style (dagannoths).

The Lighthouse dungeon actually utilizes a relatively common cave wall kit with a unique gray coloration. To preserve the green coloration used in the Waterbirth maps, we took the HD kits and recolored it. Because RuneScape's engine actually uses the 

 as opposed to RGB, the values will seem meaningless in most cases, adding a layer of complexity.

Now that we have the desired new kits, the next step is to replace the existing caves with the new ones. Given the sheer number of tiles that require replacement, manually performing this task would be excessively time-consuming. Since the new HD kit incorporates a gradient object that smoothly transitions the cave into the black void, we devised an algorithm to somewhat automate the process. Fortunately, we already had an algorithm in place for this purpose. Ardougne was one of the first locations to receive remastered cave walls using the initial version of the cave wall generator, which dates back to HDOS v281.

As we begin to witness the results, it becomes apparent that we have also accumulated a significant amount of unnecessary clutter that needs to be eliminated. To do this, we can add some code to refine the process and remove excess objects ourselves.


Due to the characteristics of the newly installed wall kit, we have created an additional problem. To smoothen the cave terrain shape and the minimap, not all tiles are squares. An overlay placed on top of the underlay can cause a square to become a cut-out of the original tile. These cut-outs can be used to create a smoothness, often seen in paths like Varrock, and are used in every cave.

As a result of the differences between the older wall kit and the new one, there is now a noticeable gap in the cut-out where the old wall used to be, resulting in holes in the walls. To resolve this issue, we have developed an algorithm that can dynamically adapt the cut-out shapes based on the placement of the walls. Manually addressing this problem would be an incredibly tedious and time-consuming task. While a portion of the algorithm was already integrated into the Cave Wall Generator, the nature of the thin walls and the presence of a unique outer wall that doesn't require any surrounding terrain necessitated the creation of a new, more versatile algorithm. This updated algorithm also has the ability to reverse the process or account for water, meaning that all shapes can be mirrored when needed.
The comparison provided below illustrates the terrain without the primary and wall objects, creating the illusion that the cave has expanded in size.

While the restored grey terrain may appear more modern, it is evident that it does not align with the chosen green style that we aim to maintain. To strike a balance between the two aesthetics, we can explore the possibility of blending elements from both styles. RuneScape HD introduced the concept of ground blending, which allows different types of terrain to interact and create seamless transitions. For instance, when light sand is placed adjacent to dark rock, the sand in the vicinity of the rocky terrain will naturally adopt a darker shade. Additionally, past overhauls introduced new patterns in the terrain, adding further depth and variation. Interestingly, the tunnels leading to the boss room have already undergone a mixed terrain overhaul. Taking all of this into consideration, we can replicate a simplified overhaul that combines both the green and grey terrain, aiming for a harmonious fusion of the two styles.

You may have noticed that the dungeon still lacks some detail. Some NPCs are unrestored, lights are out of place, the atmosphere can be improved, and additional decorations could be added. All of these elements are part of the restoration process and are addressed individually.

As previously discussed, the redesigned shapes of the wall kits can lead to compatibility issues with the existing terrain. This concern extends to the decorations placed on the walls as well. The provided comparison reveals the modifications made to the water streams, ensuring they are properly aligned and no longer appear to be floating. Additionally, the introduction of swamp bubbles and strategically placed lights enhances the immersive atmosphere within the dungeon.

There is undoubtedly much more involved in a remaster than what has been showcased here. Regrettably, it is impossible to cover every aspect within the confines of a single blog. We hope you enjoy this remaster, and feel free to ask any questions in our Discord. See you in the next one!

Developer's blog 3: Dagannoth King's Remaster

blog-dagannoth-kings

It's been a long time coming, but the plugin subsystem is now moving
into open beta. This lays the groundwork for us to add any plugins that users
desire. I would like to thank everyone for their patience, and to all users who
helped us iron out the major bugs during closed beta.

I am one guy, and I am a perfectionist. If it was up to me, I would wait to release a nearly flawless
system. But given that everyone is asking for plugins, and people are reporting that remaining bugs are minor,
I feel it's time to open the beta to all users and continue the work in a public scope.
Once this initial release is stable, the remaining plugins people want can be enabled.


So yes, many more plugins (core and hub) will be added in the future.

There is a lot more work I wanted to do, and plan on doing.
I tried to get the performance loss to a minimal, but it remains a work-in-progress, so if you
spot any problems, please let us know.

The goal of HDOS is to restore the game we grew up on.
It was never and will never be about plugins, plugins simply remain a feature within HDOS.
My passion is not in plugins; I enjoy working on new and exciting things, things not done before,
artistic thing, and things that tickle my passion. My heart simply isn't into plugins, so I would hope
people can come to understand and respect this. This client is meant to be enjoyed, and with all that said

Developer Blog 2: Plugin Beta is here!

Plugin Beta is here

HDOS is an entirely standalone client, as opposed to other third-party clients that work via 'client injection' — modifying the binary code of the official Jagex client.
Modifications to the game engine can be performed because the client is written independently of the official Old School RuneScape client. HDOS uses a newer, more modern engine than Oldschool RuneScape: RuneTek 4, instead of the older RT3 engine. With this in mind, unique features and capabilities can be performed, and bugs can be encountered that would otherwise not exist on other approved clients.

This client was among the first clients to receive Jagex's approval, alongside RuneLite.

Development of HDOS had officially begun on 8 May 2020, taking the official 530-revision client as a base.
The majority of the client's core has been carefully refactored and structured, allowing for easier modifications and additions as if it was Jagex working on the engine back in 2008 and beyond.

Although the engine base is RuneTek 4, it has been heavily modified to allow for newer features:

Inheriting the old tek led to some challenges. The old fixed pipeline and rendering
techniques used by the engine (while great for its time) were becoming more deprecated over time,
meaning GPU vendors were phasing them out and they were becoming slower and slower over time.
It was nearly required for us to solve this problem. We wanted as many users to enjoy the client
without needing good or even decent hardware; any hardware within the last 10 years was the aim.
The high performance on higher-end systems (500 FPS) translates to usable (30-50 FPS) performance on
lower-end systems. With that said, some of the modifications we have done are as follows:

The requirements to run HDOS are roughly:

Some other modifications we've worked on:

A comparison of the original 2009 RSHD client (left) and the HDOS client (right).

A comparison of the extended view distance

To start, we will be taking a look at the main feature of HDOS: Restoring and remastering. These are recurring terms that we use to describe the process in which we upgrade specific content within the project. If you are reading this blog and have not yet seen our 

 that beautifully demonstrate the two, then you should!

Restoring content means bringing back what once was and making it compatible if necessary. This content often cannot be copy-and-pasted over freely; careful work goes into rebuilding areas to ensure the gameplay still reflects oldschool. The complexity of these restorations can vary greatly — something we will be diving into in future blogs.

Lumbridge was one of the first areas to be restored. Although the area wasn't restored in the early stages of the client, it still showed a visual representation of HD. This is thanks to our methods of automatically upgrading assets: 

. However, this will only work if the assets existed in both 2007's release and the 2009 client HDOS is based on. This is what we call 

Remastering content, however, is the means of upgrading new oldschool-specific content that did not exist in the 2008-2011 era. Because we have no means of using existing assets, we have to make our own. This can be done in the forms of the following:

. A full area remaster in the style of Al-Kharid.

In the next HDOS developer blog, we will be detailing the inner workings of the plugin system, as well as client optimization and performance.

Dev blog

Developer's blog 3: Dagannoth King's Remaster

Developer Blog 2: Plugin Beta is here!

Developer Blog 1: Introduction