I had this exact problem, the receipt email just had an empty box where the serial code was supposed to be. Contacted support and after an initial misunderstanding they provided me with a text copy of my purchase receipt, which contained all the relevant info as well as the missing serial code.
So if you’re worried about it, or want to be safe in case of any future mishaps, I recommend you contact support and they can help you out!
It seems you (the moderator who went on a delete spree through my posts) moved my thread from the warrior forums to the patch update forums, as well as removing update posts from this thread instead of the moved one.
Specifically the posts about the line I added to Head Butt and King of Fires on the wiki to reflect their buggy nature at the moment and the update on how I narrowed down the bug.
I’m not sure how you tested this, but I tried it with with Savage Instinct selected in my traits, and it did trigger Eternal Champion just fine. The trait also works if you break the self-stun with abilities like Outrage or Endure Pain.
Keep in mind that going into Berserk is not a stun break unless you trait for it.
Headbutt not triggering (6) bonuses if you are stunned by it is not a bug, the runes bonus is a skill and you cannot use skills while stunned. The stun from HB appies 1st, before the rune is triggered.
Except it did work until very recently (the July 26th patch, to be exact). I can’t see how excluding head butt from being able to trigger runes, as well as traits, is an intentional change. This would make it the only elite skill (or only rage skill, in the case of King of Fires) in the game that would not be allowed to trigger such things.
The self-stun part also no longer triggers other traits, such as Last Stand, which should be working regardless of being stunned.
It seems to be more of an unintentional side effect of fixing the animation/self stun cancel that you were able to pull off with queuing up something like Shattering Blow when you used Head Butt.
I have started noticing this as well. At first I thought it was my keyboard/mouse buttons being stuck and pressing themselves, but after a bit of testing and paying closer attention to when it happens, it appears to be a bug like you’ve concluded.
This bug, as well as the the two other very noticeable ones (Banner #5 skill not actually being an ability and Head Butt self stun breaking trait and rune triggers) are something that could really use some attention. I wish the known issues tracker would be updated to reflect if they’re being looked at, and if they’re not, then they should be.
I would really like it if we could at least get some confirmation if this issue, as well as some of the other currently aggravating warrior bugs (Head Butt self stun breaking trait and rune triggers and F1 burst skills randomly firing by themselves), are being looked at. It’s so hard to know if they’ve caught the attention necessary for fixes, since they’re not being added to the known issues tracker, when it’s been almost a month since the patch released.
I would really like it if this bug, as well as some of the other bugs present in the warrior skills at the moment (F1 Burst casting by itself and banner #5 skill not actually being an ability), could be looked at soon, or at the very least added to the known issues tracker, so that we know people are aware of their existence.
This seems to be the same bug that is making Head Butt not trigger the Fire Shield detonation from the King of Fires trait. I’m guessing it’s from the changes they made regarding this specific line in the July 26th patch notes: Head Butt: Fixed an issue in which skills could be executed before the warrior stunned themselves.
I’ve reported it on the bug report forums, as well as made a note on the wiki entry’s for both abilities:
Head Butt (Berserker elite Rage skill) no longer detonates instances of Fire Shield on you with the King of Fires trait selected, ever since the patch that changed it to a longer cooldown in pvp. I have tested it to be working with all other Rage skills (even the heal), Torch skills (4 and 5), Primal Burst skills (F1 while in Berserk, F2) as well as going into Berserk itself (F2), and they all trigger it like they should.
Edit:
This thread has had a bunch of updates removed, see image for what was in it before.
I am very curious how the changes on Tuesday will be implemented and the cynic inside me wants to agree with most of the points you brought up. I really don’t want to get my hopes up only to get them crushed once again.
I guess we’ll see what happens on patch day and I’m sure we’ll return here to compare notes.
I am fairly certain that this is not a hardware specific issue to one person as I have also noticed a spike in temperature on my GPU since the edge of the mists patch. It is only tied to this game, no other action on my computer even comes close to breaking 90°C on the graphics card.
I am using an AMD Radeon HD 5850 with the fan manually set to 100% in the Catalyst Control Center and yet the overheating is constant while playing Guild Wars 2.
