Runescape

Runescape Dev Tracker




13 Sep

Comment

Good afternoon folks, it's time to find out what's going on This Week In RuneScape!

🐱‍👤 The Ninja team have taken aim at statues, pets, and more, which is great news for those of you chasing the Trimmed Completionist Cape! The weekly limit on the Shattered Heart D&D has been removed and a number of items have had their Grand Exchange buy limits adjusted. That's not all they've done though, so check out the newspost for more!

🌈 The recent Rainbow's End promotion is coming to an end. Grab the fabulous new Rainbow Outfit while you can!

🔧 We've got our usual haul of fixes, improvements and community goings on!

Read the latest news here: ...

Read more
Comment

It's been a while, but I think you might need to finish a conversation with Sir Owen first.

If you check your quest journal, it should have an objective of what to do next, to work out your current state.

It's not a Magic level requirement to use the grimoire, don't worry - Owen just has some info that'll be pertinent before starting the ritual.


12 Sep

Comment

you got me


11 Sep

Comment

Originally posted by Mortichar

Is something similar happening to the luminous snagglers on anachronia? The green pods are not visible when they land, so there's a lot of guesswork involved when dodging the special.

Yah it's the same projectile. Raised it with the engine team :)

Comment

This is awesome


10 Sep

Comment

What a lovely surprise to be lurking and then spot this. Thank you so much for the lovely comments, and what a cracking way to play the quest.

I wrote it when my daughter was particularly ill in hospital, and in hindsight I think that came out in Primrose.

Mod Raven did such a great job of turning the writing into a working quest. I’m sure he would have loved to put in replayability and a few other gameplay tweaks, but it’s a minor miracle that he got Her Story in to RuneScape at all.

Thank you so much again. Made my day.

Comment

Originally posted by AssHat_

Way to shoutout your team! I wish my work environment was healthy enough to do that

Honestly I love my team and weirdly enough the isolation of lockdown has only brought us closer together. Jagex takes a commendably supportive and compassionate approach.

If you fancy a career change, we're hiring for content developers, plus a variety of other roles!

...

Read more
Comment

Originally posted by Legal_Evil

Can you make it possible to get a Durzag or Yakamaru assignment only if your raid lock is open for these bosses and only get one kill needed for the task?

From what I've made out from the Reaper code so far, technically that sounds possible. But my goal this week was to get back the functionality that'd been lost.

Beatsmaster Dirtbag and Yamaharu (musical raids when?) were intentionally excluded from Reaper (including the Reaper's Choice list), so I made sure that came back. Particularly as some players were less than impressed to be assigned raids bosses this week.

I suspect it would be one of those situations that needs its own toggle, as some players may be willing to fight group bosses, but not to get a 10 person team together to do a raid, and resent having to lose a reroll to it.

There'd probably need to be some reward tuning too, even if it's only 1 kill, given it's a longer-form objective.

Comment

Originally posted by TrashPandaSpecialist

Another reason to love Easty and the Release Candidate team - they accepted the Reaper/Beasts boss requirements refactor I've been developing since Tuesday into RC, despite it completing WIP testing Thursday noon, which is usually past the cutoff for RC requests.

Can someone explain what this "Reaper/Beasts boss requirements refactor" is? As well as what "RC testing" means (inb4 Runecrafting) I'm OOTL

To answer your second question, last week I did some tech debt reduction on how boss requirements are defined for Reaper assignments and to display their requirements in the Beasts tab, while doing some player-facing QoL to consolidate how the activity tracker and Slayer counter display Reaper/Slayer task information.

Requirements for bosses had been defined in about 4 different ways over time, as the needs of individual bosses developed - some requirements were data-driven on a config defining the boss' attributes, some as embedded cases in the Beasts requirements but with those requirements not being visible to Reaper assignments, some that were both, some in a different method that overrode the data and substituted alternate requirement text, etc.

I consolidated those boss requirements into a consistent data-driven approach to minimise the steps to define the requirements for a boss and centralise their requirement data, with the aim of simplifying the process of...

Read more