Jagex_Stu

We could theoretically reinstate those by triggering them from the area task code that flags the area task variable and achievement popup. Actually quite surprised they didn't continue to occur. (Presumably these special jingles were more deeply embedded in the old task system and didn't survive when we created a new achievement system.)

For clarity's sake, did these jingles happen when you completed the last achievement in a difficulty set, or when you claimed the reward from the task giver for that set?

That's a really good idea (a button that reveals the description if you click it, similar to the required items field in the quest interface). Would be the best of both worlds.

Not sure how achievable that is as Mod Asherz looked after the achievement system & engine work (I was the cheevo data monkey), so would need investigation, but I love that approach.

I hear ya. We may be able to append a tally of the total and completed requirements in a meta achievement to the meta's description. Not sure if we can do it the easy way by counting them up clientside, or if a new achievement engine command will be required to get that information. Something we'd like to look at when we're allowed to commit development time to improving the achievement interface, for sure.

To clarify, achievement paths are still a thing. I've just had to temporarily remove quests in paths until I can rewrite the path system to use the new engine-cached quest achievements.

You should, yes, but not because of that risk. I encourage any excuse to quest moar.

IMO, as much as I like my comp cape, there's only one cape better than the quest cape, and that's the master quest cape.

Thank you!

Alas, other than the above quest system decoupling that I snuck in during the Christmas downtime, and the engine change for boostable achievement stat prereqs mentioned at the bottom, I don't anticipate any further achievement development in the near future as long as finishing mobile remains CXP's #1 priority, unless a different team picks up something achievement-related in the meantime.

Rest assured, I do want to work on achievements/paths first chance I get - we have a whole second batch of additional achievement work, like rewriting the compare mode and improving the achievement interface - that was descoped from the 2020 release as getting the engine-cached data live was so time-critical (for continued creation of achievements for quests, bosses, Construction contracts, etc). It's definitely not "shelved", but currently mobile requires my team's exclusive focus.

<3

Ah, lovely. Thank you for the info. I copied the reqs from the wiki at the time of adding all the miniquests to the quest system. Those alterations for an Everlightened world make total sense.

Would you be able to please send these in an ingame bug report so they can be registered in our ticketing system by QA?

Yay, that's great to hear! Gratz! :D

That seems like something it would be better for us to fix with achievement data. The achievement either requires you to be in a members' area or it doesn't.

We simply copied across the member data from the previous achievements, so likely various achievements default to membership that need a F2P flag. (There used to be a policy that achievements always required membership.)

If you could send a bug report listing the achievements you feel should be F2P and you currently can't complete in F2P, we could resolve that as a bugfix without engine work.

That's a delicate one.

My preferred approach is that achievements that can't be completed any more should be removed. Therefore we initially removed Mobilise This.

However, some players who had completed the achievement were vocally upset because their special accomplishment had been taken away. The Steam Release achievement had also recently been released, so we re-enabled Mobilise This.

Have recently had conversations with Steam stakeholders and was able to negotiate permission to remove the Steam Release achievement.

However, whether we remove these timelocked achievements or keep them in, there's going to be people on the other side of the argument who'll be upset by the action taken.

The optimal solution is to implement a feature where if you've completed that achievement, it's visible to you, but you don't otherwise see it and it isn't included in achievement tallies.

That should hopefully make both parties happy. (Though it do...

If I remember correctly that was a feature of the old task system, before area tasks were consolidated into the achievement system in 2017, which chooses from one of several subtle variations of achievement jingles whenever you complete an achievement.

• If I remember correctly, the final decision was to retain the value of runescore highscores, rather than mirroring them to the runescore in the new achievement system, so that players didn't lose their highscore values
• I know nothing about a public API for achievements, so presumably no.
• Happy to. Dev blog news posts are a little trickier and require a good amount of notice, as they need to be localised for all languages we support, which puts extra strain on our translation and editorial teams, so it's something we have to factor alongside other project requests in their queue.

I just checked the live code against changelists and there doesn't appear to have been any changes to the Stuffed With Anima achievement for a long while, other than removing the progress messages (the new achievement engine no longer provides that data server-side to be able to put those in your chat), and switching to a call to the new achievement system when the achievement completes.

In case it's at all a factor in completing your achievement, from the code it looks like:

• You need to have completed 5 phases when you defeat Telos
• You need 100% enrage or more each time you complete a phase
• Your anima charge needs to be at the max value of 100 (whatever that means - I've yet to get a Telos kill - but it's different from your current enrage) each time you complete a phase
• The progress is saved on a boss instance controller, so ensure you're in a solo instance (I think that's the only way you can fight Telos anyway)

Ahh, of course.

Well, if you'd like to send a bug report about it so the request is tracked in our systems, I'd be happy to remove the Magic requirement from Family Crest when I'm allowed the time. (We don't do soft requirements for quests any more, but I could mention the blast spells in the combat description, if it isn't already.)

I'd like to recreate the quest paths after converting the path system to the new achievement format. (But can't give any ETA on that.) Good to know that someone finds it useful!

That sounds like a case where the Magic requirement could probably be removed from Family Crest, if it's not a hard requirement to progress.

Don't you need to cast each of the elemental Blast spells on Chronozon, and therefore need 59 Magic for Fire Blast? How are skillers getting around that?

• How much impact would these changes have on server/game performance?

Sufficiently negligible that a player wouldn't really notice. The quest system's doing more direct calls instead of bouncing through the old achievement system, so slightly more efficient, but the quest system is far from being one of our more processing-intensive scripts.

• Are future paths on hold until the path system gets an overhaul with the new system?

Devs can and do continue using the path system (eg the Archaeology tutorial path that was added). They aren't officially on hold (though personally before doing any future big path initiatives, I'd prefer to rewrite the path system, as the new data format is considerably more elegantly data-driven).

Edited! Thanks, buddy. It'll be our little secret... nobody else on the internet will know. >.>

As communication is a hot topic at the moment, I want to give you advance notice of a tech debt project I developed for a few days while working over Christmas, which if all goes to plan should release alongside the Valentines game update in mid February.

As you may have heard, we shifted over to a new engine-cached achievement format last year. The achievement interface displays nearly 3,000 achievements and some of their conditions are very programmatically complex, as RuneScape is a strange beast.

We'd basically reached the point where the volume of complex achievement data the achievement system needed to process was hitting the limits of our scripting language, so we needed to recreate all that data in a format the game engine interprets, to be able to continue adding achievements.

Over time we intend to gradually phase out dependencies on the old achievement system, so we can retire it. And consequently be able to improve its interface.

The old...