Er the m+s rework had major issues on release and still had issues years later and do you remember that time he did a full comp rework? Owait no it didn't happen. nty.
Er the m+s rework had major issues on release and still had issues years later and do you remember that time he did a full comp rework? Owait no it didn't happen. nty.
Love you too, man.
If that were true at least some of these would be comp/trim reqs by now since we were told a year and a half ago that old/missing reqs would be added retroactively lol;
Mazcab wildlife reserve + reputation
GWD2 reputation (component blueprints (comp) title (trim))
Agent of the eldest outfit
Vanquisher outfit
Raptor outfit
Omens outfit
May or may not be title
Ravensworn title
Gold nomad cape
Max heist + cabbage fp unlocks
Shattered worlds abilities (comp) + outfit/pet (trim)
Sceptre of the gods
The survivor title + t3 dom medallion
Advanced fire cape
The distracted title
The tool title
The elite title
Unlocking expertise achievement (all abilities)
Max aquarium prestige
Unlock all 5 chisels (from statue monthly)
Own all elite skilling outfits (available in game and most alr have achieves)
The archivist title
Return gregg herrings lost ring
Witchdoctor outfit
Unlock runespan portal redirect + fully upgraded wicked hood
A lot of these even already have achievements and just need to be moved over to comp reqs.
Can I suggest you point these towards the ninja team. I have neither the technical setup nor the remit to add comp requirements.
It's also weird to say you don't have the technical setup to move an achievement from a general category to the comp cape category. And that it wasn't related to your task of a major comp cape overhaul. when half of the task that you actually completed was adding and removing a couple achievements.
I was the designer on the comp cape rework. Part of my remit there was establishing and agreeing that we could add new comp reqs (as it had been a controversy in the past), which including making changes to the relationship it has to avatar power. With those changes, we're now free to add reqs without taking away anyone's power.
However, I haven't been a content developer now for nearly ten years. I don't have the tools for coding installed on my machine and in general I'm rusty enough that I shouldn't be trusted with even simple technical changes in isolation in case I cause a catastrophic regression bug. Even if I was a content developer, we have work assignments that we're expecting to prioritise. I work in the episodic team designing (and designing the relationship between) content releases, so within that framework I can and should suggest that the content we're adding include comp reqs.
Adding old content to comp is something I personally support, and as of the rework is now something that can happen from a policy, balance and technical perspective. However, actually doing that work isn't something we can simply click our fingers and have happen - it has to be scoped, prioritised, developed and tested. Prioritisation is key - even if we all agree it should happen, doing it means something else gets pushed back.
Because the episodic team don't really have time for this sort of thing we actually did set up an entirely separate team to handle improvements and QOL updates to old content, and that team is the ninja team. I don't, and shouldn't, have any authority to pressure them to prioritise things in any particular way. However, they are very interested in what players want, hence my suggestion that updates of this sort be sent to them.