Nuclear Nezz

Hello everyone, after possibly our longest downtime to date we figured we owed it to you to let you what happened and why it took so long to get the update out. The update ended up taking nearly 89 hours, which doesn't include the ~2.5 hours after the game update when we weren't able to actually start on the update (see https://x.com/oldschoolrs/status/1909935042807148552). What happened tldr; I got very sick at a very unfortunate time. On Apr. 8 I started to come down with an illness, but didn't think a lot of it because I generally bounce back from things pretty fast. Then I slept for roughly 20 hours. On Apr. 9 at 12:50:00 UTC the game was updated. Usually updates go pretty smoothly, if anything is broken I can fix it easily or Pandemic is able to take over. Generally our updates take 1-4 hours, in rare rough cases up to 8. Unfortunately, this one was larger than normal. I realized a large number of our hooks were broken which made the client unusable. I knew this was going to be hours of work, worst case days, but due to my illness and the current time (10:30pm), I was not going to be able to work through it. I hoped another night of sleep would get me at least to a point of being able to work. Pandemic and I discussed if he'd be able to step in, and decided that by the time he was even able to understand it and start, I would already be well enough to do it. Each day went by with that same discussion, with the hope tomorrow I would feel well enough to do it. On Apr. 12, I felt well enough to put in a couple hours of work throughout the day, but I knew it was going to need a lot more. Finally on Apr. 13, I was able to sit down and give proper focus to the work, and got the client back up and running around 5:48:00 UTC. I do genuinely appreciate all of the support I received any time I popped in to give an update on discord, and we appreciate the patience you've had during this time. How we plan on avoiding this in the future Having a single point of failure, like a single person to be able to fix the updater, obviously isn't great. However, in this specific case, it really seems to have been just unfortunate timing. If any of the events had happened differently (the update came at the normal time, the update didn't break our updater so badly, I didn't get sick) then the outcome likely wouldn't have been so disruptive. There's a reason this hasn't happened before in our entire 11-year history. Many comments suggested hiring an additional developer, but this wouldn't have really helped in this case unless they specifically worked on the updater. I would likely no longer focus on or be up-to-date with those changes as we're a very small team and try to focus on separate areas with our specific skills and experience. While the outcome could have possibly been better in this scenario, we don't think it'd be prudent considering how rare something like this downtime is. We think the best way to move forward and minimize the chances of something like this happening is by improving our internal tooling to be more robust so that it's less likely to break during such game changes. If this had been a normal non-breaking or only slightly breaking update, if I'm not immediately available, like this time, Pandemic could have ran the updater and updated the client. With this in mind, though, it's entirely possible that this could happen again with a similar outcome due to the nature of the our business. We have no prior knowledge of the upcoming game updates or how they may break the client or updater. No software is perfect, and we unfortunately can't predict the future. What we're doing for monthly subscriptions that were affected All affected monthly subscriptions have now had time added to make up for the extended downtime. VIP and Sponsor subscriptions were extended by 7 days, and all other subscriptions were extended by the actual downtime (plus a few extra hours to make up for setup time) as we're unable to extend those further. Any VIP or Sponsor purchases that expired during the downtime have been extended by 7 days, and you should have received the role again. Anyone with a VIP purchase that expired during the downtime (or impacted otherwise) and then bought a separate VIP purchase after the downtime have had their new VIP purchase extended by 7 days. Thanks for reading, The Dream Team

⪼ JOIN OUR DISCORD ⪻ ⪼ LINK TO STORE PRODUCT ⪻ Key Features INFINITE PRAYER ONE TICK FLICKING (Menu Manipulation Required) RESTOCKING INTEGRATED MULING & REVERSE MULING ALCHING DYNAMIC & MANUAL GEARING ALL STYLES SUPPORTED Requirements CHILDREN OF THE SUN ENOUGH GOLD TO BUY SUPPLIES, UNLESS YOU HAVE REVERSE MULING SET UP 43 PRAYER Recommended BASE 60S OF COMBAT STYLES USED ADDITIONAL FEATURES Extremely customizable and Easy-To-Use Auto-creation of default settings file with GUI QUICK START capable with settings file names - able to edit all available settings Easy-to-use SAVE/LOAD buttons on GUI to set up individual settings MULE SUPPORT Make sure you're running GMuling at the same time on the same PC The username of the mule must be entered correctly in the script GUI/settings - case insensitive Port parameter is optional and should only be used if you experience port conflicts This script will walk to the mule's location, so make sure it's in a safe and reachable position INSTRUCTIONS Can easily be run through both QUICK START and NORMAL START button { QUICK START } For custom settings, add -params yourfile.json to your quickstart file For default settings, add -params default to your quickstart file Example (Windows): java -Xmx1024M -jar %userprofile%\Dreambot\BotData\client.jar -world members -script GHueycoatl -accountUser [email protected] -accountPass password -params default { NORMAL START } Just click the START button and the GUI will pop up with the default settings. There's a drop-down to load any custom files you created. When you're ready just click START!