Hearthstone Wiki:Editing policies/Mercenaries bounty encounters

This page states unofficial Hearthstone Wiki policies applied to Category:Mercenaries bounty encounters articles.

All editors will be expected to follow these policies in normal situations.

Style guide for Mercenaries bounty encounter can be found in Help:Style guide/Mercenaries bounty encounters.

General

• Only one {{CustomBountyScenario table}} can be represented in an article.
• It's suggested that you use {{CustomBountyScenario description}} to let it return the default description of the article for consistency between articles.
• Name of the article can be whatever you desire, but it's suggested that
  • you come up with a name that can be easily searched with Special:Search
  • the name is meaningful so that readers can get the basic idea of what encounter may consist of
    • For boss encounters, you can simply name like <Bounty name> (NULL)/Heroic Encounter. Ex: Taran Zhu Heroic Encounter, Y'Shaarj Encounter
    • For normal encounters, let's say you encounter 3 Taurens with all 3 roles, you can name it 3 Role Taurens.
    • Let's say you encounter 2 Mercenaries/Naga Battlemages and a Naga Commandant, you can name it 2 Battlemages 1 Commandant, or Naga 2 Protectors 1 Fighter
• Do
  • Write the sentences in proper grammar.
  • Excluding Notes and Tips sections, use "the player" instead of "you".
  • Keep the sentences brief, but meaningful or useful to the readers. Remove sentences that add nothing useful to the article. This is a game wiki that is supposed to give the players information to help them play games, not a lecture.

• Don't
  • Use the unofficial abbreviations (Not many people will understand what BTX means, since it's an unofficial term made up by the community).
  • Mention a card without at least making a hyperlink to its wiki article in an entire section you are editing.
    • In the same section, you can make multiple same hyperlinks to an article, as long as the length between them are long enough (There is no exact restriction about how long it is needed, but try not to overuse the hyperlinks).
  • Evaluate any cards or any encounter under any circumstances. Especially, do not use these kind of sentences:
    • This is a hard fight that requires proper setup and careful management.
    • <Equipment name> is the answer to this encounter.
    • Shado-Pan Infiltraitor is essentially Diablo with Black Soulstone {0}.
  • Add the redundant information that was already represented in other sections, especially notes in Characters section.
  • Use the unofficial terms (comps, compositions)
  • For now, add the information about encounters that consist of collectible mercenaries. They are likely to be created by random algorithms.

Bounties

• It's suggested that you use {{CustomBountyScenario bounties}} and define the list of bounties ids or pages in {{CustomBountyScenario table}} let it return the list of bounties.

Characters

• Generally, all characters (mercenaries and minions) are heavily modified in encounters, so the card data we get in client are not often useful. At its base, they will be included a lot of token variables/attributes that we can modify. That's why {{CustomBountyScenarioCharacter table}} exists to allow us to fill in information about how those cards actually look like in game.
• Do
  • Keep all {{CustomBountyScenarioCharacter query}} and {{CustomBountyScenarioCharacter table}} between {{CustomBountyScenarioCharacter intro}} and {{CustomBountyScenarioCharacter outro}}.
  • Only use {{CustomBountyScenarioCharacter table}} if {{CustomBountyScenarioCharacter query}} does not return the character you desire.
• Don't
  • Delete {{CustomBountyScenarioCharacter intro}}, {{CustomBountyScenarioCharacter query}} and {{CustomBountyScenarioCharacter outro}}.
  • Leave wikiId and wikiName empty. They are needed so that you can use them in other encounters.
    • Both of these must be unique.
    • The last wikiId that has been used is 1. You can use |wikiId=2 for the next character you want to define. You can also visit {{CustomBountyScenarioCharacter table}} to see the full table.
    • wikiName can be anything you want, but it's suggested that you name it so that you and other editors can easily remember.

Tips

• Try to avoid suggesting combos that require treasures. Treasures are offered randomly and inconsistent in securing victory.
• Do
  • Add any combos between abilities, interesting equipment choices of mercenaries that may help you gain significant advantages or completely counter the bosses' strategies. (You can explain how it works after you mention the combo).
    • Examples: Mercenaries/Xaravan Heroic Encounter#Tips
  • Add the tips about collection (tips that help the players complete tasks more efficiently or faster using a certain encounter). However, you need to create a smaller section called Collection tips below the game tips, which will be called Game tips.
• Don't
  • Add generic strategies like role advantages, suggesting use generically powerful parties. For example, if you know the encounter has 1 Protector and 2 Caster, don't just say "Just bring 3 Casters/blue". Another example like "Just bring fire comps." is something you should absolutely avoid.
  • Evaluate any cards or any encounter under any circumstances. Especially, do not use these kind of sentences:
    • This is a hard fight that requires proper setup and careful management.
    • <Equipment name> is the answer to this encounter.
    • Shado-Pan Infiltraitor is essentially Diablo with Black Soulstone {0}.
  • Suggest cards ambitiously or without specifying why it's useful. Example: "Inferno {0} can clear everything."

Dialogues

• You can specify these kind of triggers: Start of Game, <character> using <ability>, Idle. Death is associated with the characters' card basic voicelines only.
• You must include the audio file along with the voiceline if possible. For example: <sm2>VO_LETL_827H_Male_Satyr_Attack_01.wav</sm2> Curse you!.
  • To find the right audio files, you can check out MISSION_AUDIO.txt file, which can also be opened in the Hearthstone folder on PC devices. Ctrl + F is your friend.
    • The left columns are actually the global strings of the voicelines, but the audio files are generally named after them.
    • You can test it out by typing [[File:VO_<id> on wiki editor. You will be suggested a list of files that you may be looking for.
• Examples: Mercenaries/Xaravan Heroic Encounter#Dialogues

Patch changes

• You can add the changes freely, as long as they are true, specific and brief. Moreover, you will need to add references using <ref> and {{cite web}} if you have anything to prove.
• Remember to start a sentence with one of the Category:Patch templates. While you are typing after {{, if you type long enough, you will be suggested a list of patch templates that you may be looking for.