Escort to Necropolis event Bugged.

[mechanicalman.8645]

Your supposed to trigger this event by speaking to the receiving attendant at dusk or dawn and there is no way to trigger or initiate a conversation with him.

[Elie Etherion.1725]

2 days around necropolis and surroundings...still nothing and it's kinda frustrating :/Does anyone have any information about it?

[Malediktus.9250]

I saw this event going when I did a legendary bounty run yesterday. So it is probably not always bugged

[Pifil.5193]

Gonna Necro this one (haha) because it still seems to be bugged. I've spent hours trying to find this event with no joy, the receiving attendant never becomes interactable and the event doesn't seem to spawn.

From the number of Necromancers I spotted hanging around near the NPC I would say I'm not the only one with an issue.

[Mazreal Blackknight.1564]

Been trying to get this event to pop up for about 5 days now.

[Pifil.5193]

Is there any way of telling if this is a known bug? The Known Issue Tracker seems to have been abandoned for now so that's no use.

[Illconceived Was Na.9781]

For what it's worth, I've participated in it a couple of times in the last week.

---

@Pifil.5193 said:Is there any way of telling if this is a known bug? The Known Issue Tracker seems to have been abandoned for now so that's no use.

If you reported it here or via /bug, it's a "known bug."

The "Known Issue Tracker" is misnamed and isn't abandoned. It's more accurately described as a "Curated Issue Tracker," i.e. it's a manually selected list of issues that the QA team thinks is of issue to enough to sufficient numbers of people to track its status. It depends on specific individuals to update and when (not "if") they get busy, the updates slow down or stop. (It never got updated much more often than once per major release.) Consequently:

• Most bugs won't ever show up on the "Curated Issue Tracker"
• Those that do might be listed as "investigating" even as the patch that fixes them is released.

Or in brief: don't rely on it as the be-all/end-all of issues. It's better than not getting any updates and that's about all we can say.

[Pifil.5193]

Edit: Thanks Illconceived Was Na, the below might look a bit snarky but that's not my intention.

@Illconceived Was Na.9781 said:For what it's worth, I've participated in it a couple of times in the last week.

I haven't seen it spawn once despite camping the guy for hours. I'd say it's still bugged just perhaps sporadically, I'll try it tonight after reset if I can stay awake.

Where did it spawn? Did you participate?

---

@Pifil.5193 said:Is there any way of telling if this is a known bug? The Known Issue Tracker seems to have been abandoned for now so that's no use.

If you reported it here or via /bug, it's a "known bug."

Yeah, I mean known to the actual QA team as in something they are actually aware of and tracking. Some forum moderator reading it doesn't really count.

The "Known Issue Tracker" is misnamed and isn't abandoned. It's more accurately described as a "Curated Issue Tracker," i.e. it's a manually selected list of issues that the QA team thinks is of issue to enough to sufficient numbers of people to track its status. It depends on specific individuals to update and when (not "if") they get busy, the updates slow down or stop. (It never got updated much more often than once per major release.) Consequently:

• Most bugs won't ever show up on the "Curated Issue Tracker"
• Those that do might be listed as "investigating" even as the patch that fixes them is released.

Or in brief: don't rely on it as the be-all/end-all of issues. It's better than not getting any updates and that's about all we can say.

The page claims that it's updated at least once a week it hasn't been updated in almost 4 weeks, (October 28th, to be exact). So I'd say my "abandoned for now" comment is pretty accurate.

Also, where does your information on how ArenaNet works come from?

[Illconceived Was Na.9781]

@Pifil.5193 said:

@Illconceived Was Na.9781 said:For what it's worth, I've participated in it a couple of times in the last week.

I haven't seen it spawn once despite camping the guy for hours. So I'd say it's still bugged.

Where did it spawn? Did you participate?

I picked it up near the Necropolis. Yes, as I wrote (and you quoted), I participated.

---

@Pifil.5193 said:Is there any way of telling if this is a known bug? The Known Issue Tracker seems to have been abandoned for now so that's no use.

If you reported it here or via /bug, it's a "known bug."

Yeah, I mean known to the actual QA team as in something they are actually aware of and tracking. Some forum moderator reading it doesn't really count.

And that's what I mean: they track everything we report.That doesn't mean it gets priority treatment, nor whether they agree it's even a bug (as it can happen sometimes that things are "working as intended" or "user confusion"). The stuff reported via the in-game /bug tool is automatically added to their tracking system.

The "Known Issue Tracker" is misnamed and isn't abandoned. It's more accurately described as a "Curated Issue Tracker," i.e. it's a manually selected list of issues that the QA team thinks is of issue to enough to sufficient numbers of people to track its status. It depends on specific individuals to update and

when

(not "if") they get busy, the updates slow down or stop. (It never got updated much more often than once per major release.) Consequently:

• Most bugs won't ever show up on the "Curated Issue Tracker"
• Those that do might be listed as "investigating" even as the patch that fixes them is released.

Or in brief: don't rely on it as the be-all/end-all of issues. It's better than not getting any updates and that's about all we can say.

The page claims that it's updated at least once a week it hasn't been updated in almost 4 weeks, (October 28th, to be exact). So I'd say my "abandoned for now" comment is pretty accurate.It was never updated once a week for longer than 2 weeks. So I'd say relying on their statement is "pretty inaccurate" as is the claim that it's "abandoned for now" — it gets updated a few times a year now, as it has since it was first introduced.

Also, where does your information on how ArenaNet works come from?From statements made in the forums and Reddit. The person who started the "Known Issue Tracker" explained how & why it was set up and mentioned when someone else took over the duties. Various people from the QA team have explained how they learn about bugs/issues/etc. And that's all consistent with how these things work with other QA departments.

To be clear: I'm not questioning whether people are having trouble. I'm only commenting on my own experience.The biggest difference between the two situations is: the OP is looking for the event and I happened along it, i.e. bugged or not, there's a "watched pot never boils" sort of effect that makes it seem dire to the OP.

And also to be clear, I'm not trying to defend ANet's use of the Known Issue Tracker. It's a terribly misleading name for what it does. I also don't support their claim that it's updated "once a week". As I mentioned above, I think they managed to get 2-3 weeks a couple of times. And often, they were just updating the status of things that had been fixed in earlier releases.

So it would be better for them to call it a Curated Issue Tracker and to state that they update it as often as possible. And it would be helpful for them to clarify that only some things are tracked: important issues aren't always listed. So while it's very relevant if something is on the list, we can draw no conclusions from from an issue's absence on the list. All that means is that it's not on the list.

[Pifil.5193]

Thanks Illconceived, I missed the "I've participated" part and then asked you if you participated, duh.

Thanks for clearing up my misconceptions about the way the issue tracker works, that's a pity.

[Pifil.5193]

Finally! :)

The event just popped at about 10 or so minutes after reset at 12:10, I was near the Receiving Attendant but there seemed to be no need to actually talk with him (I had a good view and couldn't see anyone next to him). An announcement popped up and the location of the Funeral Procession was pinged on the map. It pinged north of the Necropolis Waypoint along the road in a grove surrounded by Sand Lions including a Veteran or two. I turned on my Mentor tag and a horde of people swarmed the event. You can heal the casket between fights with the Skimmer attack.

I still think the spawn is bugged (or else on a very long timer) but I also think the information in the wiki is a little wrong. I might edit that.

[Illconceived Was Na.9781]

@Pifil.5193 said:Thanks Illconceived, I missed the "I've participated" part and then asked you if you participated, duh.

Eh, blame me for that; it's a wall of text.Also: I wasn't looking for the event chain; I just stumbled upon it on the way to something else, so my feeling about what's going on also differs from the OP's. To me, it was just a bonus event; the OP is trying to finish off a darn collection and it's a lot more frustrating when the events aren't triggering as expected.

Thanks for clearing up my misconceptions about the way the issue tracker works, that's a pity.

Yeah, it really is. In its current form, it gives the impression that they aren't paying attention. When it's the opposite: the busier they are, the less likely it is the tool gets updated. I really hope they can update the name and the description to accurately reflect its value.