Candidum and Hekaru sometimes do not drop loot/are un-lootable when they do drop

Bug Name:

Hekaru sometimes do not drop loot/are un-lootable when they do drop
​

Bug Description:

Item: Hekaru (sea monster)

What is supposed to do: Drop loot / loot can be picked up by pets

What happens: NOTHING happens. Hekaru drops, but player is unable to loot even though there is the glowing loot bubble/light on the corpse showing that there IS loot. Swimming or sailing slowly right over the sea monster corpse does nothing, and it finally despawns after awhile with no loot for the player. Sometimes Hekaru does not drop loot at all.
​

How to reproduce/proof:

Attempt to kill Hekaru with an Epheria Sailboat/Frigate using Q (Ram) or with cannons


(post edited to reflect changes)​

 

True, i had same problem yesterday at EU server.

 

This has happened every time I killed a Hekaru, four times in a row now. No loot at all, not even Neidans (which are pretty much guaranteed every time) and trash loot (Hekaru spikes).
And yes I had pets out, they were fed. I even went down right on top of the corpse, but there wasn't any loot bubble right from the start.
Candidums are just fine now, they drop loot. But Hekarus remain bugged for me.

@Kolka would you look into this possible bug please? Thank you

https://imgur.com/a/psXGY4k

 

Yea it happened to me. I have an another problem too. Can you see them from far away ? or is just me ? I can see them when i found them by luck they appears

 

Vision range of your character (not mini map) for sea monsters is very limited. I can only see them if they're close by my boat. Vision improves when you're on the mast.

Also, just killed another Hekaru - no drops once again. How am I going to get Hekaru Spikes then? To craft cannons?

 

Yea i wonder . What you by ''Vision improves when you're on the mast'' ? Do i need to change my vision options ?

 

No, you just have a wider view when you're on the mast that's all

 

I know i am sailing on retail game but i cant see them far away...

 

@Lareldal @Noyah Could this be looked into please? Me and others are still encountering this problem, and we're not even sure if it's intended feature or a bug. Thank you!

 

Fixed