Template talk:Rewards item

Profession parameter

Would it be possible to add a 'profession' parameter for this template for items that are only rewarded to a player based on their profession? Sunlion (talk) 21:01, 27 September 2020 (UTC)

Just asking, what would be the purpose of such change? This template's main purpose is SMW property setting for other pages to be pulled by {{rewarded by}}. DJemba (talk) 22:25, 27 September 2020 (UTC)

What I meant was to allow, say, profession icons to be added to acquistion sections for pages about items only obtainable for specific professions for {{rewarded by}}. Sunlion (talk) 23:34, 27 September 2020 (UTC)

Well, I'm not very fond of this idea since it has only one use, namely Personal Story rewards.

The personal story rewards are:

1. Complete, all story pages list the correct rewards and all item pages list the correct stories.
2. Formatted nicely and minimally by hand which can't really done automatically without lots of effort

Simply compare your already updated page:

• Before: Rawhide Bracers (personal story reward)
• After: Rawhide Bracers (personal story reward)

You can't tell me that the second one looks better, I definitely prefer the previous format.

Note that I also intentionally decided to not provide personal story reward for the already mentioned reasons (complete and nicely formatted) when creating this template. My purpose was to simplify life where possible (on straight forward pages), not to brute force apply it everywhere. Replacing a manual list/table with a smw template should always provide at least the same amount of information and readability as before (preferably it should improve it), it should not get worse.

Hence, here I would suggest to find a way to mimic the current format first (not sure if possible), however on the other side I can't see a reason for it: repeating myself, the personal story rewards are already complete and won't change in future. --Tolkyria (talk) 09:11, 28 September 2020 (UTC)

Hard to improve on simplistic perfection from 2015 to be fair :) -Chieftain Alex 19:53, 28 September 2020 (UTC)

So should I remove the rewards item template from {{reward/1/2}} and just undo that edit or change all instances of {{item icon}} on that page to {{rewards item}} since {{item icon}} doesn't show up with {{rewarded by}} while still removing the profession-specific stuff having {{rewards item}}? Sunlion (talk) 04:29, 29 September 2020 (UTC)

In general if you can answer the following two questions with yes then it's a good idea to replace a manual text with a template generated one:

1. Does it improve the page in terms of information and readability?
2. Is it likely that the page needs to be updated soon again due to new content? (which wouldn't be the case with a template as it collects the updated information automatically)

For the personal story equipment I would anwers both questions with no. Mirroring the current format with the rewarded by template is kinda hard as it requires look-forwards and look-backs, e.g. setting the profession icons directly at the beginning is hard; we could easily pass the profession from the {{rewards item}} to {{rewarded by}}, but then it would show it e.g. on the page Rawhide Bracers (personal story reward) 15 times, for each story line. Edit: see example below.

However, let's take a look at Bag of Loot (container) stating: "All Personal story storyline steps except those awarding racial or order specific rewards (2-10)". For me that's pretty unsatisfing, and I can't see how anyone wants to do this by hand, furthermore, I would answer question 1 with yes.

I would say: yes, please revert your edits regarding personal story equipment (this can't be improved nor will it update in future), but I think it would be nice to to replace the other loot (e.g. Bag of Loot (container)) with {{rewards item|<item>|qty=<quantity>}} (Make sure to set quantity). --Tolkyria (talk) 08:19, 29 September 2020 (UTC)

Added examples section below. --Tolkyria (talk) 08:32, 29 September 2020 (UTC)

Examples

How it would look like by simply passing profession icons from {{rewards item}} to {{rewarded by}}:

Example 1

• Possible reward upon completing any of the following story steps:
  • Personal story
    • Chapter 1: Experiments Gone Wrong
      • Statics path
        • Snaff Would Be Proud
      • Dynamics path
        • In Snaff's Footsteps
      • Synergetics path
        • The Snaff Prize
    • Chapter 1: Getting the Band Back Together
      • Blood Legion path
        • Chain of Command
      • Ash Legion path
        • The Tribune's Call
      • Iron Legion path
        • Best Laid Plans
    • Chapter 1: Krytan Politics
      • Street Rat path
        • The Perils of Friendship
      • Commoner path
        • On the Mend
      • Nobility path
        • Welcome Home
    • Chapter 1: Forging a Legend
      • Defeat Our Ancient Foes path
        • A Weapon of Legend
      • Protect the Spirits path
        • Wild Spirits
      • Guard the Mists path
        • A Pup's Illness
    • Chapter 1: Following the Dream
      • White Stag path
        • Called to Service
      • Green Knight path
        • Mockery of Death
      • Shield of the Moon path
        • Awakening

Standardize template parameters and output

This template could use being standardized together with Template:Contains and Template:Gather. They are all used for the same reason, just in different contexts.

• This template defaults to chance=Guaranteed, while the others default to chance=chance.
  • Normalize to chance=chance being default for all
  • Bot edit unspecified story rewards to chance=Guaranteed, as this has been the assumption when they were added
  • Bot edit unspecified event rewards to chance=chance, as they may have been left unspecified assuming chance=chance was the default
• Add chance=choice as an option to this template.
  • Example: Template:Reward/The Battle of Claw Island/5 and other story rewards offering a choice are labeled as a chance.
  • Bot edit chance=chance story rewards to chance=choice and edit to "Choice of the following".
• This template includes the item notes on the source page, while contains/gather do not.
  • Add a "note style" parameter to all three templates, with options "normal", "hide", "small"
    • "normal" shows the note parenthesized behind the item (like the current implementation on rewards)
    • "hide" hides it on the source page (like the current implementation for gather/contains)
    • "small" shows (the note small paranthesized) on the source page
      • Would fix the current issue for gather/contains where the note has to be duplicated to show it
      • This also mimics the formatting on the pages referencing the objects
  • Don't change defaults at the moment (keep =normal for reward, and =hide for contains/gather); adding options is sufficient.
    • Later determine best course of action, likely will a unified =small be the best common default as it uses same formatting as guaranteed/chance/choice/historical.
    • Many contains/gather usages can be bot edited to =small with the duplicate notes removed.
• Show "(guaranteed)" for =guaranteed rewards.
  • Bot edit cleanup for duplicated notes on map completion rewards
• Implement "id=" in contains/gather

Slightly unrelated: Specifying qty=1 is a good thing documentation wise, as it shows that "I know one is possible", as opposed to "Some may be possible". Showing the (1) is not necessary, but some old templates are plagued with stuff like qty=0-2 when it actually is just a chance of qty=2.

Kinda related: Because the context is known on each page, there could be a benefit to the templates being invoked through a polymorphic {{gives|item}} or similar, as an editor shouldn't need to know which template has to be used.

--Hazasoul (talk) 19:40, 24 October 2025 (UTC)

Some good feedback here. I've modified this template to accept chance=choice and also made it show (guaranteed) for guaranteed rewards.

The {{gives|item}} suggestion is interesting, but in my opinion it is another template to maintain without much benefit.

--BuffsEverywhere (talk) 22:50, 25 October 2025 (UTC)