Nexus Clash

https://nexusclash.com/clash.php?op=character&id=12804

When I attempt to buyback TEM EYES on this character, I get sent back to the skill purchase screen with no message, but I do get a button to return to the game.
When I return to the game the buyback has not initiated.

You need the premium version of Nexus Clash to be able to play without Tem Shop ads, sorry.

This happened to me with a renamed version of a spell, too. I ended up fixing it by renaming it to its original variant, and then the buyback went through fine.

The consequence was that everyone in the Nexus who owned the spell received a notification I had done this, and a duplicate appeared in our inventories. But both went away when I completed the buyback. YMMV.

Haweh wrote: ↑Wed Jul 06, 2022 11:09 pm https://nexusclash.com/clash.php?op=character&id=12804

When I attempt to buyback TEM EYES on this character, I get sent back to the skill purchase screen with no message, but I do get a button to return to the game.

welp.PNG

When I return to the game the buyback has not initiated.

werlp.PNG

Try using the new reset spell button in the credit store to reset the spell to the base spell and then try the buyback. If there are issues, with the reset, get in touch with me through Discord please and thank you.

Leila wrote: ↑Thu Jul 07, 2022 1:31 am This happened to me with a renamed version of a spell, too. I ended up fixing it by renaming it to its original variant, and then the buyback went through fine.

The consequence was that everyone in the Nexus who owned the spell received a notification I had done this, and a duplicate appeared in our inventories. But both went away when I completed the buyback. YMMV.

Exactly this is what actually caused issues where a duplicate spell was created for everyone with the original spell. There is a new credit store button that will reset your custom spell to the base spell. Please use the button and do not attempt to rename the spell to the original spell name manually!

The new button appears to work. Thanks plscks!

There's a pending fix for the underlying issue here.