Wrong quest requirements

[artista]

Hey I was trying to twink up my lvl 28 hunter by doing the STV questline for Master Hunter's Rifle, which is the 3 animal quests: tiger, panther and raptor mastery, leading to the quest: Big Game Hunter. The requirements starts out with lvl 28 but raises for tiger and panther mastery on the last part, and the third part for raptors to lvl 31. This rly sadness me because when I played vanilla back in the days, this Master Hunter's Rifle was obtainable.

Another issue is the gloves Razzeric's Racing Grips which was obtainable in lvl 29, but now through the questline, starting with Load Lightening and ending with Safety First, ends with a lvl requirement of 41

I hope this issue would be changed so our beloved hunter twinks can keep going on their journoy to glory in tons and tons of BG's

Best regards
Artista

[Freddydk]

I have the same problem, plz fix
Cheers Freddydk

[Lacrave]

Has there been any word on this? I wanted to stop in the 20-29 bracket for a little while before leveling. I definitely used to have the raptor hunter tunic/master hunter rifle on my 29 in this patch

[Lacrave]

I just realized that there's another thread where proof is asked for so here's what I can find.

"By Aestil on 10/26/2006 (Patch 1.12.2)
This gun is attainable by completing all of the hunter quests in STV. You get a final quest to kill the master of all the beasts or something. There is also a bow which can be rewarded.

The main reason this gun is amazing is that it is attainable by a lvl 29 twink. And because the gun is a high lvl, a +40 friend can attach the +7 dmg scope to it."

http://db.vanillagaming.org/?item=17687#wh-comments

This is a comment from from vanillagaming about the gun being used in patch 1.12.2

Next is a guide for 20-29 twinks that lists the gun as bis

"Range: Ironweaver / Master Hunter's Rifle [+5/+7range dmg]
Ring: Seal of Sylvanus / Plains Ring
Ring: Basalt Ring of Monkey / agility (WSG Ring) "

http://www.blizzardguides.com/20-29_bg_warsong_gultch_twink_guide.html

The guide itself doesn't have a date (as far as I can tell). It does however talk about talent builds that were in 1.12.2, but changed in later patches which can help to date it (1.12.2 or before). A specific example is the warrior spec

"0/11/9

5/5 Cruelty
5/5 Unbridled Wrath
1/1 Piercing Howl

5/5 Shield Specialization
4/5 Iron Will "

In patch 2.0.1 Shield Specialization was moved to a tier 2 talent and Iron Will was changed to an arms talent.

2.0.1 talent tree: http://www.wowprovider.com/Old.aspx?talent=2006080_1
1.12.1: http://db.vanillagaming.org/?talent#L


Here's the other thread in case this should be merged
https://forum.nostalrius.org/viewtopic.php?f=45&t=10550&p=74148&hilit=master+hunter#p74148


Edit: Here's a video showing a 29 hunter with the master hunter rifle (you can tell from the model in game and the description of the video). Based on the post date it's from before Jul 29, 2006 and based on the raid chat in game (it's before cross-server battlegrounds), the video is from before patch 1.11.2.

https://www.youtube.com/watch?v=wEg8DxSSYyE

I went through the next several patch notes and the only mention of changing the quest is after the TBC release, and that was only to nerf the gun, not change the level requirement.

[Hydra9268]

Please post this in the Bug Tracker. The forums are used for discussion. The BT is used to ... well, you know, track bugs.

[hcklive]

anyone know if this has been changed yet?

[Happy1337]

Would be great if someone has an update on this

[mouthbreather]

Bump. I'm also twinking at 29 and need to know if this is fixed.

Any word?

[Mantis]

I can confirm that this is not fixed yet.
I didn't see this in the bug tracker so I just submitted it, from my experience they haven't been very responsive though.

edit: as it turns out there actually is another post for this in the bug tracker from May, but it's still listed as "new"

[hcklive]

I can confirm that this is not fixed yet.
I didn't see this in the bug tracker so I just submitted it, from my experience they haven't been very responsive though.

edit: as it turns out there actually is another post for this in the bug tracker from May, but it's still listed as "new"

Thanks Mantis, appreciate the update.