Difference between revisions of "Feb 12 2026 Devblog"

Revision as of 20:41, 12 February 2026

Good evening, everyone! It’s time for another heRO GM Developer Blog, courtesy of Aventurine. Currently, I’ve thrown Flutrane and Ayu into the mines to ensure WoE:SE is on time! Please look forward to it YoshiP:tm:.

Abyss 4 – What the hell happened?

Surprise nerf! It was such a surprise, it even took us by it as well. On a more serious note, this was huge shock for us. We typically would only do such a massive change after To explain, this bug has been around for almost a year now but only popped up on our radar back in Late September/Early October. Once identified, we prepared a fix that would remove part of the mobs’ skills to stop them from replicating. To avoid a long-complicated explanation (search my comments in the heRO Discord for a more detailed one), there might have been something messed up in our Git, or the GM who managed the patch did not check it in at all. Put simply, the patch file didn’t get loaded into the stable branch, which is what you all play on. However, we weren’t aware of this, and continued onward, thinking it was fixed. Even with the most recent balancing prior to this, we worked with it as fixed and mainly focused on numbers for our recent economy changes. Somehow, when the same GM who fixed the bug prior loaded their branch up and made the recent changes, it also grabbed the bug fix changes from back in November and added them to the branch as well. Once I merged that branch into our test branch, it was mixed in with all the changes. While we do peer reviewing, the GM in question was not in the review process on this one. I and another GM reviewed it, thinking everything was good, and off the patch went, with the bug fix and all the changes combined, delivering a nuke to A4. We all saw what happened after this.

Going forward, we’re making some changes in our review process. I’m not going to go into detail on those. We’ve gone ahead created a new bug tracking system on T&D, and have already been using it to track issues over the past week, and we’ve seen a much larger increase in our testers reporting issues and we’re able to easily check if it’s been fixed, what branch the fix is in, has it been merged into another branch, and if it’s released. Once fixed, we close the bug thread and move onto the next. We can’t guarantee this will solve all of our problems, but please know, we would never release a change on that level without reaching out and informing players first. This was a honest mistake on our end when reviewing, and checking files in. For that, you have the entire GM teams apologies.

WoE:SE

We’re wrapping up on the WoE:SE Betas, and are nearing the finish line to get a release out the door. As I type this up, Ayu and Flutrane are fixing a last minute issue with a backend system (which is why I’m writing and not Ayu..). The betas have gone very well, but unfortunately, one feature was culled, and that was progressbar. What is that? That’s the backend code we use to create little progress bars that slowly fill up, giving you a visual of the time remaining for a task. We planned to use it to replace Barricades and Guardian Stone construction, but unfortunately, we were unable to solve the issue with players soft locking their clients after being killed. This is a root level issue, going all the way into Hercules code, and while we’re confident we can fix it eventually, we don’t want to hold off on releasing SE any longer. As such, we’re putting the old menu-based method in, and will use that until the issue is fixed. Provided Beta 3 goes well, we’re aiming for a February 21st release, replacing FE with SE. This will include the new SE chests, and a reworked FE chest to help ensure less garbage and more good loot.

Valentines Day

Our bullet hell game returns! Flutrane is finishing the last couple bugs to make sure it’s working properly and doesn’t crash midway, and maybe even make it harder for you! It’s a sign of how much we love you all. Please look forward to it!

Future Content

Once SE is finished, we plan to continue work on our next instance, which is currently midway in development. Not much has changed since our last update, due to SE, but we’ve been working on it on the side when we have time. We hope to have this out by mid-March. In the meantime, take a look at one of the new Malefic Soul weapons you’ll be able to forge inside! I'm sure many players are starting to see a pattern here with our teases...

We do hope to restart work on completing Achievements, as we're close. We actually planned to release achievements with the client update, but was cancelled after a last minute critical bug. After bribing Flutrane, we plan to go back and finally complete this. We know all of our costume fanatics will be happy!

We also plan to start development on more PVE content, such as another instance, new MVPs, and finishing Port Malaya. We have 2 new MVPs in the pipeline already, and Ayu is currently processing the best way to handle the end of Port Malaya, and Flutrane and myself have been brainstorming some wild ideas for the next instance after the current one in development.

Server Changes

Going forward, we will be migrating many of our online systems to a new server, so you might experience some downtime over the next couple of months. We will ensure all players are warned ahead of time, and minimize disruption to any of our systems. We're sure many of you who have been experiencing the error 429, or accessing the wiki on Firefox, or issues with patching will be happy with this change. We've already migrated our patch server to a temporary one. Additionally, we've released a Repair Tool for your patchers that lets you clear your cache, edit your patch number, or even delete it all together to redownload them all.