Borghild Acid Sigil Bug

My partner and I do Borghild fairly regularly. There's an Acid Sigil that frequently gets stuck in the east wall of the first room. It's not attackable, even with AOEs. But it attacks any player regularly, keeping them in combat and depleting armor, making it very annoying. It's also around a couple crystals, which make them unobtainable because the sigil hits you over and over and interrupts you.

We always put in a bug report, and after a few days, it's usually fixed. But then, a day or two later, it's back. We will continue to put in bug reports every time it's back, but it would be awesome if this could be permanently fixed.

I've heard of that but have never been able to find it. All the spawn spots look valid to me. I need to see it in game or get game coordinates. So if you see it again please stand as close as possible and send an in-game report, which will include coordinates, and a direction from there. Thanks!

PM sent with screenshot link. Also filled out an ingame bug report.

Quote:

---

Originally Posted by Citan

I've heard of that but have never been able to find it. All the spawn spots look valid to me. I need to see it in game or get game coordinates. So if you see it again please stand as close as possible and send an in-game report, which will include coordinates, and a direction from there. Thanks!

---

Thanks for this, Citan. I was in Borghild again this evening and submitted a bug report right at the sigil. Here is an image of it as well. You can see the base of it to the left of the injector bug and to the right for the orange and green crystals.

https://i.imgur.com/GjLcbhj.jpg

The acid sigil in once again stuck in the wall in Borghild. It is slightly to the left now, about where the green crystal is on the above image. I put in yet another bug report in game.

The acid sigil has returned to the same spot in Borghild on the far wall (seen in the screenies above). Thought this got fixed? It looks like it spawns in the room upstairs and falls through the floor/wall below.

Thanks guys, we actually found the bug and corrected it for the next update based on Alopias' post. So it will be fixed in the next update. Thanks!

Thank you for taking care of that!