Original Post — Direct link
Since the introduction of Skill Styling in Update 42, the only playstyle which could not utilize the initial batch of Skill Styles was Werewolf, because none were made for the Werewolf skill line. Now, we're getting a brand new Skill Style for Roar, which is said to be colored green. It will be available via a fragment chase or alternatively purchasable with Archival Fortunes. This is huge news for Werewolf players. Finally there is a way to interact with the Skill Styling system. Although I can't say any of us expected to be able to color the visual effects of Roar to a green color (what exactly would that recolor — the emanated sound waves or the saliva that splashes everywhere?) what I hope is that this is only the first of many new Skill Styles for the Werewolf skill line. Maybe we'll even get some for Werewolf Transformation itself some day! Here is a clip from the Update 43 preview stream where the upcoming 6 Skill Styles are discussed: https://clips.twitch.tv/TrustworthySmoggySandpiperM4xHeh-9DfTeqMTJGr4Tgrg
8 months ago - ZOS_Kevin - Direct link
We chatted with the team yesterday and there is a bug in for this notification issue happening with some skills and collectibles. The team is working on a fix now and we'll update when a fix is set. tomofhyrule;c-8172519
Tommy_The_Gun;c-8172507
I have unlocked it, but the weird thing is that every-time I login, it says: "Skill Styles has been updated with the Roar, Verdant Green collectible." It happens EVERY TIME I login into the game. I am not sure if this is a UI bug, or the game tries to re-add something I already have in my collectibles. It does not matter on what character I login. The 1st time I login into the game I have this notification. Add-ons do not seem to affect this, as even without add-ons it still shows up every time. And it is only this skill style. Does any one experience same thing, or is it just me ?
That's evidently a UI bug. It happens for all six of the new Skill Styles and the new Hroldan Hammer custom action as well. I've submitted it as a /bug, and I know others have as well. Hopefully it'll be fixed in an incremental.