Please remember to make use of the Manual of Style and Code of Conduct during your stay on the wiki.

Template talk:EventBox

From Dragon Mania Legends Wiki
Jump to: navigation, search
SUGGESTION

Make sure to first read the Event Article Model as it outlines the process for creating articles.

The EventBox is fairly complex and is made up of over 30 parameters which become more complex over time and whose number grows. This means that reading it thoroughly might become tedious. As such, provided you do not have the patience for it, we recommend picking an appropriate event from these groups and then use it as the basis for creating a similar event. Since some parameters are not used by all events, those needed for the type of page chosen are already selected and this article can be referenced for the documentation of said parameters.

The EventBox is a powerful template that is able to automatize a certain percentage of an event page. The more generic an event is, the larger the automatizing is. For example, in the vast majority of cases, Clan Events and Hatching Events are fully automatized (meaning that a simple placement of this template, without any additional information, is enough to generate the contents for those events). Aside from manually-written information needed to generate content, the EventBox uses other variables and templates to determine the type, color, starting date and ending date of an event.

To get a general grasp of how templates work, visit MediaWiki Templates and the Manual of Style. The EventBox is fully explained in a way that anyone, regardless of their knowledge of wiki software, will be able to use. If you want to make a suggestion or find the instructions are unclear or insufficient, feel free to contact the staff who maintain the template (namely Star Warden and Soukupmi).

Creating a template on any page is done by adding the name of the template between double braces: {{EventBox}}. If the event is 100% generic, that line is enough to generate its contents. If additional information is needed, additional parameters must be filled in.

Note that, in this article, the term "regular events" is used to represent those events that occur regularly, on a weekly basis, in which Trainers compete against other Trainers while the term "profile" is used to represent those elements that display the representative images of an event, namely Banner, Milestone, Leaderboard, Faction, Advertisement and Calendar.

Parameters[edit]

% USAGE

  • Extremely Low < 5
  • Low 5-15
  • Medium Low 15-25
  • Medium 25-45
  • Medium High 45-55
  • High 55-65
  • Extremely High > 65
  • Parameters are built-in segments that produce different content depending on their given value. When using any other word in the template which is not defined as a parameter on the position of a parameter, the template will simply ignore it.

    To use any parameter, add it before the last double braces, making sure to add a | before each parameter. To assign a value to the parameter, add the equal sign after it and add the value after the sign. If the EventBox only needs one parameter (as is generally the case with regular events that offer Dragons as prizes) then the entire line of code will stay on the same line. If two or more parameters are needed, then the beginning, ending, and each parameter will be on a separate line. See the examples.

    Note that some parameters only respond to certain values while other parameters respond to any value. "Built-in Values" represent those values to which the parameter will respond and must be manually inserted while "Default Values" represent the contents the parameter will generate if no value is attributed to it. The former will not be functional unless it is given a value, while the latter will be functional regardless if a value is given or not (unless they are overridden by other parameters).

    The position of the parameters inside the template, when creating articles, must be strictly respected as per below.

    special[edit]

  • Usage: Extremely Low
  • Status: Obsolete
  • Examples: Crowded Nursery (15/01/12), Dinnertime! (15/02/10)
  • Description: Used when an event does not have any relevant images.
  • The parameter completely cancels the profile of the event. Starting with the 30th of August 2018, each event now has at least one representative image, either generic or custom made, thus this parameter has fallen out of use.

    specific[edit]

  • Usage: Extremely Low
  • Status: Semi-Active Usage
  • Built-in Value: novip
  • Example: Green Day (18/04/09)
  • Description: Used only when a Calendar Event does not double the prizes for Trainers with an active VIP Status.
  • This parameter responds only to the built-in value and any other values will be ignored. When used, it will eliminate the line of text related to the VIP Status under the Notes section of the event.

    generic[edit]

  • Usage: Low
  • Status: Semi-Active Usage
  • Built-in Values: 1, 2, 3, 4, 5
  • Examples: President Day (16/02/15), Dinnertime! (15/11/20), Masked Mischief (16/02/05), Golden Gatherer (18/01/05)
  • Description: Generates the contents of the leaderboard when said contents can not be generated on their own.
  • There are several generic leaderboards that are used for the vast majority of regular events. These can be found here. Some types of events have their own generic leaderboard (such as Hatching Events, Gem Spending Events and Clan Events). Other events make use, more often than not, of a particular generic leaderboard:

    The parameter responds only to the built-in values. In those cases in which the automatically assigned generic is not applicable, add one of the values to display the correct generic.

    table[edit]

  • Usage: Low
  • Status: Semi-Active Usage
  • Built-in Values: 1, 2
  • Examples: Dinnertime! (17/10/20), Sweet Victory (16/05/23), Draghi Italiani (15/06/01), Pixel Perfect (15/08/21)
  • Description: Used when a regular event does not have either a generic leaderboard or a generic milestone and a generic leaderboard.
  • In those cases in which an event has any of the built-in generic prizes and the generic parameter is also not able to retrieve matching data, this parameter must be used to either negate the leaderboard or negate the milestone along with the leaderboard. Depending on what is excluded, the prizes must be manually added through the use of {{Milestones}} or/and {{Leaderboard}}. Note that milestone negation is not possible without the inclusion of the leaderboard, because the milestone is generated ahead of the leaderboard. So, even if it happens that a milestone is generic (but a leaderboard is not) both must still be negated.

    The parameter responds only to the built-in values. 1 is used to negate both the milestone and the leaderboard while 2 is used only for the leaderboard.

    These events have manually added milestones or/and leaderboards and thus can be used as the basis for new events:

    picture[edit]

  • Usage: Extremely Low
  • Status: Obsolete
  • Examples: Crowded Nursery (15/02/02), Lunar New Year (15/02/16)
  • Description: Used when a regular event does not have one or more of Banner, Milestone and Leaderboard.
  • Add the name of the image while omitting File: and its extension, which will override the profile, and add the image in place of it. Same as with specific, this parameter has fallen out of use.

    [edit]

  • Usage: Extremely Low
  • Status: Obsolete
  • Examples: Hatching Hearts (18/06/07), Golden Gatherer (18/06/08), Weekend Dragon Race (18/05/18)
  • Description: Used when an event has the exact same banner of another event that has already occurred.
  • Add the name of the image while omitting File: and its extension. Same as with specific and picture, this parameter has fallen out of use.

    milestone[edit]

  • Usage: Extremely Low
  • Status: Semi-Active Usage
  • Examples: Freedom's Reward (16/07/04), Legends 2016 Final (16/07/08), Dinnertime! (17/08/04)
  • Description: Used when an event has the exact same milestone of another event that has already occurred.
  • Uses the same mechanics as banner, but adapted for the milestone. Has generally fallen out of use, but it can still be used when the event is presented with a non-generic milestone of an event that has already occurred in the past.

    leaderboard[edit]

  • Usage: Extremely Low
  • Status: Semi-Active Usage
  • Examples: Farming Fanatic (15/09/11), Celestial Sightings (16/06/06), Whelp Day (17/10/05)
  • Description: Used when an event has the exact same leaderboard of another event that has already occurred.
  • Uses the same mechanics as banner, but adapted for the leaderboard.

    calendar[edit]

  • Usage: Extremely Low
  • Status: Semi-Active Usage
  • Examples: Wings Up (17/02/13), Blizzard Bells (17/12/15)
  • Description: Used when a Calendar Event has the exact same calendar of another event that has already occurred.
  • Uses the same mechanics as banner, but adapted for the calendar.

    chain[edit]

  • Usage: None
  • Status: Inactive
  • Examples: None
  • Description: Used when a Chain Breeding Event has the exact same chain breeding depiction of another event that has already occurred.
  • Uses the same mechanics as banner, but adapted for the chain depiction.

    faction[edit]

  • Usage: None
  • Status: Inactive
  • Examples: None
  • Description: Used when a Faction Event has the exact same faction rewards and description of another event that has already occurred.
  • Uses the same mechanics as banner, but adapted for the faction image.

    map[edit]

  • Usage: Extremely Low
  • Status: Semi-Active Usage
  • Examples: Boss Challenge (18/02/26), Boss Challenge (18/07/30), Boss Challenge (18/10/22)
  • Description: Used when a Relay Event does not have a generic map or its generic map can not be displayed.
  • Uses the same mechanics as banner, but adapted for the map.

    [edit]

  • Usage: Medium
  • Status: Active Usage
  • Default Value: {{Exists}}
  • Examples: April Food's Day (17/03/31), Golden Opportunity (17/05/19), Dinnertime! (17/11/10)
  • Description: Used when an event needs to have its advertisement manually added in.
  • Normally, {{Exists}} checks against either the title of the page or the value of prize to retrieve a matching ad. The name of the file must either follow this pattern: File:NameEvent (yy.mm.dd) Advertisement.jpg or this pattern: File:Name Dragon Advertisement (NameEvent).jpg. In those cases in which a pattern is not found, the advertisement must be manually inserted. Add the name of the image while omitting File: and its extension.

    started[edit]

  • Usage: Extremely Low
  • Status: Semi-Active Usage
  • Default Value: {{GetDate}}
  • Examples: Child's Play (15/06/09), Crowded Nursery (16/12/05), Revolutionary Spirit (15/07/03)
  • Description: Displays the starting date of the event per the following format: 8 January 2015.
  • The starting date is automatically generated through the use of {{GetDate}} which extracts the date from the title of the event, thus this parameter is used to override that date. As there are few cases when date overriding is needed, the usage of this parameter is scarce.

    ended[edit]

  • Usage: Medium Low
  • Status: Active Usage
  • Default Value: See below
  • Examples: Golden Opportunity (17/03/16), Crowded Nursery (17/05/22), Dragon Dynasty (18/02/16)
  • Description: Displays the ending date of the event per the following format: 8 January 2015.
  • Normally, the ending date is automatically generated through the use of {{#time}} and additional coding inside the template. However, this is only applicable when the event has a generic duration. A certain number of days are added to the starting date in order to retrieve the ending date. Events that have a built-in generic duration are the following:

    • Solo = 10 days
    • Relay = 7 days
    • Clan (except the Weekend Dragon Race), Hatching, Arcade, Gem Spending = 4 days
    • Feeding, Food Gathering, Gold Collecting, Gold Spending, Weekend Dragon Race = 3 days

    In those cases in which the ending date is not a standard one, this parameter must be used.

    duration[edit]

  • Usage: Medium Low
  • Status: Active Usage
  • Default Value: See below
  • Examples: Awakening of the Machine (15/05/13), Happy Victoria Day (15/05/18), Extra Credit (15/10/05)
  • Description: Displays the total duration, from beginning to end, of the event.
  • The duration is, usually, generated when it matches a generic event title or a certain type of event. The following events have a built-in generic duration:

    • Solo = 10 Days (9 Days & 16 Hours before the 1st of August 2017)
    • Relay = 7 Days
    • Clan (except the Weekend Dragon Race), Arcade = 4 days
    • Hatching, Gem Spending = 3 Days & 16 Hours
      • When the ended parameter is used, the duration becomes 2 Days & 16 Hours
    • Weekend Dragon Race = 3 Days
    • Feeding, Food Gathering, Gold Collecting, Gold Spending = 2 Days & 16 Hours
      • When the ended parameter is used, the duration becomes 3 Days & 16 Hours

    In those cases for which the built-in duration does not match the real one, insert the duration using the following format: Digit(s) Days & Digit(s) Hours (as in the above examples).

    type[edit]

  • Usage: Medium
  • Status: Active Usage
  • Default Value: See below
  • Examples: All Events with non-generic titles
  • Description: Indicates the condition of the event.
  • Events with generic titles will have their type automatically generated. When a title is not generic, the type will have to be added in manually. All the types can be found here. Add the name of the type as it is written there.

    The following are considered generic titles:

    • Boss Challenge = Relay
    • Crowded Nursery = Hatching
    • Dinnertime! = Feeding
    • Farming Fanatic = Food Gathering
    • Golden Gatherer = Gold Collecting
    • Golden Opportunity = Gold Spending
    • Weekend Dragon Race, Clan Siege, The Great Dragon Race, Feel the Fury, Settle the Score, Winner Takes All = Clan

    vip[edit]

  • Usage: Medium Low
  • Status: Active Usage
  • Built-in Values: VIP
  • Examples: All in Good Jest (16/03/31), New Beginnings (17/01/01), Golden Gatherer (17/10/20)
  • Description: Indicates that an event is restricted to Trainers with an active VIP Status and categorizes the page as such.
  • While this parameter works by using any value, it will react only to the built-in value when generating the necessary images, thus the addition of |vip=VIP will suffice. As such, the usage of VIP as the standard value is compulsory, regarding if an image is needed to be generated or not.

    Since all Gem Spending Events are VIP Events, as of the 1st of September 2018 this parameter is automatically generated and no longer needs to be added.

    description[edit]

  • Usage: Low
  • Status: Semi-Active Usage
  • Default Value: See below
  • Examples: Golden Gatherer (15/04/10), Deep Sea Dragons (16/10/07)
  • Description: Displays the custom, in-game description.
  • It is used only when an event does not have a generic, built-in description. When a unique description exists, write it exactly as it is written in the game. The following events have a default generic description:

    Event Description
    Arcade Arcade Events are events in which participants gift various objects to their Dragons in order to move higher on the leaderboard and earn progress rewards.
    Calendar Log in every day to get these rewards!
    Castle Castle Events are events in which participants must open a multitude of different chests in order to advance through rooms and earn the final prize.
    Clan Siege Clan Siege is an event in which participating Clans complete various tasks to earn Spellbooks needed for sprites.

    The sprites are then summoned for use, allowing the Clan Dragon to attack the opposing Clan's base.

    Chain Breeding During the event, you can get the awesome |prize=NameDragon by using its parents in the Breeding Den!
    Feeding Feed your Dragons by using as much Food as you can.
    Food Gathering Collect as much Food as you can from any source.
    Gem Spending Spend as many Gems as you can to win awesome rewards!
    Gold Collecting Gather as much Gold as you can from any source. All sources count, except for selling.
    Gold Spending Spend as much Gold as you can for a chance to earn special rewards.
    Hatching Hatch as many dragons as you can. Rarer dragons give you a higher score!
    Relay Beat all the celestial Bosses to complete rounds!
    Solo Solo Events are events in which participants race against the clock and complete various tasks in order to win numerous prizes.
    The Great Dragon Race
    Weekend Dragon Race
    The Great Dragon Race is an event in which participating Clans complete various tasks to earn items needed

    for dishes they then prepare and feed to the Clan Dragon, allowing it to move forward on the race track.

    element[edit]

  • Usage: Extremely Low
  • Status: Obsolete
  • Examples: Dinnertime! (15/06/05), Dinnertime! (16/04/08), Dinnertime! (16/05/13)
  • Description: Used for Feeding Events to indicate which Dragons could be fed, provided they had the given Element.
  • Update 2.5 removed the restriction on specific Elements, allowing all Dragons to be fed, thus this parameter has fallen out of use.

    prize[edit]

  • Usage: Extremely High
  • Status: Active Usage
  • Examples: Play Day (17/05/26), Divine New Year (18/02/16), Crowded Nursery (18/08/10)
  • Description: Used to indicate the Dragon given as the main prize of the event.
  • Add the name of the Dragon while omitting the additional "Dragon" from the name. This parameter is to be used only if the Dragon is the main reward of the event. In the case of regular events, it is is the prize for placing in the highest spots of the leaderboard at the end of the event. For other events it is the prize given for completing the event.

    reward[edit]

  • Usage: Extremely Low
  • Status: Semi-Active Usage
  • Examples: Crowded Nursery (15/01/12), G'Day Day (16/01/25), Farming Fanatic (18/09/03)
  • Description: Used to indicate the main reward of the event.
  • Apart from Clan Events and the majority of Hatching Events, all other events almost always offer Dragons as their main prize. Since the prizes for Hatching Events are automatically generated, this parameter is only used when either a generic prize is not applicable or when a Dragon is not the main prize of the event (thus the prize parameter is not to be used). The parameter is also applicable to any other event that does not offer Dragons as a prize, such as the aforementioned Clan Events, to override the generic default.

    dragon[edit]

  • Usage: Low
  • Status: Active Usage
  • Examples: Vibrant Changes (16/10/20), Scent of Progress Event (17/11/27), Gloom Gems (18/04/12)
  • Description: Used to indicate the Dragon given as the final milestone reward in Gem Spending Events.
  • As with prize, add the name of the Dragon while omitting the additional "Dragon" from the name. This parameter is used only with Gem Spending Events.

    pieces[edit]

  • Usage: Extremely Low
  • Status: Active Usage
  • Examples: Back in Session (16/09/09), The Winds of November (16/11/14), Dream Days Event (17/09/01)
  • Description: Used to indicate the Dragon Pieces needed to collect in order to obtain the main Dragon of the Calendar Event.
  • The amount of Dragon Pieces will be displayed inside the EventBox next to the icon of the main Dragon prize and an additional line of text will be displayed under the Notes section of the event. However, if a Dragon is not the main prize or if there are no pieces to collect for it, the value that needs to be added is the collective amount of matching Dragon Pieces that are given for absolutely any Dragon in that event.

    mvp[edit]

  • Usage: Extremely Low
  • Status: Semi-Active Usage
  • Default Value: 3,000
  • Examples: Clan Siege (17/07/24), The Great Dragon Race (17/07/17)
  • Description: Indicates the prize the MVP of a Clan receives at the end of an event.
  • Used only when the prize is not the generic one that belongs to the highest Clan League. When this is the case, write the number in digits, making sure to separate thousands through the use of commas.

    section[edit]

  • Usage: Low
  • Status: Active Usage
  • Default Value: 10 (only Solo Events); 6 (only Castle Events)
  • Examples: All Calendar, Castle and Solo Events
  • Description: Used to indicate the total days (Calendar), levels (Castle) or tiers (Solo) an event has.
  • This parameter works in conjuncture with the type parameter, thus it is able to determine the name of the sections an event uses. Add the numbers of sections in digits. It does not need to be used for Solo Events if they have 10 tiers or for Castle Events if they have 6 levels. If the tier/level count is lower or higher than that number, then the parameter must be used.

    hero[edit]

  • Usage: Extremely Low
  • Status: Active Usage
  • Examples: Dawn to Duskwing (18/07/09), Knight Fight (18/11/12)
  • Description: Used to indicate the Dragon needed to participate in the Relay Event.
  • Add the name of the Dragon while omitting the additional "Dragon" from the name.

    ticket[edit]

  • Usage: Extremely Low
  • Status: Active Usage
  • Examples: Boss Challenge (18/07/30), Boss Challenge (18/08/13), Boss Challenge (18/10/22)
  • Description: Used when a Boss Challenge offers Divine Tickets as a reward.
  • Add only the last part of the ticket's name, namely the one that comes after the dash.

    badge[edit]

  • Usage: Extremely Low
  • Status: Active Usage
  • Examples: Spring Fiesta (18/05/04), Big Kick Cup (18/06/15)
  • Description: Displays the badge that can be obtained within an event.
  • Add the name of the badge while omitting the additional "Badge" from the name. The first letter of each word in the name of the badge must be capitalized.

    badge2[edit]

  • Usage: Extremely Low
  • Status: Active Usage
  • Examples: The Great Hatchling Hunt (18/03/23)
  • Description: Displays the second badge that can be obtained within an event.
  • Add the name of the badge while omitting the additional "Badge" from the name. The first letter of each word in the name of the badge must be capitalized.

    note[edit]

  • Usage: Extremely Low
  • Status: Active Usage
  • Examples: Golden Pyramid I (18/07/23), Golden Pyramid II (18/08/06)
  • Description: Indicates an objective observation that can be made about the badges offered within an event.
  • It is usually used when the requirement for obtaining the badges is not met in one event, but rather within the course of two or more different events.

    exclusive[edit]

  • Usage: Low
  • Status: Active Usage
  • Examples: Stars & Stripes Forever! (15/07/03), Wings Up (17/07/23), Heavenly Hatching (18/09/21)
  • Description: Indicates when an event is restricted to certain countries, operating systems or/and groups of users.
  • Using the parameter will add a line in the EventBox, indicating the event is exclusive and it will also categorize the page under Exclusive Events. If the event is exclusive by country or by operating system, simply enclose its Wikipedia article inside the {{wp}} template: {{wp|AddValueHere}}. Make sure the link to its Wikipedia article is correct and it is not a redirect. If the event is exclusive to two or more groups, separate the last two with an ampersand (&) and the first with commas.

    occasion[edit]

  • Usage: Medium Low
  • Status: Active Usage
  • Examples: Oktober Feast (15/09/18), Birth of an Empire (17/05/25), Screaming Eagles (18/07/05)
  • Description: Indicates when an event is celebrating a particular holiday or any other occasion.
  • Using the parameter will add a line in the EventBox, indicating the occasion of the event. If the occasion has a Wikipedia article, make sure to link to it by enclosing the occasion inside the {{wp}} template: {{wp|AddOccasionHere}}. Make sure the link to its Wikipedia article is correct and it is not a redirect.

    Try to shorten the name of the occasion if it is longer than 25 characters (including spaces), by adding a pipe after the occasion and then adding a shorter, but still intelligible name (check the third example above).

    text[edit]

  • Usage: Low
  • Status: Active Usage
  • Examples: Game Maniax Special Event! (15/04/17), Crowded Nursery (16/01/25), The Forgotten Castle (16/05/17)
  • Description: Displays various objective observations that can be made about the event.
  • Some observations that can be made include whether this type of event took place in the game for the very first or the very last time, or if the event was not available in a particular region because of a concurrent and exclusive event for that region, or any other factual and objective notes. Make sure to follow the writing style as specified in the Manual of Style.

    Examples[edit]

    Note to always use the Show preview function before saving an event. You can also experiment with this template by using the powerful template-expanding function. This function also allows modification of the template on the spot in order to produce varied results. The context title can be the name of the event you want to create since the EventBox makes use of the name of the page to generate its contents.

    First[edit]

    For complete generic events, add {{EventBox}} as the sole element of that article and then save the page, as in this article.

    Second[edit]

    For near-generic events, in which only the prize Dragon needs to be manually added in, add the |prize= parameter between the opening and the closing of the template and fill it in with the simple name of the Dragon, on a single line: {{EventBox|prize=Mentor}}, as in this article.

    Third[edit]

    When more than one parameter needs to be used, add the template and each parameter on a separate line:

    {{EventBox
    |type=Feeding
    |prize=Mentor
    }}

    Fourth[edit]

    Provided you have to use the reward parameter, the addition of the <center> and <br> tag will most likely be necessary, as in this article.

    {{EventBox|reward=<center>Prize 1<br>Prize 2<br>Prize 3</center>}}

    Fifth[edit]

    If a Feeding Event exclusive to New Zealand, with a non-generic name, unique leaderboard and the Go Green Dragon as the main prize, is occurring in the game and it celebrates Earth Day as its special occasion, then:

    {{EventBox
    |table=2
    |type=Feeding
    |prize=Go Green
    |exclusive={{wp|New Zealanda}}
    |occasion={{wp|Earth Day}}
    }}

    The generic milestone is automatically generated here, right after the EventBox, after which the leaderboard must be added in automatically, through the use of {{leaderboard}}.

    ==Leaderboard Prizes==
    {{leaderboard
    |Positions; ex: 1-10
    |Prizes (left empty if the main prize is a Dragon)
    |Positions
    |Prizes; ex: {{i|Gold}} 5,000,000 &nbsp;{{i|Food}} 200,000 &nbsp;&nbsp;{{i|Gems}} 2
    |Positions
    |Prizes
    |Positions
    |Prizes
    |Positions
    |Prizes
    |Positions
    |Prizes
    |Positions
    |Prizes
    |egg=Go Green
    }}

    Note the addition of &nbsp; which is a non-breaking space used here to separate the prizes in the table so that they are easier to follow. There is no default amount of said space that must be added, simply preview and add/remove until the alignment is right. The addition of |egg= is only used when the prize for the top positions is a Dragon. Otherwise, remove that line and insert the prize after the second | inside the template.

    Sixth[edit]

    A 5-day Gem Spending Event, that started on the 1st of October 2018, has a generic title, but a non-generic milestone or/and leaderboard, and has the Darkfire Dragon as the main prize and the Warden Dragon as the milestone prize.

    {{EventBox
    |table=1
    |ended=6 June 2018
    |duration=5 Days
    |type=Gem Spending
    |prize=Darkfire
    |dragon=Warden
    }}

    The milestone and leaderboard must be manually added here, right after the EventBox, through the use of {{milestones}} and {{leaderboard}}.

    ==Progress Rewards==
    {{milestones|Score; ex: 100,000|Icon of prize; ex: Gems|Amount|Score|Icon|Amount|Score|{{i|Dragon Egg|i|40}}|[[Warden Dragon|<font color="black">Warden Dragon</font>]]}}

    Note that this template and its parameters must all be on the same line, otherwise its formatting is broken. Also note for the last milestone, that the amount will be replaced by the name of the Dragon. If a Dragon is not the last milestone reward, add the amount instead. While for the first two milestones it is sufficient to only add in their name, the {{i}} template must be used for the last milestone. See its usage here.

    ==Leaderboard Prizes==
    {{leaderboard
    |Positions
    |
    |Positions
    |Prizes
    |Positions
    |Prizes
    |Positions
    |Prizes
    |Positions
    |Prizes
    |Positions
    |Prizes
    |Positions
    |Prizes
    |egg=Darkfire
    }}