Legacy of the Rose interaction - bug? @GGG

TL:DR Cast speed and costs aren't treated equally with the staff, buyers beware.

There are a few issues with this weapon, which are so sadly overlooked. The ES spent doesn't work with the new Bladefall of Trarthus gem, even when paired with the new amulet Whispers of Infinity, which seems to be able to work with every other skill available to force an ES cost. Also, the bastard child of Inquisitor, Fanatacism, doesn't work, which is a huge shame as the wording specifically says "Reduces cost by 75%" but doesn't stipulate mana, ES, memories, etc and it absolutely should work based off the wording. The cast speed for Devestation, Ire and Despair all suggest it should be increased to ~250%, but it doesn't seem to cast any faster than normal. I have screen recorded a frame by frame and even though it says that the cast time is more than halved, it doesn't actually summon shaper or allow him to preform his actions any faster than normal. This weapon, with its scaling, would be an incredibly fun addition to the game if the interactions followed normal wording behavior and patterns of other skills.

Dear GGG, I'd also like to report that the summoning of the shaper can bug, resulting in no more memories able to be earned, despite how much ES is spent. This issue bricks the map, yielding a really unfortunately playstyle. I have dumped every divine I have into this build and it has so much potential, but now I am questioning if this was a huge mistake due to the fact that half of my maps are bricking due to a faulty interaction with the summoning. I know this isn't a huge deal, nor something that you probably think requires any attention, but I am really loving this staff and want to use it. Please help!!!!!

I am having the same problem. It seems like you have to stay with Shaper until he has finished casting his spell to be able to gain Remembrance charges again. If I go back to Shaper after leaving him casting, the spell (Ire) will resume casting like it pauses while i am a screen away. Seems like a bug for sure.