Miss Marigold

I can confirm this is not working. Thank you for sharing! The problem does seem to be vastly reduced overall though. Hopefully they'll continue to tune things!

Amity Fields is very, very, very active!

Examples, please! I also hope you reported the issue in-game when you encountered it!

That may well be the case. It's not "my string" that I've noticed being fixed though, for what it's worth. Rather, every single string I've known not to work suddenly worked fine. I was hopeful this meant the issue was fixed, but I suppose that's not the case. Something definitely did change though!

I know you read my bug report because you commented on it, so you should understand what I'm talking about. As the bug report says, certain strings were being rejected with 100% reproducibility. If you have examples of any such strings where this is still a problem, please share them.

Yes, me too, but… that was a night or two ago! I'm specifically interested in issues occurring after my post. If anyone knows this issue is not fixed and has an example of a string that doesn't work, please share it!

So far as I can tell, this issue is finally fixed! If anyone is still running into this bug, please post and let me know!

I've posted a desperation plea to Reddit in order to encourage more people to report this bug. If any of you care to get your butts over there to upvote it for visibility, it would be much appreciated! Yes, I am being completely shameless about trying to get this fixed!

For Santasha? No, not at all. If your heals were hitting for as much as you say they were, your tank probably had inappropriate armor.

Personally, I'd rather send one big block and then send a "(done)" or equivalent—our company uses "<3" for this purpose—than have to hope every part of a multi-part post went through. With how I do it, I can be 100% sure that everything's getting to the other end—even if it does mean that I occasionally need to break up posts (and send a "<3" after each part) if the other person tells me they didn't see anything.

The post is now in the "Accepted Bugs" forum and cannot be commented upon. I strongly urge you to use the bug reporting feature that's present in-game the next time you experience this issue.

The only way to fix it is to report the problem the next time you run into it. Include the exact text that was dropped, make it clear that it's 100% reproducible, state that it makes no difference who sends it or how it is sent (/party, /say, etc), and so on. If enough people report this issue and report it clearly and accurately, I'm sure it'll get fixed eventually. Please don't neglect to report this bug just because I've already reported it! SE is swamped at the moment and prioritizes whatever has the most people clamoring for a fix. As bad as it is, lots of people filing related reports is probably the only way this issue will be resolved within the next month or two.

Has anyone heard anything about this? It's been over five weeks and this bug is still driving me completely bonkers!

It's a secret! Usually we'll start off doing work for the Wailers or similar with location information coming in via linkpearl so we know where to gallop off to. After a bit though, you just RP about whatever while you run around and kill things. It's just not any fun to pretend goblins are attacking the same thing again after you've already dispatched them several times! The fact that events in this game are sort of icky, don't really chain much, and generally disappear without consequence if a timer runs out makes it hard to address them too directly. Guild Wars 2 does it a lot better!

Edit: Please ignore this post! I think I misinterpreted what I was replying to!