New MH Development #2

Heroes,

The Closed Beta has gone live! It has already been a week. Thanks to everyone who has helped thus far, and reported bugs!

• Something was crashing the server frequently, but the cause was quickly found and it has been fixed with the first patch on day 2. Since then, no more sudden crashes. The server has been running smoothly for the rest of the week, where the only downtime was for more patches to the beta.

• We had 3 patches this week so far, roughly 25% of the ~40 reported bugs have been fixed. Most of the bugs are pretty minor! And all of them will be ticked off soon enough~

• This first week of testing was focused on 'general' gameplay testing. From next week we will be focusing more on specific system testing. For example; all of parties, guilds (siege/SR), and others.

We might invite more people for this later on.

Behind The Scenes: Sharing about Patch Etiquette

Some of the these development logs will include a 'Behind The Scenes' segment where we will share something from behind the scenes. This because we want to be more transparent with you, our players. As well as show our thought-process on how we plan to tackle issues from the previous version of Madrigal Heroes, and improve from there.

This week in Behind The Scenes: Patch Etiquette. What we believe is important with each patch we put out in the future.

Every patch should follow these steps to deliver the best product;

1. Concept/layout internal discussion of what is inside the patch.

2. If any specific changes are made, e.g. PvE/P balance, rewards, etc., discuss directly with those responsible.

3. Make the necessary changes to the concept after discussion.

4. Create the patch and put it on the test server.

5. Test each aspect of the patch. This includes minor things like a small % edit of a skill.

6. Make the necessary changes (bugs and more) to the test server and re-test.

7. Confirm everything is working as intended.

8. Port the patch to the live server.

9. Announce & patch.

Rules of thumb;

• Do not rush a patch

• Do not patch anything untested, no matter how minor the patch

• Communicate clearly between staff members, and know what your role is within the patch

• Keep announcements professional and to the point (spellcheck)

• Do not prematurely tease or announce future patches if they have not been tested

That concludes the development update for this week!

- The Madrigal Heroes Team