"Emperor" DLC banner.

For the full Terms and Conditions of the Paradox Wikis contest please visit here



The wiki will run a contest to celebrate the release of "Emperor" starting on 2020-06-09 at 20:00 CET till 2020-06-18 at 20:00 CET.

Prizes

Contest avatar

Users can enter the contest by contributing to the wiki during that time span -- with various actions providing different number of tickets.

The three users with the most tickets will each get to pick their product(s) of choice from the Paradox Web Store up to the amount they won:

1st place can pick at an amount up to $60 - Won by Grotaclas‎ (344 tickets) 2nd place can pick at an amount up to $40 - Won by UserID‎ (296 tickets) 3rd place can pick at an amount up to $20 - Won by Capitaine Spock (283 tickets)

In addition, the winners will also receive a special forum avatar and icon ( ). These are unique to major wiki contributors.

Notes: Can be used for any combination of digital goods (regular retail prices) in a single occurrence, does not apply to physical goods, winner's product keys will be delivered by Paradox Wikis moderator SolSys.

Rules and guidelines

Paradox Wikis administrator SolSys decides whether a raffle ticket has been earned based on the guidelines below.

Members of the Paradox Wikis team (administrators, moderators, halfops) cannot enter the contest.

The competition is open for anyone around the world aged 16 or above. Entrants under the age of 18 require parental consent to participate.

All entrants must register an account on the wiki; anonymous edits are not counted unless they can be clearly connected to a registered user (E.G., in cases where the user was accidentally logged out).

Any action on the list undertaken between the start and the end of the contest will earn tickets.

the start and the end of the contest will earn tickets. The entrant must have access to the email address they've defined for their account, as prizes will be sent via email. Note that by default the Paradox Account email address is used.

email address is used. If you have changed the email address of your Paradox Account since registering on the Paradox Wikis (before the unified account), you should update your email address via the Paradox account settings from the forums. Otherwise, it may take longer than normal for you to receive your prize(s) if you were to win.

Any vandalism will cause all raffle tickets earned by the entrant to be forfeit.

Entrants should read the style guidelines in order to ensure their edits are up to the wiki's standards. Edit summaries are encouraged, but not required except where otherwise specified.

For the full Terms and Conditions of the Paradox Wikis contest please visit here.

Earning tickets

All tickets are provisional until the contest starts and edits made in advance can change the values below



A large variety of tasks will earn you tickets; everything from updating pages, to writing strategies, to modding information, to creating pages on new features. All tasks are listed below.

Anything that involves the creation of a new page or section assumes that the resulting page is rated B or above, and has no resulting ambox requests ( {{rewrite}} , {{cleanup}} , {{copy edit}} , {{expand}} and {{stub}} ).

Any task that gives "at minimum" a number of tickets can give more than that number if the quality and/or thoroughness of the writing is higher than expected.

The first three tasks give more tickets the more outdated the page/section/infobox is. The base ticket amount is multiplied according to the following table:

Version Multiplier 1.29 1 1.28 2 1.27 3 1.26 4 1.25 5 1.24 6 1.23 7 1.22 8 1.18 10

Important: When updating an article/section/infobox do not remove versioning tags. Instead, set the version number to the updated version. This will make it stop displaying until a newer version is released. The SVersion tags should be present after each tier 2 header.

Ensure that pages are up to date. See outdated pages for a list of potentially outdated articles. If no changes are necessary for the page to be considered up to date, a justification must be written in the edit summary or on its Talk page. This gives a base amount of 1 ticket per page updated

Ensure that page sections are up to date. See outdated sections for a list of pages with potentially outdated sections. If no changes are necessary for the section to be considered up to date, a justification must be written in the edit summary or on the page's Talk page. This gives a base amount of 0.25 ticket per section updated.

Ensure that infoboxes are up to date. See outdated infoboxes for a list of pages with potentially outdated infoboxes. If no changes are necessary for the infobox to be considered up to date, a justification must be written in the edit summary or on the page's Talk page. This gives a base amount of 1 ticket per 10 infoboxes updated.

Improving an article by such an extent that it is reassessed at a higher level. See Category:Articles by quality for information on how assessment works. This gives at minimum 2 tickets

Write a page about an important modding concept. This gives at minimum 4 tickets

Other improvements to the wiki give tickets based on the judgement of the person assigning tickets. Content additions, structure improvements, and grammar improvements are prime examples of contributions that'd fall under this

Mechanics pages

Mechanics pages are worth more than other pages to update, the changes and rewards are shown below.

High value tasks

These tasks are of high importance to the wiki and as such are worth more than their components would be.

Unit packs

Build a page listing unit packs. Images are uploaded and stored in Category:Unit_packs.

Emperor/1.30

A number of features are introduced or changed in Patch 1.30. Having info on this is highly important to the wiki, and is thus highly rewarded compared to the effort involved:

Content added Reward Revolution revamp 10 Hussite faith 10 Hegemonies 5 New Missions 10 per set added Defender of Faith 5 The Council of Trent and Counter-Reformation 5 Provoke Rebellions 5

Mechanics page and navbox

Add any missing mechanics from the list above to the mechanics page complete with appropriate icon and description. 5 tickets per mechanic added

Develop a complete mechanics navbox and deploy it to all mechanics pages. Complete with links from any existing mechanics navbox. See the Stellaris Game Concepts navbox or the HOI4 Mechanics navbox for examples.

New navbox: 10

Apply Mechanics navbox to all Mechanics page 1 per 5 pages

Identify any missing mechanics pages from the newly moved navbox and add them 1 per mechanic correctly added.

There are a number of very outdated pages on the wiki. The prizes for updating them are listed below. Note that mechanics pages which are outdated are instead listed above.

Old images

These images are all outdated, replacing with an up to date version is worth 8 tickets each.

Image age identification

Some images do not have a version category. Add an appropriate version for any pages in the following categories. 1 ticket per image given a version category.

Page expansion

There are several pages on the wiki which have been tagged as needing an expansion. The tickets below do not include bonuses for updating a page so an entrant will be awarded more tickets if they update the page too.

Page Changes requested Reward Army professionalism events Add missing events 10 Culture modding Country and province modifiers of cultures or culture groups 10 Event modding Default ai chance, when not all options have it specified. 5 Faction modding Custom faction names 5 Japanese missions Add in missing missions 10 Korean missions Add in missing missions 10 List_of_decision_lists#Religion Add in missing decisions 5

Content verification

Verifying that content on the wiki is correct is also important. Each page checked and verified is worth 5 tickets. The unverified content is tagged with the {{Sup}} template.

Adding categories

Add categories to images in Special:UncategorizedFiles

Verify computer generated content

Pages in Category:Computer_generated were generated using the PDXParse suite. Verify the content and fix any transcoding errors. 1 Ticket per event verified and updated to 1.30.

Unrecognized icon strings

Pages in Category:Pages with unrecognized icon strings contain unrecognized icon strings either through typing errors or missing files. 3 Tickets per page corrected.

Flag images

Some of the flags are low resolution and high resolution (800x533 to 1000x667) ones are desired. This is not the same as stretching the image (see the history of File:Apache.png for an example of what not to do). Each flag uploaded with correct copyright is worth 1 ticket.

Reporting completion

For most of the above, no report of the action is necessary. A descriptive edit summary is enough. Please only contact the overseeing moderator about tickets if you've got any complaints about the # of tickets given, if 72 or more hours after your actions you've yet to receive any tickets, or for the circumstances described below. Questions about anything else are welcome at any time and will be answered as soon as possible.

All earned tickets are be listed below on a per-user basis. There is no need to notify overseeing moderator that one is entering the contest (except for the specific contributions mentioned above); it is assumed everyone wants a chance at winning a prize.

If you believe you have made a significant contribution ("Other significant improvements to the wiki"), or that your ticket-earning contributions have been missed, this can be reported at User talk:SolSys.

Earned tickets

Fractional tickets are only used for accounting progress towards an entrant's next ticket.

Notes