Jagex_Stu

Yep, the Completionist category now only (other than the Feats subcategory*) contains the meta achievements for max, quest, MQC, comp and comp(t) capes.

The reqs for those cape metas are listed in alphabetical order.

Just click a req for the selected cape and it'll jump you to wherever in the system that achievement is located.

So the cape metas are basically an index that'll easily help you find their requirements to complete. :)

*Completionist->Feats is where all the 'hidden' achievements go. Previously these were invisible until you completed them. Now every achievement has a tangible presence in the system, so 'hidden' achievements have generic 'the details of this achievement are hidden' name and description until you complete them. So at least it's clear how many Feats there are. And they're bundled in one place so if you're not into chasing Feats, you can safely ignore them.

Membership is handled similarly to the old system - a prereq that's enabled by default (because the vast majority of achievements are members), and we can make a one-line config change (so not hotfixable) to make it F2P.

Prereqs are more rigidly applied than before to prevent ambiguous property errors - an achievement won't appear as complete if the prereqs aren't met, so we have to be very careful any prereqs are valid when you can complete them.

We copied across the current member data, so this is a great example where there may be existing achievement bugs that still need fixing.

When the project goes live, please do report any achievements that you find you should have complete in F2P, and we'll jump on correcting those prereqs.

Yep, I've seen plenty of lists for more achievements, true trim, etc. Great ideas out there!

I imagine there'll be an achievement bonanza or two in future years to exploit the breathing room we've added, but for now the schedule is planned out and locked in for many months, so we need to work on those assignments to hit deadlines.

Nope, doesn't work like that.

It doesn't make a difference to Steam what achievement system we have in-game.

The only power we have content-side is to send a message to the Steam module to let it know an achievement is complete.

All the Steam achievements are replicated in the Steam module by web systems liaising with Steam admins.

It's therefore unlikely we'd ever add achievements that grow organically and relock as requirements are added, like comp cape or Music Maestro, to Steam.

A game updating weekly that needs that much Steam achievement maintenance would be a real nuisance.

So we carefully picked Steam achievements for the initial release that are static unlocks.

(Mostly - 99 and a Flake will probably be a pain whenever we add a new skill, but at least that doesn't happen very often.)

To clarify, it isn't that it was previously implemented poorly. At the time, we requested time from an engine developer to build an engine-cached solution. That resource wasn't available at the time, so we had to do it all in our scripting language.

Which had sufficed for several years, but inevitably as more achievements got added to the system, we'd exceed the processing constraints imposed by that language (eg operations limit per server cycle to process that volume of bespoke data) and need to replace the interim solution with a long-term solution.

This time around, engine resource was available, so we were able to build the solution we wanted to have the first time. It happens, and it has certain benefits. (Not least of which to the end user in getting features sooner.)

I won't personally be - I've already been reassigned to my next project.

We've done what we can to lower the cost of doing that, but when and whether resource will be assigned to such a project is not my decision to make.

It's a constant balancing act. If we do that in the short term, then another project will be delayed in the short term. If other projects are higher priority to release at certain scheduled milestones, then those'll get done first.

Yes to all your points. :) And thank you for the hard work you all do maintaining the wiki!

Being able to hide subcategories that are fully complete is honestly the feature I'm most excited about in this update.

Feels good to not have to eg scroll past and mentally filter out the Archaeology subcategories I've completed while trying to find the incomplete subcategories in the list.

So glad Mod Asherz managed to squeeze that request in. We had to really fight to include it.

Yep, that was the reason. Nex and Telos are significantly above the difficulty of the rest of GWD1/2, and I figured people would be more likely to first look for Telos toward the end of the difficulty list than look inside GWD.

If there weren't dungeon-specific achievements (eg GWD2 reputation; GWD1 Kill Count Still Counts to create an omni soulstone) and non-boss combat achievements (eg War's Retreat, Final Boss), I'd've been inclined to stick to alphabetical boss subcategories. But given the achievements that needed to be categorised, difficulty order including dungeon subcategorisation where available seemed to be most appropriate.

To add to the excellent advice in this thread (thanks, guys!)...

The breadcrumb trail has a limited render distance (about 20 tiles from your destination). You're in Lumbridge and Draynor's the adjacent village to the west.

Since you have a path achievement selected, you should have an arrow on your minimap pointing in that direction when you're too far away for breadcrumbs.

If you open your worldmap (globe attached to your minimap), there should be a path objective indicator at your destination.

You can also double-click a place on your worldmap to set your own custom blue marker on your minimap to that destination.

As others have noted, the path system doesn't tell you step by step how to complete RuneScape's quests; just where to start a few suitably novice quests.

Part of the joy of RuneScape is that you explore its quests, pay attention to hints (your Adventures -> Quest journal helps keep track of your quest progress) and figure...

I do a livestream series reviewing Runescape's tutorials. The footage may help rekindle your memories. :)

Sounds like you played either Learning the Ropes:

https://www.youtube.com/watch?v=haaxzv2HEwo&list=PLMjuVhi1Lg6cAB0kFpGi3fTVKHanxdHv3&index=4&t

Or Unstable Foundations:

...

It was certainly a surprise to me too! Very glad that worked out for you. Enjoy Yak Track!

I'm going to hold onto your save for edge case testing, as its specialist focus has provided some interesting outliers to address!

Hah! I love players who have the same RSN as their social media name. Makes life a lot easier! :D

Okay, so this is a pretty wacky workaround, but it fixed your account for me:

• Make sure Settings->Gameplay->Information Windows->Guidance system hints is TICKED (it looks like your account hasn't made any progress in the Burthorpe paths, but with this ticked, you won't have to - you're over 100 skill level which should also make it unnecessary, but just to be on the safe side)
• Press the Home Teleport button (the H next to your minimap) and teleport to Burthorpe
• Log out and log back in again
• You should hopefully get a Yak Track Task List in your backpack when you log in, and be able to start the Yak Track

According to your variable states, you've not teleported to the Burthorpe lodestone before (which is impressive for an account with 150 skill level).

It looks like an obscure condition requires you to have flagged ...

Could you please let me know your RSN?

Or even better, please submit a bug report if you haven't already (I searched through our JIRA database but couldn't find a ticket that's been created as yet), so that we can get a snapshot of your account in order to repro your state, and therefore construct a fix.

To submit a bug report, press the - button in the top right corner of your player chat window, and choose Report, then Report a Bug->Gameplay.

Had a look at the code for Yak Track. From the messages you're getting, it looks like it hasn't initialised on login.

Best guess I have at the moment for a user fix, without being able to replicate and debug your exact account state:

In Settings, Gameplay tab->Information Windows: Tick Guidance system hints

Press F1 to open Hero parent, go to Achievements tab.

Press the bottom centre button on the Achievement Paths window - see if that'll let you Skip Tutorial or otherwise cycle to the ...

Thanks for putting this together!

I've read through it and also forwarded your list to the combat council.

Ninja are also seeing what they can pick out of it.

For what it's worth, I investigated this issue today and submitted a fix to QA to test.

So no need to send more bug reports. :)

Your activity tracker has 5 slots, so can consequently track a path and a quest at the same time.

You presumably have an objective from one of the Lumbridge skilling paths in your activity tracker.

You can right-click an activity in your activity tracker and choose Remove to remove it.

(Given the destination, the achievement's probably called You Doity Rat, It Was Dead Already, Camping Trip, or Ratatouille - Lumbridge path cooking rat meat.)

If your activity tracker isn't on your screen (assuming you're playing with the new interface system on the Desktop client), hover the sword and shield on your ribbon and press the Activity Tracker icon (looks like a pirate's treasure map).

I wish I had the luxury of choosing how I spent a week of development time! That is not my decision to make, however.

You touch on several points I would like to address if I had the opportunity. I certainly felt the limitations of Social Slayer you describe when attempting to slay with friends I introduced to RuneScape. (Particularly as you'll likely both need to world hop to find Slayer mobs you can grind, leading to the desyncing issue you mentioned.) Though realistically it'd likely take more than a week to rewrite Social Slayer.

Mod Shogun also did some work on improving low-level Slayer assignments in CXP, as I was able to convince our producer of the importance of doing so, before Mod Shogun was re-assigned to the ninja team. It sounds like that'd address several of the issues you raised.

His new team is aware of the remaining work to complete the project, and we're hoping he'll be able to finish it between other ninja priorities.

Given that, ...

The Morningstar fight was balanced around being prepared for combat, equipping armour and bringing food, and using abilities from the action bar to endure the fight. To reinforce those mechanics, he hits hard to encourage you to use what you've learned, and better endure future combat.

But even with starting stats and no armour, you should be able to take 6-7 of Morningstar's attacks without taking action, so a 3-hit suggests something's crippling her.

It's difficult to say what might be causing the issue without seeing her action bar, skills and equipment, but a few suggestions that may help (which Turael should've covered en route to this point in the tutorial):

• If you use the threshold ability that blinks on your action bar during the fight, and eat food to keep your health topped up (the Eat Food ability you put on your action bar in the previous stage makes eating more convenient), you should be able to outlast Morningstar even though he hits hard...

Thank you, Autumn Elite! The Death of Chivalry's certainly the quest I'm most proud to have developed in my time at Jagex. I feel very fortunate that Mod Osborne was my designer reviewer for that project. His feedback and guidance were instrumental in achieving the final product.