The frozen maw meta event is bugged. It’s stuck on the totem part….
Are any events active in the area? When the investigation completes, it immediately starts the totem event. I’m trying to find out exacly where it got stuck. (And I don’t have GM commands on the Live servers, so I can’t check the servers listed above.)
So the totem is destroyed, but the shaman hasn’t appeared? Does anybody know if the “Destroy Totem” event ended successfully?
As I mentioned above, this is not an issue I’m able to reproduce, so I can’t find the issue. I am looking into it, but I don’t have an ETA.
We’re actively working on it, but without being able to determine HOW it broke, it’s a tricky process. Without a way to reproduce the issue on a test server, I can’t be sure that the fix is good. Also, note that actual “content” updates are on a monthly schedule at the moment, so if an issue isn’t fixed immediately, it doesn’t mean that we don’t know or care about the bug, but we need time to run new fixes through testing before it goes live. (And there is lead time, so anything I fixed right now wouldn’t make it into the January update.) I’m not all bad news, though. I’ve added some safety checks to these events to make them more reliable, but unless I can repro the bug to test my fix, I can’t provide an accurate ETA.
It’s not an issue of the Test sever having different data, it’s not being able to determine how the event got in a bad state. When you expose an event chain to hundreds of thousands of players, one of them might do something you didn’t think was possible and/or didn’t account for. I’ve played this chain dozens of times and haven’t found a way to break it, so I’m just trying to make it as error-proof as I can. In the short term, it sounds like the server resets are at least restarting the chain.
Interesting. I’ll see if I can repro the break Monday. Thanks!
Woot, I think I got it. I found a very tiny window where Brogun could die to a condition in between events, which blocked progress. He’s now immune between events, and it appears to be working again. (I was able to break it reliably, but I can’t now.)
The in-game bugs don’t come directly to me, but they do make their way to me once QA has confirmed the bug. I know I’ve fixed several submitted bugs. Keep in mind that I’m just a content designer, though, so I can’t fix code/art bugs. : )
It’s best if you submit it ingame via a detailed bug report. I get dozens of PMs every day, so I can’t answer them all. (Though I do read them.) I’m currently trying to clear out as many event bugs as possible, though (obviously) many of the fixes I’m working on now won’t hit until the NEXT major content update.
This should be fixed in the next content update. I found a fairly obscure bug where Brogun would stall if he died to a condition immediately after the escort event ended.
So the guy tasked with tracing and fixing the bug doesn’t have a way to inspect the state of the bugged servers? Er… that doesn’t sound very efficient. Do they at least let you use metal cutlery, or are you stuck with a spork?
On the test server I have access to a lot more debug info—it’s not available on the Live servers because it slows things down too much, or it’s disabled to keep people from trying to cheat/hack to get it. (For example, I can’t insta-kill creatures on Live, but I can on Test.) So I will try to get repro steps so I can look at it on a test server, because I can only get limited information on Live.
Thanks, I appreciate it. I know how frustrating it is when things break, but rest assured that we’re doing our best to fix any problems that come up and continue to improve the game.
As mentioned above, I believe I found the issue—Brogun could die to a condition (bleeding, poison) in between events, which prevented him from kicking off the next event. He was immune to direct attack, but not conditions, and it’s fairly rare—you have to kite a mob with bleeding attacks onto him—so we had a heck of a time trying to reproduce the issue. I’ve fixed that, but I don’t have an ETA for when it will be applied to Live, sorry!