Ok Jagex? Should you not have rolled back yesterdays update considering it A) broke all worlds, and b) seems to have borked the achievement system as well? I have trim and mqc (minus effigy inc) yet I've only completed 6/73?
Seems to be these "feats" which contain sweet FA information on how to complete..
If it's stuff like collection log titles, they shouldn't be under comp, since they aren't needed for trim or MQC.
External link →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.)
It's not the first time a rework or update didn't work as planned so I'm wondering why you don't offer the community an extra (test)server to help you out finding bugs or make suggestions for the current project to improve it. Many many things could've been found way before the official release.
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 cadence, and players have been pushing hard for gameplay-additive updates to be more frequent.
Considering the volume of data we had to recreate, very few issues with the achievement data have slipped through. And due to the elegance of the new system, we already have fixes prepared to address them in the next release.
There's a larger question there of beta testing as a standard element of the development cycle. We likely wouldn't be able to update weekly if that were the case. Updates would likely either be released with more known issues or would be postponed to go back under the knife much more often. Perfectionism can be paralysing. Would it be worth it?
The feedback loop would be helpful to make releases more stable, but there's always more you could do to make an update better, and always something else that's higher priority, so at what point do you draw the line? Fortunately that's not my decision to make.
If you're moving Feats do you plan to just display the criteria for these hidden achievements? It's silly to even display they exist but each one is "Haha just play the game bro!"
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.
devtrackers.gg
