[3.0.1] A Bigger Fish - is the invisible Rautai Royal Weathermage a bug?

[bringingyouthefuture]

So ... A Bigger Fish I am fighting to clean out the Raitai sailors - Shrimp and his crew - but annoying there is an invisible Royal Weathermage in the corner - he/she will take AOE damage but is non-targetable.  Just wondering if feature or bug.  I can send a save if necessary.

Edited October 7, 2018 by aaronghowell

[TheWeaver]

That has been there since release I think -- I've always thought it was intentional and that she may be a spirit following Shrimp (who seems to have proto-watcher powers).  Not sure if the fact you can't directly target her is intentional or not, but that's always been true for me as well.

 

You get some other clues in different dialog choices:

 

 

 

Shrimp can see/sense Iselmyr.

If you use the "there is a ghost" route you actually think you feel one pass you at the end.

 

 

[whimper]

I’ve encountered this problem too. I’m pretty confident that it’s a bug, not intentional.

[bringingyouthefuture]

Hmm, not sure it is a bug, I think it is just too make the challenge tougher,

[TheWeaver]

That's what I always assumed.  As it is, it is really just a minor annoyance (though the very first time I did the fight it did confuse the heck out of me).

[SChin]

Hey everyone,

 

From my understanding, there is a bug here.  I put a report together for it from a previous post and it is on Area Design and Programming for a fix.  After reading some other forum posts about this, it sounds like a Fog of War issue, and I've read that you can move away from the NPC to kite them out and then see them to kill them.

 

Thank you for posting bugs and sorry for the inconvenience this may have caused during your playthroughs.

[Belfaldurnik]

As 3.1.0 beta doesn't fix it yet, I'd like to confirm that withdrawing to the wooden staircase causes the Royal Weathermage to follow, and then he will be targetable.

Edited October 26, 2018 by Belfaldurnik

[SChin]

Hey everyone,

 

This one didn't make it in time for the 3.1.0 patch, but it is slated to be fixed in the future.

 

Sorry for the length of time the fix is taking.