Hearthstone Wiki:Project 13

From Hearthstone Wiki
Jump to navigation Jump to search
Project #13: Reworking Cards table Part 2
Not yet completed
Author: Use25
Working: Use25

Reworking/Revamping Cards table on pages using Card template

Last week, Fandom pushed a new update to wikipedia:MediaWiki to version 1.37 from 1.33. Due to this, Cargo extension was unable to store _pageData._categories, a key (or attribute, property) that we use frequently for querying cards by races, arts, or formats. I have no choice but decide to rework this table once more time, despite the fact that Project 1 is still incomplete, so that we will avoid using _pageData._categories in the future. Also, I want to take this opportunity to make our database importing independant from HearthstoneJSON, because there are still a lot of useful data they haven't managed to extract yet, and I want to take full control of token numbers in card texts, so that I can understand more how the texts are built and easily manipulate them.

Announcement blog: Hearthstone Wiki:News 7.

New structure

  • CardsOfficial table will be replaced with 2 tables, Card and CardTag.
    • All of these tables will be extracted directly from client by me. These tables will be independant from any public API.
    • I recommend not to touch any data in these tables, as they are fully automatic and I want to keep the official data as organic as possible. They are essential to researching how Team 5 designs cards.
  • Cards table will be separated into 2 tables: DerivedCard and CustomCard.
    • DerivedCard is a table with keys that have default value based on the official data we get. You can edit these key values, but it's suggested that you keep them as their default value (don't set new value).
    • CustomCard is table with completely made-up keys and is non-existent or unrelated to official data, but they are proved to be useful. You can edit these keys freely without being afraid of disrupting official data.

Hearthstone Wiki:Project 13/tables includes the full details of parameter changes and new parameters of the Card template.

All queries (card lists) will also be reworked, but that's for another project.

What to do