FANDOM


Forums: Yew Grove > The Required Achievement

There has been some discussion over what should be placed in the "Requirements" field for Achievement infoboxes. Achievement requirements as of now currently include a mixture of quests/miniquests, skills, and items.

Example

The Queen Black Dragonling achievement requires the Queen Black Dragon scale item, which requires 99 Summoning to activate.

In-game however, the requirements are displayed as:

nkp3tOw.png

The in-game achievement does not list the needed item or the actual requirement of 99 Summoning needed to unlock the pet, only the 60 Summoning requirement needed to access the Queen Black Dragon.

Proposals

Here are a few proposals using the above achievement as an example (feel free to add your own):

_____________________________

1 Strictly follow in-game requirements:

Requirements: 60 Summoning Summoning

_____________________________

2 Allow achievement, quest/miniquest, and skill requirements that are necessary to complete the achievement:

Requirements:

_____________________________

3 Allow achievement, quest/miniquest, skill, and item requirements that are necessary to complete the achievement:

Requirements:

_____________________________
* Song from the Depths is used as a quest example and is not required for the actual achievement

Allowed skills

For future proofing, another question would be what skills to allow in the requirements. For example, some quests require many skills to complete. If a quest is required for an achievement, should all the respective skills needed for the quest be listed on the achievement as well?

Discussion

Support proposal 2- Undecided on Allowed skills - Cuxrie (talk) 00:42, April 14, 2018 (UTC)

Proposal 2- Allowed skill i think should come from post-quest/miniquest or if it requires like playing a minigame or doing d&d then list the requirements of that. --Luis12345lts (talk) 00:56, April 14, 2018 (UTC)

1, but with comments - I think we should follow Jagex on this one. It'll get way too messy if we try and add multiple requirements which are all indirect requirements to the main achievement. The issue does come up with stuff like the QBD pet where you actually need 99 summoning to unlock the pet (unlocking the pet grants the achievement, not obtaining the pet) - we should mention this in the article somewhere, not the navbox. Haidro (talk) 02:40, April 14, 2018 (UTC)

Support 1 - Agree with Haidro, we take things straight from the game such as quest length, so I don't see why this shouldn't be the same. However, things that indirectly are requirements should be noted in the article as to avoid confusion User:KelseW/Signature 02:43, April 14, 2018 (UTC)

Quest length isn't a subjective matter unlike this. bad_fetustalk 15:19, April 14, 2018 (UTC)
Quest length can definitely be subjective, before we had the official length by jagex, it was done on a case by case basis. Also I'm not suggesting all the indirect requirements be removed from each page, just moved out of the navbox User:KelseW/Signature 15:23, April 14, 2018 (UTC)
How do you define an indirect requirement? For the above example, Proposal 1 that you are supporting suggests listing only 60 Summoning which is flat-out wrong when you need 99 Summoning to do it. I can understand not listing skill requirements for quests that are already listed for instance but the issue is moreso about Jagex listing wrong information. bad_fetustalk 15:28, April 14, 2018 (UTC)
For me, personally, an indirect requirement for an achievement is something that isn't listed in-game, but is actually necessary such as the 99 summoning. We can't do a lot about jagex not listing real requirements, but I don't think the indirect ones should clutter the navbox, but rather be listed in the main text. User:KelseW/Signature 15:34, April 14, 2018 (UTC)

Strong oppose 1 - Having incomplete/wrong information just because Jagex also does is ridiculous in my opinion. I honestly don't see why it's "messy" to have correct information in the navbox as opposed to misleading statements. From 2 and 3 I personally favor 3 but in this case I can see why some might find it cluttered compared to 2. Support 2/3 - bad_fetustalk 15:19, April 14, 2018 (UTC)

Support 2 or 3 - Additionally, in the page itself, add that the ingame requirement was listed incorrectly as trivia --Jlun2 (talk) 15:52, April 14, 2018 (UTC)

Oh yea, and report it ingame --Jlun2 (talk) 15:53, April 14, 2018 (UTC)

Soft support 2/3 - After some talking with fetus ingame, I'm leaning towards 2 or 3, however I'm worried that having so many requirements in a navbox will make the page look ugly. Fetus suggested having it be collapsible if it has more than x requirements to keep the page looking tidy. User:KelseW/Signature 16:03, April 14, 2018 (UTC)

Just in case anyone is confused, he's referring to me and not 3i+1 bad_fetustalk 16:07, April 14, 2018 (UTC)
Community content is available under CC-BY-SA unless otherwise noted.