Template talk:Objectives table header

Objectives order

I found one more achievement with inconsistent objectives order: "Albax, the Unlucky", id 6455 —Sp3l (talk) 00:50, 16 March 2022 (UTC)

Awesome work: you adjusted the objectives order and set the custom bit parameters. Honestly, at this point you could add the id directly to the template, a small note in the edit summary would be enough. I added the id.

Are you indirectly implying that the custom bit parameter should be useable without the requirement of blacklisting the id in this template? Sounds reasonable, if custom id is set to true in the header then it should use the custom order independently from the id being documented. --Tolkyria (talk) 09:14, 16 March 2022 (UTC)

Mmmh, I think I am in a way, yes. But at the same time, I think I prefer the idea of requiring all the ids to be documented and confirmed to actually need custom bits first. I'm generally always in favor of systems that reduce the possibility of human error or abuse, so I'd personally keep the requirement. —Sp3l (talk) 15:05, 16 March 2022 (UTC)

Objectives Order 2: Electric Boogaloo

I noted that the Kaineng Unmade achievement was showing the incorrect step as still needing completion for me, from the API. I was about to change the 'custom bit' values to the correct ones, but previewing had no change in behaviour after that. I believe this is because this achievement is not on the blacklist. I don't quite know how to get the ID for this achievement, but I don't see it on the list. Worth adding so that the custom bit argument actually does something? Can someone check my working? I also posted my findings on the Talk:Kaineng Unmade page. Apotheotic (talk) 19:01, 5 April 2023 (UTC)

Thanks for the feedback! I've added the id for Kaineng Unmade to the blacklist. You're right, the custom bits weren't working because it wasn't on the blacklist. I think maybe we should reconsider letting the custom bit be usable without editing the blacklist. --BuffsEverywhere (talk)