HUnting Patrannache, wtf man!

[Romire]

So ive been hunting this bird for almost 2 months, and i just cant find him, ive been sitting on his choke point 25,6-50.8 in Valley of the Four Winds

And this bird just doesnt want to cross the path i sit on, so i go and try and look for his footprints, but cant find em either cause their so bloody small and not showing up.

Ive turned ground clutter to low so i could try and see em, but that doesnt work.

Anyone got some advice at all?

[Hilde]

Are you doing rounds as well, following his path looking for footprints? That's what you meant right?

[Romire]

Are you doing rounds as well, following his path looking for footprints? That's what you meant right?

yup, preety much

[Deleted]

Well, I'd download NPCScan, leave WoW alttabbed while camping one spot. Make sure to mute WoW sounds and make NPCScan unmute it whenever it finds a rare :P Should work well

[Myzou]

Well, I'd download NPCScan, leave WoW alttabbed while camping one spot. Make sure to mute WoW sounds and make NPCScan unmute it whenever it finds a rare :P Should work well

I don't think you know how the hunter rares on Pandaria work.

As for the TC: Just keep trying. He's not very fun to find.

[Daetur]

Well, I'd download NPCScan, leave WoW alttabbed while camping one spot. Make sure to mute WoW sounds and make NPCScan unmute it whenever it finds a rare :P Should work well

The hunter rares in Pandaria don't work like that they're permanently stealthed, so it's extremely unlikely that NPC Scan will pick one up.

Patrannache isn't one that I've hunted, so I don't have any specific advice, unfortunately.

[Tziva]

Don't camp one spot; someone could be taming before he even gets there. Run his path, counter the direction he walks.

It took me a couple days of looking but that's how I found him.

[Deleted]

When I did it i started on one end (close to galleon) and followed the path til i found his tracks. Must've found the tracks and then lost them again atleast 5 times before I tracked him down, he's by no means easy to find.

If you wanna camp a spot, make sure you've got the time, patience and the right spot.
IIRC it takes him like 2 hours to get from one end of the track to the other, so if you're unlucky you might spend up to 4 hours spamming flare (that's 720 flares)

GL and happy hunting

[Romire]

I don't think you know how the hunter rares on Pandaria work.

As for the TC: Just keep trying. He's not very fun to find.

I cant find his footprints to know if im behind him or if ive already passed him, its really annoying cause his prints are so slow

[Deleted]

Don't camp one spot; someone could be taming before he even gets there. Run his path, counter the direction he walks.

It took me a couple days of looking but that's how I found him.

Also this. For all you know someone else might be camping another spot and you'll sit on the other end yelling "Where the fuck are you!?".

Hunting is better than camping.

[Romire]

Don't camp one spot; someone could be taming before he even gets there. Run his path, counter the direction he walks.

It took me a couple days of looking but that's how I found him.

So start at the end of his path and walk backwards your saying Dinosaur mod? :P

[Kinferatu]

I have tamed this on my hunter, it is a pain to find, especially when I searched for it, its tracks were backwards, joy.

The tracks are verrrrry tiny, so fly close to the ground.

http://www.wow-petopia.com/look/cranepink.html click the link within that, helped me finding him. :3 x

[Draelandria]

This video might help you a bit. It shows a map of Pats walking path. It's tracks are super tiny, and hard to see. You should turn your ground clutter to the lowest setting to make it easier to visualize the tracks. From one end of it's walking path to the other is about an hour and a half walk, so three hours for full circle. Spawn timers are random as well from what I have heard. Hope this helps.
http://www.youtube.com/watch?v=t-cxLoBbWcs

[Tziva]

I cant find his footprints to know if im behind him or if ive already passed him, its really annoying cause his prints are so slow

I lost his prints a bunch of times when I was chasing him, but once you know the general area he is in, if you lose track of him, just run ahead 40 yards and start spamming flares and eventually he'll get to you.

I even uploaded a screenshot of his track here:
http://www.wowdb.com/npcs/50885-patr...lated:comments

[Romire]

I lost his prints a bunch of times when I was chasing him, but once you know the general area he is in, if you lose track of him, just run ahead 40 yards and start spamming flares and eventually he'll get to you.

I even uploaded a screenshot of his track here:
http://www.wowdb.com/npcs/50885-patr...lated:comments

So hes path is still backwards? wowhead says its normal now

[Hilde]

The print's are called barely visible for a reason, unfortunately. :/

Even when I had found the prints I had trouble finding the following ones. So I decided to go further down the path and spam flare where I knew he would walk past.

I think he had just spawned when I saw them, since I had followed the path to the end without seeing anything, alt-tabbed for a short while, and came back to prints at the "end" of the path south of the heartland.

NPC scan can help you I think, if you use a tedious methot of camping where you basically spam flare until he appears.

[Asmekiel]

I found it twice in two days. First day I was helping a guildie find it, second day I was after it myself. Found it twice while going from the Singing Marches to the Stormstout Brewery. First time it actually made a full lap while we were trying to track it.

[Hilde]

So hes path is still backwards? wowhead says its normal now

It was the right way for me

[Tziva]

So hes path is still backwards? wowhead says its normal now

Yeah it's been fixed, the comment is outdated but screenshot is still accurat.e

[Asmekiel]

It was the right way for me

Yeah it's been fixed, the comment is outdated but screenshot is still accurate

I was so confused when I came back after a 6 month break. Suddenly the prints pointed the right way and nothing about it in the patchnotes either.