VoN 5 - Haywires Voice

[Coldin]

Our guild was running a VoN run this weekend to see how much Velah had changed, but to our surprise, we found out VoN 5 changed a little too.

Normally, there's a few people that pick up a Haywires Voice, as the other items aren't really needed. Multiple voices allow us to move through the raid a bit faster since some people can split off from the group and speak to the speaking stones. There never seemed to be any problem with this to me.

But now Haywire is only allowing one person to take his voice. Now maybe I could understand this, as there could be some hidden exploit with taking multiple voices, but that's just part of the problem. The voice also can't be traded to another party member, is destroyed when dropped, and binds. We did fine with the change, but this could lead to some very big problems for any groups attempting the raid.

First off, say the person with the voice went on an extended afk or had a disconnect. Your group would be stuck there till either that person returned, you managed to get a GM to help you, or you restarted the raid.

Or say the person got killed and released, that voice would vanish, leaving the group only the option to restart. There's a ton of room for griefing here too, which is never good for the game.

Basically, I'm asking that either Haywire's Voice gets changed back to a multiple drop, or the sole voice drops on death, disconnect, recall, and can be traded between players.


I also bug-reported this, just in case it was merely a bug.

[Gratch]

I noticed this too. We've had problems with the voice leaving via discon, release, accidental release etc. It could be a major problems with PUG's. Probably the best thing now is to have the group leader take the arcane signet, the voice and make sure they aren't a disconnector type.

[narizue]

This was a seriously aggravating and poorly conceived change that I hope(not keeping my fingers crossed here) is a bug. It causes all sorts of potential problems that all end with one of two options, call a GM or restart the quest.

When everything runs like clockwork its no big deal. But if something goes wrong it becomes much more aggravating.

Bad change made I am sure to prevent some sort of exploit that punishes the relatively casual players.

That just makes bad sense to me.

Just my 2cp

[Blazer]

I personally haven't run VON since this change, but a guildie of mine has and told me about this new "feature". Unless there is some exploit that I was not aware of, this seems like simply making a change for the sake of making a change. Too many bad things can happen to the person with the voicebox (death in lava, DC, recall accidentally, etc) that would cause headaches. I hope the 1st tier GMs can at least fix this when a ticket is put in. Having to wait for 2nd tier GM response will be annoying.

[tihocan]

I agree, it needs to be looked at. If the voice gets destroyed Haywire should give a new one.

[DagazUlf]

We ran into the problem on our very first run after Mod5 (discussed here). It's an awful change, and I cannot imagine they designed and tested it out to work this way...

It's an oversight, right devs?

[binnsr]

should be drop on death / exit and/or tradable.

Many of the original quests in the game had this same issue (Redwillow's artifacts springs to mind) rendering the quest uncompletable if someone d/c'd - introducing drops on leaving the instance was the solution in beta.

[Caliban]

Yes, this is a rather annoying change. I liked it better before.