Guild Wars 2

I have purchased the Marriner’s Horn a very long time ago and I enjoy playing it every once in a while, but it currently has a very nasty bug.

I play notes and it can last as long as I can hold it, but whenever I wish to press the next note, there is an instance where it skips the audio and makes it sound like you pressed the same button twice in a row when it isn’t the case. It can happen multiple times in a row if I press another note afterwards and so on, making the idea of playing the horn precisely almost impossible. Its easy to test the bug, just play and hold a note, then go press another and next.

Hope you can fix it soon.

I just purchased the horn for gems today and well… yeah. This bug needs to be fixed or I am going to need a refund on gems.

By the way this is my first post on the forums here. I am an optimistic person so i will try and be patient and hopeful that this issue gets acknowledged and or resolved soon

Wild

I’m sorry you had this misfortune. It worked fine before, but this bug is so terrible. Anet is usually good with being able to look and fix some of the bugs in the game. Lets hope for the best.

Horn went on sale…I assume someone else purchased it. Sorry to those who did

Tried to link a short 1-min vid to this post to show the bug but after 4+ min kept getting this message:

This site can’t be reached The webpage at https://forum-en.gw2archive.eu/forum/support/bugs/BUG-Marriner-s-Horn/reply might be temporarily down or it may have moved permanently to a new web address. ERR_CONNECTION_ABORTED

Sounds like the video was too big for the forums; you could throw it on youtube or something if you want?

He is a quick video

https://youtu.be/qTpLp8rpHLQ

Alas. You might be able to get a refund or personal reply by contacting support, but that video demonstrates the issue you experience — so hopefully the QA team will be able to reproduce it.

SlippyCheeze.5483:

Alas. You might be able to get a refund or personal reply by contacting support, but that video demonstrates the issue you experience — so hopefully the QA team will be able to reproduce it.

Oh thank goodness someone had video evidence of the bug. I hope Anet can fix it soon.