Hearthstone Wiki

The Admin noticeboard is one way through which users can notify Administrators of issues needing administrative attention. While users are welcome to directly contact specific administrators (especially if they are seen to be active), posting here can be an easier and quicker way of ensuring that at least one admin will notice an issue and respond to it promptly. Remember to sign (using four tildes: ~~~~) when posting an issue.

Before posting an issue here, please consider the following:

  • This page is for reporting wiki issues. Please post discussions on the talk page.
  • Post only issues that require administrative action, i.e. blocking vandals, protecting pages, restoring deleted pages etc.
  • Do not post deletion requests here. Deletion requests should be made by adding {{delete|reason for deletion request}} to the top of the target page, which will then automatically mark the page as a candidate for deletion.
  • Do not post issues regarding content disputes. Try making a request for comment instead.
  • Mediation requests between users should only be made once a resolution could not be reached between users.
  • For issues regarding the use of this wiki, please see our help center.

In case of vandalism, posting about it here is low priority. Revert it first, anyone can do so. If the vandal created a new page, tag it for deletion. Assume good faith and consider leaving a message on that user's talk page to explain the reason. Post here only if the user has made several disruptive edits and/or persists despite a warning. Always avoid a revert war with the vandal; it is far better to wait until an admin has a chance to intervene. If a user must be reported here, please use {{user}}, preferably as the topic subject/headline.


Current issues[]


According to the Help:Style guide, keywords and tribes should not be capitalized. However, in many articles it seems that they are, by default, capitalized. Should the style guide be updated or should we start fixing the incorrect capitalizations? I recommend the latter, based on the current style guide as well as the rules of English language. Blue Banana whotookthisname (talk) 14:29, 24 February 2018 (UTC)

Main page needs to be updated[]

The main page needs to be updated to show the three upcoming mechanics. Additionally, the gameplay section does not mention dungeon run. Quater (discuss) 12:20, 17 March 2018 (UTC)

Done. oOeyes User-OOeyes-Sig 21:29, 17 March 2018 (UTC)
@OOeyes Just an idea, but I can't help but think that saying "before April 30" is more ambiguous than saying "sometime in April". At the moment, it implies it could be released in March, which we can assume to not be the case given their previous release cycle. Quater (discuss) 11:00, 19 March 2018 (UTC)
Updated. oOeyes User-OOeyes-Sig 15:05, 19 March 2018 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── Given KnC was released months ago, it's probably best to change the featured video to this. Quater (discuss) 10:02, 21 March 2018 (UTC)

Updated. oOeyes User-OOeyes-Sig 16:23, 31 March 2018 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── Official release date for TWW has been announced. It's April 12. Quater (discuss) 11:12, 6 April 2018 (UTC) ──────────────────────────────────────────────────────────────────────────────────────────────────── Monster Hunt should be added to the Gameplay section. Quater (discuss) 07:47, 9 April 2018 (UTC)

Done. oOeyes User-OOeyes-Sig 21:31, 9 April 2018 (UTC)


See here. Surafbrov 07:33, 31 March 2018 (UTC)

I don't consider this to be an administrative decision. If you're concerned about community reaction, feel free to see if there are any objections by posting on Project talk:Community portal and waiting a few days. But since leaving the redirect behinds doesn't break links, you could just go ahead and do it too. oOeyes User-OOeyes-Sig 16:22, 31 March 2018 (UTC)

Apostrophe Bug[]

Any card with an apostrophe in its name (The WitchwoodWoodcutter's Axe, LegacyAl'Akir the Windlord, The Grand TournamentMukla's Champion ect) is currently bugged when viewed in a chart. It displays a broken 200x link instead of the card. When hovered over, the page its trying to link to is written as "Everything before the apostrophe"& (Woodcutter&, Al&, Mukla&). I have no idea what caused this. TheMurlocAggroB (talk) 16:10, 22 June 2018 (UTC)

This is totally unrelated, but, fun fact: commas (not apostrophes) did not start appearing in the names of Hearthstone cards until Whispers of the Old Gods. Aegonostic (talk) 18:45, 22 June 2018 (UTC)
Fix is in. I had to do it in {{Card infobox}}, though, so it won't be reflected in all cases immediately. I'll run a bot over card pages to try to speed it up. oOeyes User-OOeyes-Sig 01:49, 23 June 2018 (UTC)

Secrets page has a problem[]

It shows the following error: A database query error has occurred. Did you forget to run your application's database schema updater after upgrading? 16:20, 2 August 2018 (UTC)

Descriptions are always showed collapsed (solved)[]

Names were fixed by using the purge cache option on the top right of the page. Table content is always collapsed. For reviewing cards and correcting errors it's necessary to be able to see and copy paste the table uncollapsed. For example https://hearthstone.gamepedia.com/The_Witchwood_card_list Grommpy (talk) 17:25, 4 August 2018 (UTC) I've tried updating my hydra.js but it doesn't work. Grommpy (talk) 17:57, 5 August 2018 (UTC)

|collapsed=no just worked fine for me, at least on custom card table. Are you using it like this?
{{Custom card table|set=The Witchwood|collectible=true|collapsed=no}}
If so, it shouldn't collapse. Also, the variables in your hydra.js won't affect the card table collapse script; they have nothing to do with it. oOeyes User-OOeyes-Sig 04:33, 6 August 2018 (UTC)
I tried |collapsed=no in 2 browsers both with and without loading java script, try and copy pasting the Black Cat entry: You'll get the Spell Damage +1, but not the next line: Battlecry: If your deck has only odd-Cost cards, draw a card. Grommpy (talk) 21:33, 6 August 2018 (UTC)
The complete data is in the .html source code, so I downloaded the page, edited it, cut out all the java and css going on, and only left the < table > parts. Problem solved. Grommpy (talk) 21:58, 6 August 2018 (UTC)

Flood of anon vandalism[]

There's a flood of vandalism on the Hearthstone wiki pages today, coming from three IP addresses:

Honestly, it looks like kids in a school library making fun of each other. All of these IP addresses look like vandalism-only. Asolovay (talk) 21:12, 29 August 2018 (UTC)

Requesting assistance on recent vandalism blanking. Aegonostic (talk) 21:25, 29 August 2018 (UTC)
I've fixed most of them, and there were two pages which needed fixing, I did the fixes.
These users came from the Hearthstone Discord server. TheGamer765 (talk) 23:46, 29 August 2018 (UTC)
Hey, I'm a bit late to the party, but I've preventively blocked the IPs for a week. Hopefully they won't come back. Frisk (talk) 00:02, 30 August 2018 (UTC)
Thanks much, all! Asolovay (talk) 00:07, 30 August 2018 (UTC)

The error showing in the main page of this wiki (mobile version)[]

Since I cannot edit the Main Page, I want to say that the newest expansion it should show in the mobile version is Rastakhan Rumble, not The Witchwood. Thanks. Minhngoc25a (talk) 14:49, 29 December 2018 (UTC).

Fixed. oOeyes User-OOeyes-Sig 15:21, 30 December 2018 (UTC)

Problem with data caching and purging[]

Bringing this issue onto the admin noticeboard, see Talk:Twinspell. In short, in some cases purging pages will work to update the page's data, but in a growing number of cases, pages are getting stuck on the same data even with the help of pressing the purge button. Will there be a fix for data caching and the problem of "data getting stuck" in the future? Aegonostic (talk) 03:47, 15 May 2019 (UTC)

Yes, this is especially true with Nightborne art, which is not updating at all and has not ever updated since its creation. Cactusisawesome (talk) 07
03, 15 May 2019 (UTC)
Purging the pages with the lists only works when the caching issue is on that page. Sometimes, it is on the source page, and in these cases, you usually have to open the page for editing and save it without changes. I did this with Rise of ShadowsRay of Frost and it is now appearing on both Twinspell and Nightborne art after a purge of those. This is a longstanding issue, and I've heard nothing of a fix coming for it. I'm running my bot over all the card pages now in case any others have this issue. oOeyes User-OOeyes-Sig 14:58, 16 May 2019 (UTC)
Ok, thanks! So I guess I had to purge both the card datapage and the card page. I'll try doing this next time. Also, does anyone know why Quest_(ability)#Quests isn't showing any cards anymore? Aegonostic (talk) 16:04, 16 May 2019 (UTC)
I managed to sort it out. The parentheses needed some special handling. oOeyes User-OOeyes-Sig 18:45, 19 May 2019 (UTC)

Make {{List cards}} visually sort cards by mana (and by card name)?[]

I notice that it would be immensely helpful if the template {{List cards}} could, by default, sort cards by mana (and by card name) when the cards are visually displayed on the screen.

For example, in the following template, Rise of ShadowsBronze Herald is shown, then Knights of the Frozen ThroneCobalt Scalebane, etc. Is there any way to make it so that by default, the lowest cost cards come first, and make it proceed in increasing mana? (I know that the card table has the "wikitable sort" functionality, but can the visual table be made to do this by default?)

{{List cards|format=standard|type=Minion|subtype=Dragon{{!}}{{!}}All|collectible=True}}

So in short, I'm asking if it's possible to do a cargo query of two sortings (one on mana, and then a second on card name) and display it visually. Aegonostic (talk) 05:45, 17 May 2019 (UTC)

I've switched {{Cards}} over to descending sort by mana and secondary sort by name. Did we want to change the tables' starting sort too? oOeyes User-OOeyes-Sig 18:45, 19 May 2019 (UTC)
Is it ok if you do ascending sort for mana (and the current ascending sort for name is good as is).
I think the tables' starting sort can be double as well: (1) Sort by Rarity like it is now and (2) Sort by mana ascending. Just to mix it up a bit with the table vs the visual list. Aegonostic (talk) 22:15, 19 May 2019 (UTC)
Updated. oOeyes User-OOeyes-Sig 22:24, 20 May 2019 (UTC)

More content on the sidebar?[]

Recently Blizzard added their own gallery for cards, and I figured that they could be featured on our sidebar, is there a reason we are not adding it or is it that it hasn't come to anyone's attention? Cactusisawesome (talk) 15:01, 17 June 2019 (UTC)

Just didn't occur to me to add it. But it's there now. oOeyes User-OOeyes-Sig 09:39, 18 June 2019 (UTC)

Request for reference highlighting feature[]

Whenever you click on a reference hatnote, you are redirected down to the References section to the appropriate reference. However, the target reference hatnote is currently not properly highlighted. I would like to request the addition of better highlighting to help readers navigate through multiple references on a page. So, what I'm asking is the ability to darken the highlight and maybe even underline the particular reference hatnote number (e.g. 6.0, 6.1, 6.2) that was clicked. The existing highlighting is barely visible, if it at all exists. So something like:

1.0 1.1 1.2 1.3 1.4 1.5 Hearthstone (2019-07-31). Saviors Of Uldum Final Card Reveal Livestream (30:50 - 34:00). YouTube. Retrieved on 2019-08-01.

Instead of the current:

1.0 1.1 1.2 1.3 1.4 1.5 Hearthstone (2019-07-31). Saviors Of Uldum Final Card Reveal Livestream (30:50 - 34:00). YouTube. Retrieved on 2019-08-01.

Aegonostic (talk) 20:17, 5 September 2019 (UTC)

No. Those superscripted links are not targeted by the inline citation links. Only the entire line is, so there is no way for me to set styles specifically for the correct link without a change in the extension, which is beyond my purview.
Well, technically, I suppose a script could be written to do it. But as it would be yet another per-wiki thing to maintain that could potentially break with extension updates, I'd greatly prefer this feature be added directly to the extension if at all. We don't seem to have the Cite extension listed as a subgroup in our GitLab, so I'm not sure if the platform would handle a ticket on it. If you did want to request it, it'd probably be best to ask the authors directly, maybe here. oOeyes User-OOeyes-Sig 13:35, 6 September 2019 (UTC)
Actually, they might be resistant. It occurs to me that it's probably not possible to target both the line and the specific link without adding Javascript in to a feature where they've neatly avoided it. oOeyes User-OOeyes-Sig 13:45, 6 September 2019 (UTC)
Hmm.. this does seem like something the Mediawiki extension should invest in (if at all possible), because it improves reader usability. Well, thanks for your insight, it's unfortunate that this wasn't possible. Aegonostic (talk) 17:49, 6 September 2019 (UTC)

Caching problem again?[]

There was a question raised about cards missing from a list: Talk:Hero_card. This seems to be a caching problem again. I tried the null edits and the purging on one of the card's datapage and the article page, and also the list page. No bueno. Aegonostic (talk) 18:13, 11 September 2019 (UTC)

Cargo doesn't seem to be picking up the pages' categories in its _pageData, and I'm not having any luck figuring out why at the moment. I might have to ask for a rebuild to be run on that table, which might affect results across the wiki while it's running. oOeyes User-OOeyes-Sig 19:35, 11 September 2019 (UTC)

Also, this page is missing all cards from its list(s), if it helps: Start of Game (e.g. The WitchwoodBaku the Mooneater, The WitchwoodGenn Greymane, etc.) Aegonostic (talk) 03:12, 12 September 2019 (UTC)

Yeah, it seems there are 241 pages which do not have their categories listed in the _pageData table. I've logged a ticket with the platform team, as I'm more or less at a loss for a resolution. oOeyes User-OOeyes-Sig 18:45, 13 September 2019 (UTC)
It looks like this particular problem is resolved. I see another issue that might affect some cards with redirects, but I should be able to fix that one myself. oOeyes User-OOeyes-Sig 23:00, 13 September 2019 (UTC)
I think these problems are resolved now, at least for the time being. >.> oOeyes User-OOeyes-Sig 23:22, 13 September 2019 (UTC)

Some weirdness is going on with {{Card}} and {{Card infobox}} in that even though the card datapages exist, the images don't go through to display through the aforementioned templates on the article page. See here: Talk:Buried_Finley. I tried purging and null-edits, but no effect. Aegonostic (talk) 18:12, 17 September 2019 (UTC)

Some funny stuff is going on with Data:Cards/First_Wish(92182), it shows First Wish listed three times as a card content page on its datapage. I tried null edits + purging. Also, if you hover over the wikilink of First Wish, you don't get its card image. Aegonostic (talk) 06:44, 30 September 2019 (UTC)

Looks like the ye olde delete/restore trick has resolved the issue. oOeyes User-OOeyes-Sig 11:33, 1 October 2019 (UTC)

Lua error[]

Could you fix a lua error here? 00:57, 22 September 2019 (UTC). Page Triggered effect contains many lua errors. 00:59, 22 September 2019 (UTC).

It should be corrected now. oOeyes User-OOeyes-Sig 07:16, 23 September 2019 (UTC)

Trying to create {{Notelist}}[]

I'm trying to make {{notelist}} and {{efn}}, but the ability to use reference groups and alternate list-styles seems disabled in the Cite extension, as well as it feels like something funky is going on, not sure. Can you help enable areas so that making a notelist is possible? (example of problem is seen visually in my sandbox: User:Aegonostic/Sandbox7) Thanks. Aegonostic (talk) 07:49, 29 September 2019 (UTC)

Cite has no documented configuration settings. I'm pretty sure, at a glance, this has to do with custom styling added on top of Cite, especially given these are templates and not parser functions or tags. Which means I should be able to copy styles over easily enough, but I need to know where to look for them. Are you using a particular wiki as a source? oOeyes User-OOeyes-Sig 11:26, 1 October 2019 (UTC)
Hm, so I'm using the main English Wikipedia for the code for {{notelist}} and {{efn}}. Notelist here and Efn here. The implementation of the code works on that wiki, but it doesn't work on this wiki. So if this wiki is using custom styling added onto the Cite extension, I'm not sure but I'm thinking you're referring to configuration settings like the one given in this link here, where it says:
"[Grouped references] may be disabled by $wgAllowCiteGroups = false;"
You can try enabling that and setting that to "true" to enable "grouped references" I think. Aegonostic (talk) 19:06, 1 October 2019 (UTC)
The grouping doesn't appear to be disabled. See User:OOeyes/Cite test. I have no access to the setting, anyway, and can't imagine why we'd change the default true for that anyway. I think you're mistaking the grouping feature for the list style type? It looks to me like this doesn't lie in the Cite extension but in wikipedia:Template:Reflist. Note in the template's source where it's adding list-style-tyoe to the style attribute of a div surrounding the references. That's where the magic is happening. The sole link between the list styles and grouping is the use of the group template parameter for both things. oOeyes User-OOeyes-Sig 23:05, 1 October 2019 (UTC)
Yea I got a bit confused and thought the CSS "list-style-type" was within the Cite extension, thanks for clearing that up. But I still don't know why this wiki isn't able to utilize the "liststyle" template parameter for in a normal reflist template such as {{Reflist tester}}. This is pretty unimportant, but it's really weird. :(
The problem is here if you want to take a look: User:Aegonostic/Sandbox8, but you don't have to Aegonostic (talk) 06:38, 3 October 2019 (UTC)
It looks like help from an admin was unavoidable. With another trip down the rabbit hole, I found this small bit of CSS needed to be added to prevent Cite from overriding the indicated style:
div.reflist ol.references {
  list-style-type: inherit;  /* Enable custom list style types */
It's now in MediaWiki:Common.css. That only fixed the lists, though. I eventually found I had to add pages like MediaWiki:Cite link label group-lower-alpha for the inline links to properly work for each group. So there is indeed a Cite extension feature that needs to be used, but we gotta bring our own labels. -_- oOeyes User-OOeyes-Sig 09:18, 3 October 2019 (UTC)
Ah, cool, gracias. :) I just did a quick google search on that mediawiki page, putting it here for reference for future reading: Help:Cite_link_labels. Thanks for the fix. Aegonostic (talk) 16:16, 4 October 2019 (UTC)

Update home page[]

Hey admins, could you update the Outdated home page for mobile ? Minhngoc25a (talk) 03:45, 12 November 2019 (UTC)

Oops. *facepalms* Alright, updated. oOeyes User-OOeyes-Sig 18:15, 12 November 2019 (UTC)

Card infobox for Battlegrounds[]

moved to Hearthstone Wiki talk:Community portal#Card infobox for Battlegrounds

Caching problem[]

For some reasons, the recent data I've created haven't recognized pages using them. Is there any way to fix this? Use25 (talk) 08:41, 6 December 2019 (UTC)

Sorry. That was due to my Cards table changes. The table was in read-only mode while a replacement table was generated with the new fields. I've swapped in the replacement and things should begin functioning normally again. oOeyes User-OOeyes-Sig 17:24, 6 December 2019 (UTC)

Problem with attempting to setup for Battlegrounds queries from card table[]

So, right now there are 253 pages in Category:Battlegrounds cards, which is a category derived from specifying |category=Battlegrounds in card infoboxes. (Category:Battlegrounds_card_data is also a derived category)

I'm putting in |hiddentag=Battlegrounds tavern minion in the infobox of Battlegrounds minion pages to categorize the page as a purchasable minion in Battlegrounds, but when I try to query for these cards using {{List cards|hiddentag=Battlegrounds tavern minion}}, it doesn't work. I believe it is querying from the card table Special:CargoTables/Cards, so the query doesn't work and results in zero results, since |category=Battlegrounds is specified in the infobox, thus not registering these pages into the card table. However, due to caching issues, I am unable to verify if this is true.

Should we:

  • Delete "|category=Battlegrounds" for all these 253 pages in Category:Battlegrounds cards and just use the regular card table Special:CargoTables/Cards?
    • Then the query {{List cards|hiddentag=Battlegrounds tavern minion}} should work, but right now I think I'm getting caching issues and I can't verify if this query will work, but it works for Wild cards such as {{List cards|hiddentag=Giants}}.
  • Or should we make a new cards table specifically for Battlegrounds? And then alter {{List cards}} to query the appropriate card table?

I feel like the first option is best, but as of right now, I don't know whether I'm querying correctly because there seems to be a caching issue. Aegonostic (talk) 22:54, 18 March 2020 (UTC)

I'm getting results when I add |category=All|bg_type=All as well to remove some automatic conditions, though List cards needed a fix because it was ignoring bg_type. I probably need to figure out logic to remove the automatic check for Category:Card data when certain bg_types are supplied or something else so the category=All isn't needed, but with the List cards fix, this seems to be getting the desired results.
Categories have no effect on whether a card goes into the Cards table. They are supposed to be added in the _pageData table, and the queries join them when checking, but that seems to be what's affected by the caching issues. oOeyes User-OOeyes-Sig 02:38, 19 March 2020 (UTC)
Sweeet, thank you, adding |category=All|bg_type=All works, though it does seem weird these two parameters are needed. I'll try to work with this now. Aegonostic (talk) 03:34, 19 March 2020 (UTC)

Broken homepage[]

The homepage has two featured videos played at the same time. One video can be paused, but the other one was found nowhere. Minhngoc25a (talk) 18:21, 8 June 2020 (UTC).

It should be fixed now. A weird issue cropped up recently with Twitch VODs where if you explicitly disabled autoplay with autoplay=false, it did the exact opposite. We should have all of those removed now. oOeyes User-OOeyes-Sig 23:41, 9 June 2020 (UTC)
@OOeyes: Unfortunately, this still happens to me and I had to use uBlock Origin to block all Twitch players in this site. Minhngoc25a (talk) 17:53, 10 June 2020 (UTC).
Yeah, okay, Twitch embeds are doing funky things this week. I guess there was probably an API change on their end. But might as well switch to a more current Youtube video anyway, which neatly avoids the problem. oOeyes User-OOeyes-Sig 15:35, 11 June 2020 (UTC)

Portuguese card pages bleeding into English card tables and category pages[]

I'm noticing the creation of a lot of Portuguese card pages. These are starting to bleed into the English category pages and card tables. I'm wondering if there is a more established or more formal way to set apart other localizations for this wiki so that they don't collide with the English localization. I know Fandom does this, but I don't know if this wiki has a natural way of doing so. Aegonostic (talk) 02:55, 8 August 2020 (UTC)

Uh, it has been 3 days and I'm starting to worry. I wonder where the old admins or Gamepedia staffs are... Use25 (talk) 13:05, 10 August 2020 (UTC)
I've talked to the person who made the edits, and they should be marking their pages for deletion... They were just trying to help translate the wiki for people who don't talk English, unaware that it wasn't the best way to do. I don't know where the admins are too, but seeing the List Files flooded with Brazilian cards bothered me a bit x) --Mattheus 45 (talk) 20:13, 10 August 2020 (UTC)
I'm very sorry for missing this. I was unknowingly having issues with notifications after the user merge ended up renaming my account. I finally looked into it after realizing the notification volume was unusually low, and I think I have things sorted now. -_-
Anyway, it looks like the translated pages are using {{Card infobox pt}} instead, so I've just removed the auto-categorization and card table storage from the template. As long as they are all using that, they should disappear from the lists. oOeyes User-OOeyes-Sig 22:27, 16 August 2020 (UTC)
Also, I'll just leave a note for future reference: translations should not use {{Card infobox}} or copies of it directly, but there should be no problem in using {{Card infobox/layout}} (or copying that). I separated that part out specifically for cases where the cards shouldn't go into the proper card categories or lists. oOeyes User-OOeyes-Sig 22:36, 16 August 2020 (UTC)

Main page update for Scholomance Academy[]

If the main page can be updated for Scholomance Academy, that would be great. Aegonostic (talk) 01:04, 17 August 2020 (UTC)

Queries for Battlegrounds doesn't work[]

Something is wrong when I use {{Cards}} or other card-listing templates for Battlegrounds cards. They simply don't appear. For example: {{Cards|set=Battlegrounds}}

The only way to list the Battlegrounds is to use category=Battlegrounds, but it only lists Hero Powers and Heroes. Hopefully someone can take a look at this. Use25 (talk) 15:10, 10 September 2020 (UTC)

I also would like to know why this is happening. It's a pretty big issue but if solved can automate some BG lists. Aegonostic (talk) 15:22, 10 September 2020 (UTC)

Not able to add external links into pages because of captcha malfunction[]

Whenever a new external url is attempted to be written into a page, the edit will not go through because of a malfunctioning captcha. Hopefully this will be resolved soon. Aegonostic (talk) 16:47, 24 September 2020 (UTC)

This has been resolved. Aegonostic (talk) 04:53, 28 September 2020 (UTC)

It appears that all images on the wiki have been changed visually to low res[]

All pictures in card infoboxes, called from {{Card}}, and from code such as [[File:Some image]] appear visually as low resolution images on their respective pages. Hopefully this can be resolved soon. This is probably just another small side effect caused by the migration to the Fandom platform. Aegonostic (talk) 04:52, 28 September 2020 (UTC)

Can we get an update on why all images on the wiki appear blurred? It makes the wiki hard to use when looking at the text boxes of cards. This is a pretty serious issue. Aegonostic (talk) 14:40, 5 October 2020 (UTC)

Cards that have another version in other sets[]

Cards like Twisting Nether (they all get new spell schools or new changes) have multiple pages: LegacyTwisting Nether (legacy set), CoreTwisting Nether, ClassicTwisting Nether. Since Core is the most played set because it's in Standard, why don't we rename the Core card wiki page to the card name only without brackets. For example, Twisting Nether => Twisting Nether (legacy), Twisting Nether (Core) => Twisting Nether. Minhngoc25a (talk) 10:56, 10 April 2021 (UTC).

We have already discussed about this. You can check it out here: here. Personally, I prefer the original set versions to be the main pages too because:
  • Core cards are temporary and can be removed in the future.
  • Original cards stay forever.
Organzing pages based on play rate is very subjective, and we don't have any official data from Blizzard Entertainment. Ultimately, we choose to deal with Core cards like how we used to deal with Doom in the Tomb cards, since they are functionally the same. Use25 (talk) 19:01, 10 April 2021 (UTC)

Click to view Wild format cards problem[]

Ever since the move to Fandom when I click "Click to view Wild format cards" it no longer expands into a viewable section.

Hovering over it shows:

javascript:hwcollapse.toggle( 0 )

Is there some sort of setting I need to change to make this display again? Not able to view non-standard cards on pages due to this. Tycio (talk) 18:58, 13 December 2021 (UTC)

Script error at Legacy[]

i was checking Expert1 cards before the page refresh automatically. when I expand the card list again, I got "The time allocated for running scripts has expired." on it instead.

Now fixed. VGhost01 (talk) 11:12, 24 May 2022 (UTC)

Opening discussions with Use25[]

I am ready to open to discuss with you about anything I've done ever since Forged in the Barrens update. I believe you may have been questioning about a lot of important decisions I hadn't even announced publicly, or at least informed to you before I conducted. If you have such questions, now it's the time to reply to me in this section. This includes anything, such as from adding new tags, removing old tags, to changing the template usage from {{Card infobox}} to {{Card template}}. Ultimately, I just want all of us to understand each other better to avoid conflicting in editing policies, or trying to mass-edit without discussing with the community first.

I will try to answer any of the question as soon as possible in this reply. Use25 (talk) 08:49, 30 May 2022 (UTC)

Patch 23.4.0[]

I've done importing over 1815 new cards to the wiki with the addition of Patch

I'm going to be much less active from now until July as I said in Hearthstone Wiki:News 5. There are several things I would like to notify:

  • I've created a new project for working on Credits cards, more details here. Notably, I want to rework old articles so that employee articles and credits card articles will be separated (I want to manage those articles with bots better).
  • If you are planning to work on Book of Heroes: Faelin content, feel free to use |articleCustom=true on boss cards' templates if you want to use a custom layout to add the information better.
  • Do not conduct multiple edits that conflict the editing policies without asking or discussing with other admins. No matter how much you think it is obvious, please open a discussion here so that we can come into an agreement and apply new policies, then you can do it on your own.
    • While you conduct such edits, please add the summary and add the links to the converstations if possible so that everyone knows those edits will relate to them.
  • There are several projects I left at Hearthstone Wiki:Community portal. Feel free to assign yourself in one of those projects, contact me if you have any question, and inform me as soon as you complete the project (do not edit |is_completed, as they will need revision first to confirm your progress).
  • Don't hesitate to call me if you think there are similar mistakes in multiple articles that can be dealt with my AWB Bot instead.

I'm not sure if I can at least visit the wiki once a while, so I might not be able to read your messages here. I will be mostly active on Discord, but you must ping me there.

Use25 (talk) 08:37, 4 June 2022 (UTC)

Constructed Hero Powers[]

There was a minor change of how we grouped the Hero Powers in Constructed. Hidden tag Hero card hero power will be removed, but Constructed Hero Power will be used as its replacement. Following that, Hero Powers like The Grand TournamentLightning Jolt and Whispers of the Old GodsThe Tidal Hand will also recieve this tag. This change was aimed at making the Hero Powers section of class articles more reliable to use with the pre-formatting templates.

Use25 (talk) 03:14, 6 June 2022 (UTC)

New project: Mercenaries bounty encounters[]

I have initalized a new project, Project 12. In short, I want us to start adding information about Mercenaries encounters, even if we don't have information we can get from client. To make your life easier, I have allowed us to come up with our own names for all encounters and our own ids. I have also created editing policies and style guide as a way of sharing my idea to you how I came up with the layout and how we can make these articles good and useful for readers. Both of these are not fully ready and I want to discuss this you guys if there's any statement I should add, remove or reconsider. After the discussion, we can come into agreement and follow them.

Use25 (talk) 18:59, 21 June 2022 (UTC)

Reworking on card images[]

After a lot thoughts, I have to make a very difficult decision: To reconsider a new standard for card images' ratio and canvas. Blizzard has revealed a new card type called Location with a new frame. As I had tested, if we continued to apply our current standard ratio to Location images, a part of its wood border at the top would be cropped out.

Location won't be the only card frame to be cropped out. Hero card and Golden minion frames have suffered the same condition; however, the results weren't so bad (only a part of dragon border was cropped) that when I was finalized the 33:41 ratio, I knew it was too late and didn't want to redo all the works on images I already prepared. It was my fault that I didn't take account of what the top parts could be cropped in 286x395 px images.

More problems will be broken out with the Location cards, and Blizzard already decided to release more Location cards in the future, so I decided to rework the images' standard. You can check out our old standard and our new standard with this 6 images I tested:


Unlike last time when I was working on United in Stormwind images, I'm going to share to you some details of my plan:

  • 1. Download all of our card images from Category:Card images, Category:Battlegrounds card images and Category:Mercenaries card images
  • 2. Exclude all golden and diamond images (whose name ends with _Premium@)
  • 3. Group all of card images based on their dimensions. Currently we have these dimensions and I wrote down the formula to migrate these images to new dimensions and canvas. All new dimensions will have 10:13 ratio, which is the standard of ZeroToHeroes API. I consider it to be the best source of images ever out of all these, because: No frame is cropped, it has images for all uncollectible and collectible cards, and the API is always updated to the newest patch when there are card changes, even the undocumented ones (Worst case scenario where there are outdated images, I can contact with the developer directly and he will update them the next day).
Source Old dimension New dimension
Hearthpwn or OutOf.Cards
hearthpwn.com or outof.cards
330 x 410 330 x 429
Blizzard API
419 x 520 420 x 546
ZeroToHeroes API
497 x 617 500 x 650 (new standard)
HearthstoneJSON API
550 x 683 552 x 718
Blizzard Game Press
1322 x 1642 1327 x 1725
  • 4. Rearrange the canvas based on the new dimensions. I will run an automated script to do this process. I expect there will be at least 30000 images to work on, so this work will go on for least 10 days.
  • 5. Upload all of those images to the wiki. Again, this process takes a lot of time and will take roughly half of the days I work on step 4.
  • 6. While I'm uploading, I will recheck all the images with odd dimensions and make the calculations just for them.
  • 7. Upload those images to the wiki.
  • 8. Reupload all hero card images, since they had the cropped dragon border.
  • 9. Upload all golden images straight from ZeroToHeroes API without doing anything else. (I consider its images' dimension and ratio to be our new standard)
  • 10. Update {{Card layout}} to crop the div block with the new ratio.

Note: All Murder at Castle Nathria card images will be left untouched during this transition, until Patch 24.0 is released. (They are all temporary images)

You can also check out this gallery for images taken from different sources, but rearranged to have the same 10:13 ratio without quality being lost.

Use25 (talk) 14:19, 3 July 2022 (UTC)

Project 13: Reworking Cards table part 2[]

Following the _pageData._categories not being properly stored in the last few days, I have at least made some detailed plans and initiated a new project: Hearthstone_Wiki:Project_13. Keep in mind that I might change the workflow from time to time based on the difficulties I may encounter during the project, but I will try to make announcements for such changes here.

Remember to check the details of the new tables you're going to work with here: Hearthstone_Wiki:Project_13/tables. I'm sure you will have a lot of questions and feedbacks to improve these tables, so let's bring up the discussions to finalize them. This will be the biggest project next to Hearthstone Wiki:Project 1, so please share your thoughts if you can.

There will be also discussions in our Discord server, if necessary, I will bring them here for whoever doesn't want to use Discord.

Use25 (talk) 14:48, 11 July 2022 (UTC)

will all art categories need to be manually added to the CustomCard table? (VGhost01 in Discord)
No. They will be done with AutoWikiBrowser. If an article has category Naga, the card will have CustomCard.race=Naga. If an article has category Naga art, Naga will be added to the list CustomCard.racesInArt. (Use25 in Discord)

Can not currently spend gold to buy card packs. Is this a glitch or a permanent stupid move by Blizzard....they're not saying[]

On your "gold" page

Spending gold Currently, gold can be spent in many ways:

Card pack - 100 gold One new card pack ..........

NOPE! Not any more. Please explain

Shadowborn is not part of the Maw and Disorder set[]

Both the Maw and Disorder page and the Murder at Castle NathriaShadowborn page contain this inaccurate information. When I try to remove Shadowborn from the Maw and Disorder page, I learn that set 1691 is being used for the mini-set template. I don't know how to edit this set directly (I assume it's in the site's database). I would appreciate any help with this. EnchantedRaven (talk) 00:12, 19 November 2022 (UTC)

Yeah, that’s Blizzard’s fault actually. On Murder at Castle NathriaShadowborn’s card infobox, if you open the ”Full tags” section, you can see that it has the tag MINI_SET=1. The full tags are imported directly from the Hearthstone API (official data), which means devs have mistakenly tagged the card as a mini-set card. I could remove the mini-set tag, but the next time we update our card database, the tag would come back if it was still in the official database. So we just need to wait for devs to fix it, and we can update our database afterwards.VGhost01 (talk) 00:22, 19 November 2022 (UTC)
Would the text that says "Shadowborn is a common warlock minion card, from Maw and Disorder mini-set" also come back? What about the rarity numbers on the Maw and Disorder page? EnchantedRaven (talk) 00:32, 19 November 2022 (UTC)
Yes, the text would also come back. And the rarity numbers on the M&D page. Those are all tied to the MINI_SET=1 tag. The auto-generated description for Nathria cards is ”[card] is a [rarity] [class] [type] card, from the Murder at Castle Nathria set.” and if a card is tagged as a mini-set card, the ”Murder at Castle Nathria” is automatically replaced with ”Maw and Disorder”. The mini-set article cards and rarities pull from all cards that are in the Nathria set and have the MINI_SET=1 tag. For now, I can change Shadowborn’s description manually to represent the correct set. VGhost01 (talk) 00:43, 19 November 2022 (UTC)
One more thing. Was this the right place to post this? This page doesn't seem to be used very often. I thought about posting on the Shadowborn talk page, but what if no one was watching that page? EnchantedRaven (talk) 00:54, 19 November 2022 (UTC)
It’s fine to ask questions here, but the direct talk pages for the cards are better. Even if no one is watching any particular pages, I and other admins keep an eye on recent changes that are made to any pages in the wiki regularly, so I would’ve noticed your question anyways. So no need to worry about it going unnoticed. VGhost01 (talk) 01:05, 19 November 2022 (UTC)

Linkless exists template, a substitution for ifexists and a fix for its wanted link pollution[]

Some creative folks at the avatar fandom wiki have developed a template substitute for ifexists called "Linkless exists", which checks that a page exists by checking for a property, which doesn't leave a wanted link like #ifexists does.

It's very easy to drop in, just replace #IFEXISTS: with Linkless exists|, the brackets stay the same.

Positives: Removes wanted link pollution from looking around for pages and images that will likely never be made. Negatives: Results are cached, the page would have to be refreshed for changes to appear, (easier to purge the template via the API with the forcerecursivelinkupdate parameter, this will update all linked pages in a single call). Profiling wise, is slightly more expensive than ifexists, which may present problems in complex page arrangements that are near FANDOM's limits.

I hope this helps with things. --PlNG (talk) 18:09, 27 March 2023 (UTC)