Hi everyone. We haven’t had this problem so we can’t be sure, but we’ve deployed a potential fix for this issue in 0.7.7e. Please let us know (with the relevant files) if this happens again after you have the update.

Thank you!

I don’t recall if users can move threads, but it’s done by clicking the edit button (pencil) next to the thread’s title. I’ve moved it.

It sounds like you’re on standalone-- the fix for this will be out as soon as possible. Apologies for that!

Hey everyone! We’ve corrected the issues with 0.7.7e and it is now being released. It’s currently live on Steam and will come to the standalone client as soon as possible.

There are several steps in our internal testing for new releases, and the game was working as expected during that process. However, a problem was introduced in the final version that was distributed to players, which was not caught. We will improve our internal processes to avoid this mistake in the future. Thank you for your patience.

Skills

Due to some oversights, Spriggan Form builds in 0.7.7 were able to get far more totems active at once than we intended. In addition to addressing the root cause of this, we’ve made some changes to Spriggan Form and the totems in question.
 

Spriggan Form

• Summon Healing Totem no longer has a cooldown by default.
• Summon Vines no longer has a cooldown.
• Nodes that affect Healing Totems (such as Spiked Totem) now only affect Healing Totems created by the Summon Healing Totem skill, and say so on their tooltips.
• Spiked Totem now causes Healing Totems to have the same mana cost, cooldown, and totem limit as Thorn Totem.
  • This is a separate limit, so with this node you can have 2 Healing Totems and 2 Thorn Totems by default.
• Added a new node behind Spiked Totem that increases your maximum number of Healing Totems and causes you to always summon 3 Healing Totems at once.
• ...

Could you post a screenshot of your Quest Journal? (opened using J). Make sure you’ve talked to all the NPCs in the Outcast Camp if you haven’t already, characters with a “!” above their head have a new quest.

We have a hotkey for disabling the UI, which is set to the “delete” key. I suspect it was pressed by accident, as I don’t see anything out of the ordinary in your log file. You can rebind that key if it will cause issues in future.

Thanks for the report! We’re still looking into this issue, but for most users restarting the game resolves the problem.

I’ve attempted to reproduce this issue for some time but have not been able to yet. Could you post a log file if it happens again? Sorry for the trouble!

This will be fixed in 0.7.7e. Thanks for the reports!

It doesn’t ramp up as quickly if you never enter Reaper Form? That’s certainly odd, but I didn’t understand that was the case from your initial post.

I’d have to see screenshots from all your trees, passives, and uniques before I can look into this but I assume you have the Icarian Poison node, which is supposed to ramp up how quickly poison (or in this case armor shred) is applied.

There’s additionally a bug that is causing Aura of Decay to apply ailments (poison/armor shred) too quickly. This will be resolved in 0.7.7e.

That’s also intended, it’s a random chance. I don’t think making the names persistent is planned but it could happen in the future.

Screenshots of this happening (after enemies are dead is fine) would be very helpful then, including the name of the level. Thanks!

These are normally easy to fix, but we do need to see a picture to be able to fix it unfortunately.

We don’t allow uploading images to the forum, but you can upload it to somewhere like imgur.com (which doesn’t require an account) and then post the link to it here. Thanks!

This will be fixed in 0.7.7e, sorry about that! Specifically the problem is with “tagged” leech stats, such as “spell damage leeched as health”. If a source of leech applies to all types of damage it should be working fine.

Sorry about this! We’re still investigating this problem. For now, restarting the game should resolve it.

This is a known issue, we’re working on a fix. Thanks for the report!

This is a known issue, we’re working on a fix. For now restarting the game should solve it. Thanks!

This is working as intended (even when your Wolf is named Wilf). Thanks!