JagexHooli

We know these upgraded Seasonal Events we can build on each year are popular, and we're not disregarding that feedback either. I think you're far from alone with wanting the same treatment for Halloween.

For the long term, the thing we've primarily taken away is that there's a balance to strike on delivering permanent update and the timing of when we make this bigger investment seasonal event upgrades.

To be open about it, whether or not Halloween gets the upgraded Hub/Quest/Activities treatment this year is TBD right now. We haven't Yay or Nay'd it either way as yet.

That's not the intention of the post for sure, we're not putting anything on players here. We just wanted to provide context on why we had this in plan for Summer in the first place.

From our perspective, listening to that feedback has been great given the positivity we've seen for Christmas and Easter. We simply made a misjudgment to prioritize another better seasonal event for Summer over a new piece of persistent content for June.

It might be an idea to return to next year, but the feedback clearly said our near-term balance was off - which is why we changed plans.

Too early to say right now. The only decision we've really made today is to move our development efforts from that project to these two.

We may very well come back to it for next year, but based on the feedback, we'd look at it in context of the balance of the amount of persistently available content released around it.

We'll pass this to the team to consider. I think I recall seeing a good few mentions of this in the Community Hitlist submissions as well!

I can promise this isn't the case for 2024 content. We want to give you a look ahead beyond June as soon as we can.

When it comes to this year, we won't hold any announcements around our 2024 plans for the sake of making a moment at RuneFest - we know you want that news sooner rather than later, and holding it for that would be a mistake.

If we do end up having some 2024 news shared at RuneFest, it would only because it was the right time to announce it for other development based reasons. But that isn't our intention or what we're aiming for right now.

So the latest Seasonal Events (Christmas & Easter) have been designed to be just that - something we can bring back each year and hopefully build upon with each iteration. Any time we put into those benefits us for years ahead.

Building that foundational level event takes as much work as any other content release though, so there's a balance to strike with our development time. From player feedback, that balance was clearly wrong for our near term content plans - might be more appropriate in future years, just not this one.

I'll add that to the disconnect report.

Reporting this to the team to see if it's scheduled at all. Thanks for sharing it.

Just to confirm - is this related to disconnecting when you start the mini-game?

I tried replying to this before you reposted, glad you did!

It's a good spot, and bad wording on my part rush typing this. Engine Updates in general are a lot more complex with a lot of testing / lead time - especially given we have to consider Mobile platform submissions.

Generally we target batch releasing Engine Updates to avoid knock on effects to our other Engine deployment timelines or creating bigger issues by rush testing. Even without rushing, this slipped through the net on our last one which shows the unintended impact any Engine Update can introduce when you have a game with 23 years of content to account for.

This fix itself has been prioritized for that next batch for April, but there isn't an intention to push it live as a standalone update earlier - at least right now - given we've been able to find a hotfix route.

EDIT: Worth mentioning the team are also looking into how this was missed and considering solutions for how we better cat...

This is just a specific fix for the Zuk effects at present as it's one of the highest reported. We'll mention this to the team and see if we have plans to address it - either with the Engine Update or as a hotfix.

https://preview.redd.it/kxx6yos78boc1.jpg?width=820&format=pjpg&auto=webp&s=99333f97b88ecbe7444585278e7f58b4d6cb54d4

The Zuk 'Pizza' phase is now visible again. Zuk's back on the menu 'Scapers!

It's worth mentioning this is an imperfect fix, as they team had to find non-engine based solutions to try and get this sorted as soon as we could.

With this update, Zuk's pizza phase should be playable once more. We've been able to restore the pizza phase's telegraphing and visible fire when it can damage you. This does lack the build up effects as the pizza fire arrives, but this should have minimal impact on the gameplay.

The root of the issue requires an Engine Update, which have a lot more implications to cover and testing requirements before they can be deployed. We should have a full engine-based...

We're ecstatic to be sharing first details on our upcoming RuneFest 2024 - we're talking location, first hints on what to expect at the show, how and when to get tickets and a bunch more!

Get the latest news at the links below. Looking forward to hopefully meeting many of you there later this year!

https://rs.game/RuneFest-FirstDetails

Hey all. We've been wanting to provide some reassurance on this quote and have been discussing across both teams this morning.

Ayiza just responded with an answer that's totally reflective of our perspective on the RuneScape side too, so I wanted to copy it to this thread on our subreddit.

"We know bots exist, just as much as you do when you see them in-game, but it’s important to highlight that the article does not accurately reflect our strategy. Our priority is to always ensure every player has a good experience when playing both RuneScape and Old School RuneScape.

Since the news of the acquisition came about, many of you have been saying we’re not banning bots on purpose, mostly pointing to how we’re padding out player numbers. That just isn’t true and would not be good for the game. We are banning bots, more than we ever have before. But the reality is, and this is something we’ve said time and time again, it’s an arms race. As fast as we ban them, new ...

Honestly a great point.

We default to not wanting to put anything up that's a non-announcement as it rightly tends to upset people - but we could have done something like 'Where's the next RuneScape roadmap?' potentially. We might be defaulting to that based on previous reactions a bit too much.

We'll consider it alongside some other changes we're cooking on for the Newspost front. Thanks for sharing this, good food for thought.

I getcha on it being a bit of a non response. I was hoping to just provide some context on why there's a delay in a roadmap and make sure people know it's not something we're ignoring, but that is the downside of doing that I admit!

In terms of Hero Pass being a delivery vessel for future updates, that I can confirm wasn't the plan for Hero Pass or the cause of the disruption. Hero Pass was designed as a layer on to other plans rather than an anchoring crutch that compromised content.

The disruption due to Hero Pass is a planning shift - we spent 2023 trying to involve players more than we had done for a couple of years, and keep building on that gradually over 2024.

Off the back of Hero Pass, the shift in planning isn't to do with Hero Pass being cancelled - more of a development mindset shift in how we think about a more player involved RuneScape. That will still take some time to progress this year, but our plans are being re-thought with that even more ...

We do have an outline for sure, but because of the other changes happening around them, we're not in a position to make committed public plans just yet.

I know that's probably a frustrating answer, but we just need to hold laying out a vision until we can say with full confidence that we're set up to achieve it properly.

Nothing to do with a Battle Pass - it's referring to the game itself and how we approach development overall.

This is a completely fair question to ask of us, especially given the lack of a roadmap or vision isn't in line with how we've been trying to do things in more recent times.

While I can't provide a comprehensive answer today, I do want to share what we can right now out of respect for these sorts of posts!

So the most important bit - we want to provide you a picture of what’s ahead as soon as we possibly can, and we’re working towards it as quickly as possible. We know it’s important and we’re all really wanting to make it happen asap!

The reason we didn't cap the year off with a roadmap (and have yet to have one) is really simple - we modified our plans in the later stages of 2023.

Hero Pass made it clear that we need to get more player voice into development, which has led to us re-assessing how we approach things. Mod Keeper mentioned it in his message following Hero Pass, but we have a desire to be a lot closer to all of you as players in our dev...

Just as a final update for this evening (unless anything goes backwards in which case we'll be here) -

The issue has improved but we don't believe the external provider has fully cleared the issue based on the last information we have. Please keep trying any hopefully things will be sorted in the near future.

If the issue hasn't fully cleared in the morning for any unexpected reason, we'll provide more updates.