Jagex_Stu

Just to provide some context, because of the sheer number of achievements that've been added in recent years and peculiar conditions they need to check, we reached the limit of how much achievement data our scripting engine can process, and had to recreate every achievement in an engine-cached format for efficiency and to support continued addition of achievements for game content.

Converting this data, extending the achievement engine to support some very quirky achievement conditions, and adapting the achievement interface to pull data from the achievement interface took about a year behind the scenes.

The fruit of that labor means the achievement processing code is now in-engine for efficiency and we can more freely add achievements in game content releases. (Where previously the fully-scripted system was at its limit.)

The necessary drawback of that is if we need to change the logic for parsing achievements, that's an engine change.

For what it'...

The latest I've heard is that Mod Jenesis (the engine developer that created the achievement engine) stepped in as Mod Asherz is unavailable and has already done the engine work to fix this (ignore all skill prereqs configured on achievements so you can boost them).

So it just needs to go through the engine review and testing process, but this is quite rigorous due to all the combinations of hardware we support and exceptions this creates. (We don't update the engine nearly as often as we release game content updates.)

It's scheduled to release in the next full stack engine build which is currently early February.

Your ability bar rotation can make a big difference to your DPS.

The optimal rotation will vary depending on what you're fighting and your equipment loadout, but if you're using Revolution++, this is a good place to start:

https://runescape.wiki/w/Revolution/Bars#Revolution++_bars

You can also right-click the cog on your action bar and choose "Setup action bar" to apply the default abilities for your current weapon to your current action bar (they're based on the optimal revo bars listed on this page).

You'll likely need to tune it a bit for specific targets, but I find it faster...

Please send an in-game bug report if you haven't already, and the issue will get repro'd by QA to resolve in our bugfix day between project sprints.

Took a look at the config and the Family Spirit Tree achievement currently has a skill prereq of 89 Farming.

Apparently that's a concession to those that completed the achievement before the Manor Farm tree was added to it, so that they didn't have to recomplete the achievement.

Regardless, you've completed the achievement, so there's nothing to worry about. :) The achievement system considers this achievement to be complete for you, and therefore you've met that requirement for MQC.

Similar principle to skill prereqs, yeah. Membership is a prereq and achievements default to members=yes if not specified. We copied across the member status of each achievement from the old achievement system, which worked the same way.

If there are specific achievements you feel should be flagged as members=no, please submit an in-game bug report listing those achievements and we'll get those fixed.

If you mean the Power of Three Spirits achievement in the Exploration->Prifddinas subcategory, IIRC that's listed with an 89 Farming req, which'd account for why it's completed at 112 Farming.

It sounds like you have the Show Completed tickbox unticked, near the top of your achievement interface.

If you'd like to see achievements you've completed to verify, tick Show Completed, then you should see achievements you've completed in your achievement subcategories and meta lists.

Hope that helps!

I don't have any new information on the subject to offer.

I can only reiterate what I've previously communicated, which is that making the achievement engine effectively ignore skill prerequisites so that they can be boosted requires a full-stack engine deployment, and currently only client engine releases are scheduled for the remainder of this year.

We discussed our options - stripping all skill prerequisites off all the achievements, setting all the prerequisites to 1 and living with the prerequisites appearing as incorrectly struckthrough, or changing the skill prereq logic in the achievement engine - and decided to go with the engine fix as the best long-term solution.

Our producers have also reassigned Mod Asherz and myself back to working exclusively on mobile for the foreseeable future to meet the deadlines they've set, so we need to balance that need against, and coordinate with the engine release schedule for, any further short-term work on achieve...

It applies to any achievement with skill prerequisite, regardless of category, due to how the achievement engine processes the requirements.

If an achievement has a skill prerequisite, then it currently uses your base level in that skill as the condition for that prerequisite. The achievement engine assumes that if an achievement has a prerequisite, then you must need that prerequisite to complete the achievement.

The only outlier might be where content has scripted conditions that themselves throttle whether the requirements for the achievement are flagged. (From what you've described, sounds like the content scripts that complete the wilderness diary achievements themselves checked your base skill levels, at some point.)

Actually, the reverse is true. If you complete the condition for an achievement by boosting, the requirement variables are set on your account.

So although the achievement is still locked, because you don't meet all the prerequisites, you have completed the unlock condition, rather than being permanently locked out.

So once you've leveled up to meet the base skill prerequisite, the achievement should unlock.

Sure thing! I've passed on your message to him.

As in quest cape?

All content-specific achievement issues have been addressed and released, to my knowledge, including prereqs for quest cape.

(There's some requested features that require an engine rebuild to resolve, like skill prereqs not using base stats, but doesn't sound like that's your issue as quest prereqs just depend on the relevant quest being completed).

Does your quest cape achievement list any quests still to complete? (You can now untick Show Completed (and tick Show Locked) so the completed prereqs aren't listed, which should make it easier to see what's remaining).

I'd otherwise suggest submitting a bug report in-game so we can look at your account and repro it that way.

I honestly erred on the side of caution with Reaper Crew as I know it's an important goal for a lot of players.

Figured putting it in the root of Combat would make it most likely players would find it acclimatising to the new system.

If the consensus is that Reaper Crew's up there with Final Boss and they should go in the same subcategory, I'm certainly open to moving it.

Or if there's a subcategory name that intuitively encompasses the 3 for bossers, feel free to let me know.

Thanks for your understanding!

Yeah, I've thought about where achievements should go...way too much! I hope that it's fairly intuitive, since every achievement has to have one place that makes sense.

The good news is recategorising is really easy in the new system, so there's room to reshuffle as the data set expands. Picking somewhere that makes everybody happy is the hard part. :)

I'm not sure what you mean about Ironman achievements. In the case that there's different conditions for ironmen, they use the same achievement as non-ironmen with overridden attributes rather than new achievements.

Magic has its own subcategory as there are several unique Magic achievements (mostly non-combat).

The Combat subcategory only contains skill chain achievements for the combat skills that don't have any unique achievements to justify their own category.

We opted to combine these as the Skill category is already quite long, and likely to get longer as subsubcategories get added over time.

If unique achievements for those combat skills get added in the future, we could split them off into subcategories pretty easily. But tried to shorten the list as much as we could as a baseline so you have less subcategories to scroll through

Achievement skill prereqs currently aren't boostable.

We're planning to revise that in the achievement engine, but we can't update the engine as often as we update game content, so it's likely to be a while coming.

We don't currently have any full stack (server and client) engine releases planned until at least the new year, but it's possible that could change.

Can't give an ETA at this time but communication on the subject is planned as details get ironed out with the engine team.

I don't like it either.

Thank you for explaining. That tracks with my understanding of their intended purpose.

We needed to balance that against the desire from other players for achievements to all be visible so achievement totals and RuneScore are consistent and trackable.

The middle ground solution that was taken was to give feats presence but hide the information until complete, to hopefully satisfy both parties.

I agree with you that, especially now the Feats are all in their own category, hiding feat information until they're complete is probably redundant.

I put the Feats into subcategories to help provide a hint, but that may not be enough.

Personally I'd like feat information to be visible. I can just choose to ignore the Feats category if I don't want to complete item logs. Hiding the info in-game just means I have to go to the wiki to get that information.

But are there players that prefer feat information to be obfuscated? Would other players wit...

I presume that's why these item logs are hidden away as Feats. ;)

"especially because you can't hide stuff you did in that view."

You can now hide stuff you did in that view. :)

• "Unchecking the 'Show Complete' checkbox on the Achievement interface will now remove completed steps in Achievement dropdowns, making it much easier to see what you have left to complete - super useful for those completing cape Achievements."

So untick Show Complete and all the white completed items in your Completionist Cape meta list will go away, leaving just the achievements you still need to complete.