Template talk:Rewarded by

Default

Is it possible to implement a default a la "This item has not been added to any page through the 'rewards item' template"? —Kvothe (talk) 21:09, 13 April 2020 (UTC)

Good idea. Added. --BuffsEverywhere (talk) 23:45, 13 April 2020 (UTC)

Thank you. —Kvothe (talk) 08:00, 14 April 2020 (UTC)

Wording and possibility

The wording should be changed, imho, to reflect when the drop is not guaranteed. ~SimeTalk 22:17, 22 April 2020 (UTC)

Currently the following wordings, splitting between single and multiple results, are used:

Events

* Completing the event <event>.

* Completing any of the following events:
** <event 1>
** <event 2>

Stories

* Completing the story step <story>.

* Completing any of the following story steps:
** <story 1>
** <story 2>

Raid NPCs (raid event rewards)

* Obtained by defeating <NPC>.

* Obtained by defeating any of the following enemies:
** <NPC 1>
** <NPC 2>

Strike Missions

* Completing the strike mission <strike mission>.

* Completing any of the following strike missions:
** <strike mission 1>
** <strike mission 2>

The following questions arises

1. Where should the possibility of a drop be reflected?
   • In the intro text. Hence there would be unordered lists: one possible and one guaranteed.
   • As suffix.
2. How should the drop rarity be stated in the template {{Rewards item}}? What's a good parameter name?
   • Is rarity too much related to the classic rarity "fine, exotic, ascended, etc..." s.t. we can't use it here? What would be an intuitive parameter name?
   • Are the two values "Guaranteed" and "Possible" enough? Should the default be "Guaranteed"?
3. Does the intro text need some further rewording?
   • Especially, should we keep the single and multiple results split?

--Tolkyria (talk) 08:16, 23 April 2020 (UTC)

Thank you for the thoughtful response. Originally, on some pages the acqusition was listed something akin to: "Chance to drop/Possible drop/Guaranteed drop from x/event/y." Personally, I would be okay with having the wording stay like it is now, but with (guaranteed/possible drop) next to the drops, similar how a historical drop is listed:

{{Rewarded by|<item name>|guaranteed}}

which would show on the item page like this:

* Completing any of the following events:
** <event 1> <small>(guaranteed drop)</small>
** <event 2> <small>(possible drop)</small>

As a last note, I want to say I am not really versed in how these templates work, so I would like to apologize if I have proposed something that isn't really feasible.

~SimeTalk 15:09, 23 April 2020 (UTC)

Feel free to suggest anything, the worst that can happen is a "no, that's not possible".

Comparing the formats

1. Stating the possibility in the intro text:
   • Pros: The more natural approach, that's how we would write it by hand.
   • Cons: Each reward context (event, story,...) may appear twice, for the guaranteed and for the possible items.
2. Stating the possibility as suffix:
   • Pros: Only one section per context
   • Cons: Mixing guaranteed and possible might look wierd, might get excessive (e.g. list of 10 items, all having the suffix "possible", there clearly the intro wins), might clash with the rewarded quantity (e.g. <event name> (10) (possible drop))

I would prefer the intro text solution, being the cleaner and more natural approach. Most of the items are rewarded by a certain context with the same behaviour, in such cases the suffix format might look redundant, listing the same suffix over and over again.

Regarding {{Rewards item|<item>|<displayed name>}}: the second unnamed parameter is reserved for the displayed name, we still need a intuitive parameter name to label the item as possible reward.

--Tolkyria (talk) 18:17, 23 April 2020 (UTC)

After the latest comparison, yeah I agree with you about the tweaked intro (which is the most similar to what had been used before). ~SimeTalk 19:22, 23 April 2020 (UTC)

(Reset indent) Added the parameter "drop" to {{Rewards item}} which can be set to "possible" or "guaranteed" (default, hence doesn't need to be set in general).

Adjusted the template to display possible and guaranteed rewards separately; adjusted the template in general to hopefully increase the code readability.

The intros (grouped together now, allowing to easily adapt the text... if anyone doesn't like the current wording, please go ahead and change it) are now the following:

<!-- Single result intro -->{{#switch: @@@ $$$
   | Event Guaranteed          = * Completing the event 
   | Event Possible            = * Possible reward upon completing the event 
   | Story Guaranteed          = * Completing the story step 
   | Story Possible            = * Possible reward upon completing the story step 
   | NPC Guaranteed            = * Obtained by defeating 
   | NPC Possible              = * Possible reward upon obtained by defeating 
   | Strike Mission Guaranteed = * Completing the strike mission 
   | Strike Mission Possible   = * Possible reward upon completing the strike mission 
  }}

<!-- Multiple results intro -->{{#switch: @@@ $$$
   | Event Guaranteed          = * Completing any of the following events:
   | Event Possible            = * Possible reward upon completing any of the following events:
   | Story Guaranteed          = * Completing any of the following story steps:
   | Story Possible            = * Possible reward upon completing any of the following story steps:
   | NPC Guaranteed            = * Obtained by defeating any of the following enemies:
   | NPC Possible              = * Possible reward upon defeating any of the following enemies:
   | Strike Mission Guaranteed = * Completing any of the following strike missions:
   | Strike Mission Possible   = * Possible reward upon completing any of the following strike missions:
  }}

--Tolkyria (talk) 20:50, 23 April 2020 (UTC)