June 8, between 7pm-8pm UTC, Guild Bounty 3 originated on Yak’s Bend.
IP 192 No Barrells. Scallywag was near Provern Shore Way Point, stuck Invlunerable/Bubble and belching, no one could attack/interact. Bounty 3 failed.
Started new Bounty 3, got Scallywag again. Members tried porting in/out to get a different megaserver. Got IP 194 (near different WP) Scallywag spawns but no one can interact with him. Bounty 3 failed.
Started 3rd Bounty 3, got Scallywag for third time. Most members get IP 192/194. One finally got a new megaserver (originating from Blackgate) and Scallywag could be completed. Bounty 3 success.
Yes! I’ve had this happen 4 times this week. The first was Friday night, and then it happened again to our guild twice in a row tonight with Guild Bounty Training Missions, and one Tier 3 guild bounty.
All told, that’s about 900 or so influence down the toilet, plus nine days’ worth of build queue, and 45 minutes of us standing around and waiting to try again, hoping for something besides Sottz this time.
It’s really frustrating for our small guild. We didn’t expect to finish the Tier 3, but the three training missions were important to us. What a waste.
Attachments:
“It is the stupidest children who are the most childish
and the stupidest grown-ups who are the most grown-up.”
- C. S. Lewis
Reporting in that this was still bugged on Saturday June 14th. Maybe they were a little careless when they removed npcs from Vigil keep, but seems to be an ongoing problem.
