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.

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.

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

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.

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.)

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.)

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.

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, 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.

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.

HYPE Toad intensifies!

Not that I'm aware of.

And you're most welcome. ;)

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.