Sigil of Karka Slaying Recipe

[GoldenTiger.4706]

As can be seen ingame, karka incorrectly drop the recipe for Sigils of Grawl Slaying as opposed to Sigils of Karka Slaying, the latter of which are now only available from the Trading Post. Unlike most NPCs, karka also drop the Sigil of Grawl Slaying recipe after it is unlocked.

[Inculpatus cedo.9234]

Removed from the game 5 years ago.  

[GoldenTiger.4706]

Despite that, they can be seen on the Trading Post, and karka still drop grawl sigils to my knowledge. At the very least, them dropping Grawl Sigils is a bug.

[Inculpatus cedo.9234]

Yes, many items no longer available (through in-game means) are found on the Trading Post. 

[GoldenTiger.4706]

Still, it has a purpose, it's useful, most likely was originally intended to be dropped from karka. It's not like there's no reason to make it available again.

[Inculpatus cedo.9234]

Doesn't say they ever dropped from Karkas.   The Sigils were only extracted from gear that contained them. 

[MithranArkanere.8957]

On 9/17/2021 at 6:50 PM, Inculpatus cedo.9234 said:

Doesn't say they ever dropped from Karkas.   The Sigils were only extracted from gear that contained them. 

When sigils were reworked, new account bound recipes were created for the slaying sigils. 

These recipes are dropped by those types of enemies. 

When you learn one of those recipes, the related enemy stops dropping them. 

 

There wasn't a recipe for grawl slaying until it was created for this update..

 

Karka are clearly not grawl, but they keep dropping the recipe of grawl slaying after it has been learned.  That recipe should not keep dropping once learned, yet karka keep dropping it.

 

This can only mean once thing: karka were meant to drop the recipe of karka slaying and stop when you unlock the recipe. But since they do not drop the recipe of karka slaying, you can't learn it to make them stop dropping it, so they keep producing the grawl recipe because their drop table has not been set properly.

This bug has been reported shortly after the update, but it has never been addressed.

And it still happens as of this day.