Hearthstone Wiki
Register
No edit summary
Line 16: Line 16:
   
 
The Nozdormu change is still documented on the card's own page, as well as [[Hotfixes]]. -- [[User:Taohinton|Taohinton]] ([[User talk:Taohinton|talk]]) 03:21, 21 September 2015 (UTC)
 
The Nozdormu change is still documented on the card's own page, as well as [[Hotfixes]]. -- [[User:Taohinton|Taohinton]] ([[User talk:Taohinton|talk]]) 03:21, 21 September 2015 (UTC)
  +
  +
== Silithid swarmer is now a beast ==
  +
  +
Silithid swarmer's changes need to be documented here. Gracias. Correspond patch number to this change. [[User:Aegonostic|Aegonostic]] ([[User talk:Aegonostic|talk]]) 14:19, 18 July 2016 (UTC)

Revision as of 14:19, 18 July 2016

More sections

If we divide each (or at least the long ones) patch into sections for each hero / class, editing is much more pleasant. Compare the structure of Card_changes#Patch_1.0.0.3388_.282013-06-22.29 with Patch_1.0.0.3388. -- Karol007 (talk) 22:59, 2 June 2015 (UTC)

Have you linked the wrong section? Those appear to be identical except for the 'All classes' header. -- Taohinton (talk) 20:14, 3 June 2015 (UTC)
I mean e.g. ';Druid' v. '====Druid====' -- Karol007 (talk) 00:38, 4 June 2015 (UTC)
Ah, okay. Which format were you suggesting using, and for what reasons? -- Taohinton (talk) 23:44, 6 June 2015 (UTC)
Is there any downside to using '====Druid====' over ';Druid'? The former offers better granularity and IMHO allows for easier editing. -- Karol007 (talk) 18:33, 7 June 2015 (UTC)
The downside would be that those sections would be added to the TOC. In this case of Card changes, this could mean a very lengthy TOC box (more than double its current length) most of which referring to largely irrelevant changes during alpha and beta. I actually tried this out in preview and it's pretty insane, and I don't think adds any value to the page. -- Taohinton (talk) 16:56, 9 June 2015 (UTC)
Ah, OK. Case closed :-) -- Karol007 (talk) 20:55, 9 June 2015 (UTC)

"Card changes"

I've just undone an edit adding the recent fix to LegacyNozdormu's behaviour to the page. While this is a change to the card, it is not a change to the stats, card text, function or other basic properties or behaviour of the card; only an adjustment to the underlying tech. Further, the change was officially described as "Resolved an issue with Nozdormu ..." which is reasonable considering it was never the designers' intent for Nozdormu to hold up the game in this way; this makes it more of a bug fix.

I've also clarified at the top, the concept for the article. We have Bugs for bug occurrences and fixes; and individual card pages list changes to card phrasing, and other minor details. This page is intended to be a list of actual intended changes by the devs, which are pretty rare. (Hence the lengthy format for the post-release portion of this article, discussing the motives behind the changes, etc; this is something that is warranted and reasonable considering the rarity of the changes. The pre-release section is a slightly different deal.)

While many important changes to cards come in the form of bugs and their fixes, if we start including these this page will shortly become a duplicate of Bugs, with the only difference the inclusion of intended changes too. Short of that, we're selectively including a few of the dozens of bugs, and not the others, which is very inconsistent. The current article is of value because it lists the intended changes, and explains the context in which those changes were made. This makes it a good counterpart to Bugs, as well as an interesting read in terms of design and history, and for players returning to the game.

The Nozdormu change is still documented on the card's own page, as well as Hotfixes. -- Taohinton (talk) 03:21, 21 September 2015 (UTC)

Silithid swarmer is now a beast

Silithid swarmer's changes need to be documented here. Gracias. Correspond patch number to this change. Aegonostic (talk) 14:19, 18 July 2016 (UTC)