Skip to content

Latest commit

 

History

History
26 lines (17 loc) · 2.92 KB

README.md

File metadata and controls

26 lines (17 loc) · 2.92 KB

Decks of KeyForge and SAS Tickets

DoK Change request guidelines

Submit bugs or request changes to the Decks of KeyForge website. See below to suggest changes to the SAS system or card ratings

  • Search bugs or features to make sure it hasn't already been reported before creating a ticket.

Propose a new DoK Feature

Submit a bug with DoK

SAS Change request guidelines

  1. Do No Harm It is more important to prevent falsely overrated decks and cards than to accurately capture all value. Your idea should improve scores for almost all decks it touches, and very rarely cause a card to be overrated in value in decks.
  2. Legacy Cards are lower priority If a card has not been included in the last two sets, it is considered a "legacy" card in terms of changes to SAS. Changes to legacy cards will only be considered if it is obviously inconsistent with other cards with similar scores, or there is an egregious problem.
  3. Avoid suggesting minor tweaks to scores Make sure your change request is relevant. If you think a card is only off by 0.25 AERC most of the time, it probably isn't worth updating.
  4. Read the About Page This page details the basic details of how decks and cards are scored in SAS.
  5. Read the AERC Rating guidelines Find the relevant sections in the AERC rating guidelines This google doc contains detailed information about how cards are rated, and what expectations and rules are used to maintain consistency.
  6. Compare with existing cards using the card search tool to ensure your change request is consistent with existing cards.
  7. Don't make duplicates Search the card change issues or sas feature change issues to make sure your request isn't a duplicate or hasn't already been rejected

Propose an update to a card

Propose a new SAS Feature