(edited by shintenhouji.4703)
[Bug] Coiled Watch event chain is stuck
Currently on Frostgorge Sound, the Coiled Watch event chain is stuck, whew the dolyaks delivering the bombs does not move.
Wait until after the Clawr of Jormag shows up; typically, you’ll see a bunch of new maps created and the event chains will be up & running properly.
PS for future reference, use the in-game command /ip to find the instance number and include that in bug reports about stalled events/event chains. (The in-game /bug report tool works just as well for that, too; it automatically includes the IP address.)
John Smith: “you should kill monsters, because killing monsters is awesome.”
Currently on Frostgorge Sound, the Coiled Watch event chain is stuck, whew the dolyaks delivering the bombs does not move.
Wait until after the Clawr of Jormag shows up; typically, you’ll see a bunch of new maps created and the event chains will be up & running properly.
PS for future reference, use the in-game command /ip to find the instance number and include that in bug reports about stalled events/event chains. (The in-game /bug report tool works just as well for that, too; it automatically includes the IP address.)
thanks for the tip!
Just finished Claw of Jormag event, and the event is still bugged.
P.S: Edited the original post to included the IP Address.
I was just at this event and it’s still stuck. Living World S2 step is in the same place too and neither progress.
Just finished Claw of Jormag event, and the event is still bugged.
P.S: Edited the original post to included the IP Address.
Sorry, I should have been more clear: you want to join the map after the event has been over (so maybe 30 min after spawn) to make sure you end up on a new version of the map. You can use the /ip command to make sure you’re on a different one.
I’m 99% sure that the problem is your specific instance(s). That’s because the Coiled event chain was working fine for most instances as of at least 3 weeks ago, because that’s when a lot of people farm it (for the map bonus rewards); ‘coil’ is a big part of that farm. The only updates during that time seem unlikely to have changed anything for the map or events generally.
Of course, stranger things have happened, so keep reporting what you find.
John Smith: “you should kill monsters, because killing monsters is awesome.”
Just finished Claw of Jormag event, and the event is still bugged.
P.S: Edited the original post to included the IP Address.
Sorry, I should have been more clear: you want to join the map after the event has been over (so maybe 30 min after spawn) to make sure you end up on a new version of the map. You can use the /ip command to make sure you’re on a different one.
I’m 99% sure that the problem is your specific instance(s). That’s because the Coiled event chain was working fine for most instances as of at least 3 weeks ago, because that’s when a lot of people farm it (for the map bonus rewards); ‘coil’ is a big part of that farm. The only updates during that time seem unlikely to have changed anything for the map or events generally.
Of course, stranger things have happened, so keep reporting what you find.
No worries, I may have subconciously thought about it, went to a different map, then back to frostgorge. Unfortunately, the IP didn’t change. And didn’t change even after several hours.
Checking back it though, the event is now working. Seems to have reset the instance after the dailies reset.
Checking back it though, the event is now working. Seems to have reset the instance after the dailies reset.
Glad to hear it.
Some zones don’t have much turnover for /ip addresses; Frostgorge, fortunately, turns over a few times a day, so the events always get restarted at some point.
John Smith: “you should kill monsters, because killing monsters is awesome.”
FWIW, y’all, ANet run many map shards on a single server, and `/ip` is not a unique identifier for which map you are on. (Though it is usually unique, it’s not guarunteed.)
You should certainly file a bug in-game, with “blocking progress” ticked, through the “no response to this sort of bug report” interface as well. (Including the IP here is good, it’s just not got all the extra details that internal bug report would make available to anet.)
FWIW, y’all, ANet run many map shards on a single server, and `/ip` is not a unique identifier for which map you are on. (Though it is usually unique, it’s not guarunteed.)
For our purposes in advising people, it’s close-enough-to-true. (Since I’ve learned that multiple instances can use the same IP, I have yet to actually encounter an example of it. Consequently, I tend not to mention it.)
John Smith: “you should kill monsters, because killing monsters is awesome.”