Guild Wars 2

Has anyone else got a strange seedpod stuck on your back in Auric Basin?
What is it? I can provide a picture.

it is always there until you have completed a certain part in the HoT story, then it goes away.

Thanks, it was starting to freak me out. I took off all accessories but it stayed until I changed maps.

Its not a seed pod, its the dragon egg inside a backpack made of plants.

No…no…it can’t be….its…its…

nottsgman.8206:

it is always there until you have completed a certain part in the HoT story, then it goes away.

Mine never went away. I’ve reported it several times since HoT launched, but it’s never been fixed. I can replay the story step and get rid of it, but it reappears as soon as I leave the map and come back.

Quarktastic.1027:

nottsgman.8206:

it is always there until you have completed a certain part in the HoT story, then it goes away.

Mine never went away. I’ve reported it several times since HoT launched, but it’s never been fixed. I can replay the story step and get rid of it, but it reappears as soon as I leave the map and come back.

There’s a thread to report tickets that have not been addressed in over 3 days:

https://forum-en.gw2archive.eu/forum/support/support/GW2-Tickets-for-Review-3-days-older-2

Djinn.9245:

Quarktastic.1027:

nottsgman.8206:

it is always there until you have completed a certain part in the HoT story, then it goes away.

Mine never went away. I’ve reported it several times since HoT launched, but it’s never been fixed. I can replay the story step and get rid of it, but it reappears as soon as I leave the map and come back.

There’s a thread to report tickets that have not been addressed in over 3 days:

https://forum-en.gw2archive.eu/forum/support/support/GW2-Tickets-for-Review-3-days-older-2

A bug like that wouldn’t be a ticket. A customer service representative probably can’t fix something like that. There’s a difference between game bugs and asking for someone to refund a purchase mistake or help you log into the game.

I’m pretty sure something like this requires the developers to actually fix the bug. It’s very unlikely it’s something customer service can help with.