Jagex_Stu

I appreciate this isn't entirely answering your question, but Agoroth is a F2P boss, and A Shadow over Ashdale which unlocks it is a F2P quest. :)

Now, it's a safe-death F2P boss aimed at novice players, and therefore is weekly to throttle the rewards. Which I imagine isn't fulfilling your criteria for a F2P boss, but balancing-wise that's how we had to do it to meet the accessibility aim and not release a no-risk highly accessible wealth-injecting loot pinata.

Incidentally, we do see healthy weekly engagement with Agoroth even in its current state. Those black pearls seem to still be desirable even 6 years later.

My personal opinion is that hidden achievements are a silly idea. But they exist and so we had to support them.

Inclination currently is to first move Feats and see where that sits with players.

Future options for hidden achievements are to leave as-is, unhide them, or unhide aspects of them (eg name or description).

Need a better understanding why they even existed as a concept in the first place to decide how best to proceed.

AFAIK they were originally hidden until complete because they're bananas niche achievements that most players don't want to feel obligated to (or can't) complete.

Shoving them in their own Feats category might achieve that goal without needing to hide information, but not sure yet.

While a beta test would've been ideal given no time constraints or dependencies, I think it would've done more harm than good in this case.

A beta test would've postponed the update by at least a month, even if we received almost no feedback (and only a tiny proportion of players participate in betas, so gives us the tiniest sliver of player eyes (ouch, that's a painful metaphor!) compared to the issues we were able to find and correct yesterday).

We needed to align the update with the last server-side engine release scheduled for this year, so we wouldn't've released 'til 2021 if we beta tested.

Meanwhile, updates in (and nearing) development need to add achievements, which the old system could no longer sustain.

We've had to be incredibly frugal in releasing achievements this year until we overcome this obstacle.

No more achievements means no quests, no Boss Slayer, etc. So postponing engine-side achievement caching would slow our release c...

We're moving those Feats into their own category, so that should alleviate that confusion. My apologies for the inconvenience in the meantime.

The outage while we released a new engine build was unfortunate, but also resolved promptly. (It's a tricky process, hence we don't update the engine very often, but a new engine build was necessary for the achievement engine.)

Hi, there's currently a bug where this achievement has a prereq of Birthright of the Dwarves instead of Watchtower Quest.

Your achievement is complete having performed the action, and will appear as such once the fix is deployed in the next Monday update.

Sounds like you've not completed the reworked version of Death Plateau.

You can find more comments on this topic over in this thread: https://www.reddit.com/r/runescape/comments/jmn1wm/bug_death_plateau_showing_as_not_completed_for/

I realise you said below that you've completed the reworked version. But the quest system was previously using the variable for the old version of Death Plateau to track whether you'd completed it, which we fixed in today's update, which sounds like it accounts for the discrepancy you're descri...

Good point and thanks for the image! The issue's more with the achievement overview interface, which is packed (and that's a whole other can of worms).

But regardless I think it's fine to omit a Feats progress bar, since by their nature feats are niche optional extras that most players won't care about. (And I think that's reflected in how folks aren't keen on the Feat tally currently counting towards the Completionist category and causing confusion.)

From what we've heard from the Ninja team, it's a bug that the Slayer codex has an extra vyre soul at the bottom of it, and they're intended to remove it. (Consequently the accompanying To Be a Master achievement currently stops at liverworts.)

I agree with D-J-9595's assessment.

I'll investigate 2) after some sleep happens. Thanks!

Thanks very much for your understanding! I love quests too.

On the upside, completing General's Shadow will get you a step closer to Master Quest Cape.

I heartily recommend going for that, and I hope the more granular subcategories make that goal easier to break down.

A requirement for the General's Shadow miniquest accidentally slipped in to the quest cape's requirements.

We have a fix ready to release in the next scheduled game update, but it needs a coldfix, so likely can't release 'til Monday.

If you can't wait, I'd suggest completing General's Shadow to get your quest cape back in the meantime. (There's a good quick guide for it on the wiki.)

Thanks for reporting this! We've already implemented a fix to replace this prereq with Watchtower Quest, ready to release in the next game update.

We aren't able to hotfix changes to configs, so we can't deploy a fix until there is a game update coldfix.

So I'd suggest that if you can't wait until the next Monday update, completing Death Plateau will fix the issue for you in the meantime.

Thank you for this!

Boss pets are currently configured to appear in a Combat->Boss Pets subcategory, so aren't visible at the moment.

We'll reorganise the boss pets so they appear in the relevant Combat-> subcategory.

Several novice quests in Burthorpe and Taverley were reworked in 2012 but still trick the quest system into thinking it's completed if you completed the pre-rework version, with a really nasty exception that doesn't propagate well to external systems (hence the engine-side achievement system is unaware of it and only checks the reworked version of Death Plateau).

We'll work on implementing the branching logic on this achievement to support both in the new achievement system, but in the meantime I'd suggest talking to Commander Denulth in Burthorpe and completing the reworked version of Death Plateau so that the quest is properly complete. (Since the achievement engine is config-driven, we won't able to hotfix this.)

We're restricted in the number of categories we can have due to screen real estate on the overview and player examine screens.

(I had to actually remove the Completionist category from that screen to make room for Lore and Area Tasks. But since Completionist only contains metas (all the actual achievements are distributed to appropriate subcategories elsewhere) and feats (which are extremely niche hidden achievements that only a true completionist is likely to chase), it seemed to be the one we could most afford to lose from the overview screen.)

We're certainly happy to move Feats to another category such as Activities, since it seems to be causing undue confusion.

We could potentially upgrade Feats to a category, with the proviso that we wouldn't be able to display that extra category on the overview and player examine screens.

The cyan quest name in your quest list indicates your active quest to show guidance, like cyan boxes on your map for the current objective areas.

Right click a quest in your quest list and you should have an option to toggle map hints, so you can either set a different quest active or turn the guidance off.

Yep, area tasks = task sets = achievement diaries. They've been renamed a fair few times. :)

And yes, I think the way each area's difficulty tier now has its own subcategory is going to make completing area tasks much easier to manage.

I can't comment on Steam achievements. That's out of my hands. I go into more detail elsewhere in this thread.

Not that I'm aware of.

And you're most welcome. ;)

HYPE Toad intensifies!

MQC meta achievement is still in the Completionist category where you'd expect it. :) Same for max, quest, comp and trim cape meta achievements.

The Completionist->MQC subcategory with over 200 achievements in it has been moved to a Lore category and split up into subcategories for miniquests, lore books, sagas, post-quest content, etc, to break that gigantic scrolling list down into more digestible focused subcategories.