Pact Requisitioner Hargrove does not exist...

#1 - Oct. 22, 2012, 9:15 p.m.
Blizzard Post

Upon logging in after the Oct 22 update I received a Pact Victory Token in the mail and was instructed to exchange it for a lovely new weapon by visiting Pact Requisitioner Hargrove in Fort Trinity.

One hitch…that NPC does not exist. About 30 or 40 players have spent the last half hour combing every square inch of the place and he’s nowhere to be found.

Could we please requisition a Pact Requisitioner with your next update.

#19 - Oct. 23, 2012, 1:23 a.m.
Blizzard Post

I’m curious, were any of you in a group when you finished the game and couldn’t talk to him?

If you can’t find him, he’s located in an instance of Caer Aval (Fort Trinity) in the Straights of Devastation after completing the game, too. He is NOT available in the public map, which is why its blocked off.

The entry to this area is southwest of the Fort Trinity Waypoint and at the north entrance to Caer Aval. There is no marker for the instance entry like you’d normally see for Story steps, so just approach the door and you’ll get the prompt.

Once you’re in, he should be spawned straight ahead. If you don’t see him, wait around for a couple minutes and he should appear.

-Bill

#22 - Oct. 23, 2012, 1:36 a.m.
Blizzard Post

Investigating, sorry about that!

#25 - Oct. 23, 2012, 3:08 a.m.
Blizzard Post

Good news, we’ve figured out the bug! We will have this fix pushed into the next build (not the build we just ran as I’m typing this) whenever that ends up being. I don’t want to leave you guys hanging, but I can’t promise any dates/times either.

But it will be soon my young grasshoppers, soon.

-Bill

Edit: And when I say the “bug”, I mean the instance entry not being present.

#37 - Oct. 23, 2012, 11:20 a.m.
Blizzard Post

Hey everyone,

While we have multiple points where we check for issues and multiple people watching for these (all part of that delay time between builds), there are times when we make mistakes that get into the game, despite our best efforts. It’s an unfortunate reality of game design and human nature.

That being said, we try to fix these issues as soon as they’re identified; and as Bill mentioned, we’ve found this issue and pushed a fix for it into our next full build. As this issue has been resolved, I’ll be closing this thread.

Thank you for your patience and understanding; we’re always working to improve our processes, and we appreciate your support!