Bugs / glitches[edit source]
Can I post "this just happened to me, maybe somebody knows if it's a bug or what" here? I'm not sure If I can just dump whatever glitch I run into into the bugs list.
New cards in my collection have a blue glow and each class' tab shows the number of newly acquired cards. I've just got some cards from the first wing of Naxxramas, didn't view them, but only two pairs of recently acquired cards from the class challenges are marked as new, four pairs of neutral cards are not. I know I can filter the cards to find all Naxx cards, and as I have only a few, it's trivial, but WTF? -- Karol007 (talk) 16:16, 21 June 2015 (UTC)
- New bugs should be verified from at least 2 sources, and have screenshots/videos to proof them, otherwise anyone can claim that a bug exists. A single source should be ok if it is a video though. Personally, I do not really care about tracking tiny minor UI bugs, because it is the bugs that affect Gameplay that are important, not the UI ones (unless the UI bug significantly affects gameplay). Technical and compatibility bugs are also something this page shouldn't care about (eg, the last Hearthstone patch is incompatible with Razer Comms and Razer Synapse, resulting in a pink background whenever a card is mouse-overed). --Xinhuan (talk) 16:45, 21 June 2015 (UTC)
- OK, thanks. I've noticed similar glitches being added to bugs section e.g. Tavern_Brawl#Bugs, that's why I posted at all. -- Karol007 (talk) 23:02, 21 June 2015 (UTC)
Flame leviathan's living bomb is incorrectly listed as a bug[edit source]
Flame leviathan's living bomb is incorrectly listed as a bug, claiming that it is inconsistent with explosive sheep and on-damage triggers. This is incorrect because 'damage all characters' and 'damage all minions' effects behave differently in this respect. Flame leviathan's mechanics is consistent with other damage all character effects like abomination, and baron geddon. You could possibly consider the different behaviour of the 2 texts to be a bug, but flame leviathan specifically is not a bug. Here's hearthstone science's video showcasing the interactions: https://www.youtube.com/watch?v=V7Y0V2kKM2A
Season rewards[edit source]
I've ended August at rank 19, I've got my rewards: a golden card, some dust and a card back. I'm starting the September season at rank 23, as per Ranked#Season reset. I quit HS and logged back again and I got the 'season reset' animations again. It said I've ended the season at level 23 (?!) so I start the current season at level 25.
Bugs page reorganization[edit source]
The Bugs page has grown over the year to its current state and size, and is fast becoming hard to maintain by being too long. Most of the bug tracking has shifted over to https://github.com/HearthSim/hs-bugs/issues as well, but keeping the bugs on both places synced is also starting to be unwieldy. There are 3 proposals.
- Split the Bugs page into multiple pages (Gameplay Bugs, Adventure Bugs, Sidebar Bugs, Animation Bugs, UI Bugs, etc) with the main Bugs page as the hub.
- Reduce the size of the Bugs page by giving only a 1 line description of each bug, and link to the corresponding bug entry on https://github.com/HearthSim/hs-bugs/issues.
- Only list frequent or easily-encountered bugs on the wiki, or bugs that affect gameplay in major ways. This cuts down on listing bugs. or issues that will likely interest nobody (such as missing sounds on adventure minions, or minor animation bugs).
Taohinton, do you have any input on these options or have any better ideas? Option 2 and 3 will amount to deleting information from the page. Option 1 and 3 will break existing links, or break links to sub-headers on the page. -- Xinhuan (talk) 05:22, 10 November 2015 (UTC)
- Well, if the problem is wasting effort maintaining two lists, option 1 isn't going to help. I'm not sure how much option 2 will help? Since you'll still need to maintain the full list, and many descriptions are pretty short already. If you're reaching breaking/splitting point with the effort (which I certainly understand) I guess option 3 sounds like the best option. If you were focusing purely on the wiki then option 1 would make sense, but I assume github is critical for the people involved there, in which case I guess it makes more sense to cut the wiki page back.
- I'm assuming the idea would be to state clearly that the page lists only common/significant bugs, and link to github for an exhaustive list? I tend to think the wiki page probably gets a lot more views, but at least a link can help those interested in more detailed stuff to find it. You might want to consider how you define "common/significant" (or whatever criteria you choose), since obviously that's going to be subjective. -- Taohinton (talk) 01:43, 12 November 2015 (UTC)
As discussed in the above topic from last year, the maintenance of this page has apparently become too onerous and/or problematic for the editors previously maintaining it, with the result that it is now nearly a year out of date. As suggested by Patashu, since an up to date list is still maintained online, I've therefore blanked the list here and provided a link to that site. -- Taohinton (talk) 20:40, 17 October 2016 (UTC)