We want to give you an update today on the status of the content update as well as the general state of things.

1. General Status of the Team

It's summer. Everyone has likely enjoyed some leisure activities, and we, the team, have also taken a bit of a break behind the scenes. We've had some time to recharge, and now we're ready to dive back into the work on Shiva.

2. Status of the Content Update

The content update isn't actually that far off. However, over the past few weeks, we've done some self-reflection and realized that some of our behaviors have been counterproductive, both for the update and for ourselves. We now have several systems that are about 80% complete. The remaining 20% to completion, however, is the problem. Each system was started somewhat randomly for various reasons, and now we're facing multiple systems that are nearly finished, but no one has a clear overview of what’s still missing. This is a big issue and leads to a high error rate. Fortunately, we have a solution!

3. How We Are Proceeding with the Content Update

All of this might sound a bit alarming at first, but it’s not as bad as it seems. We worked this way because we had no other choice. To explain this simply with an example: Imagine you have a car and a motorcycle. Both are broken and need repairs. You order the parts and start with the car. You've installed all the parts for the car, but one part is still missing and needs to be delivered. Now you’re stuck waiting, with nothing else to do. So, you start working on the motorcycle until the car parts arrive. This approach is a huge mistake because while it might work with two vehicles, with 20, you lose the overview of everything.

So, going forward, we will tackle each system one by one and complete them fully without working on other things in parallel. This will ensure an efficient workflow and the completion of systems with fewer errors.

4. What Will Happen Before the Content Update?

Before we roll out the content update, we want to address 2-3 weak spots to ensure they don’t interfere with the update or disrupt gameplay further. We’ll start with the offline shop and the shop search systems. These are massive systems with a significant impact on the server. Over the past two years, some weaknesses in these systems have become apparent, and now it’s time to address them. We're planning a full rework of the shop system. A separate topic will be created to involve the community in this process.

To clarify why we need to complete this before the content update: With every major change to the server’s overall system, there’s a risk of introducing new errors. As you’ve recently seen with the Summer Event, issues can arise. To ensure that any potential problems don’t ruin the hype or disrupt the flow of the content update, we want to complete the shop rework beforehand.

Note: The Content Update will NOT be delayed because of this. The Shop Rework will be done alongside the main work.

5. Our Strengths and Weaknesses

Shiva is a reliable server, and in just a few days, we’ll be celebrating our two-year anniversary. We offer one of the best economic systems in the Metin2 section, and we strive to help everyone in support, showing a lot of leniency, especially towards our long-term loyal players. These are our strengths. However, our biggest weakness is getting updates out quickly, which you’ve likely all noticed. This is because we don’t rely on Shiva for our livelihoods; we all have our own careers and professional paths. The time we can invest in Shiva is limited, and we now aim to significantly improve this with our revised workflows. It’s important to recognize our weaknesses and work on them.