Offset Mismatch: BloodshardCount

[kbrebel04]

ZetaDia.PlayerData.BloodshardCount is returning -1. This is causing basically anything using Trinity (aka all) stop working as soon as people fill up on blood shards(which is something that takes me about 30 mins).

Again, seems the API ZetaDia.PlayerData.BloodshardCount is not returning the correct value in Demonbuddy, may need to fix that offset, Demonbuddy basically can not AFK for anyone right now, since it bugs out trying to collect blood shards that it has no room for.

 

[Misa]

ZetaDia.PlayerData.BloodshardCount is returning -1. This is causing basically anything using Trinity (aka all) stop working as soon as people fill up on blood shards(which is something that takes me about 30 mins).

Again, seems the API ZetaDia.PlayerData.BloodshardCount is not returning the correct value in Demonbuddy, may need to fix that offset, Demonbuddy basically can not AFK for anyone right now, since it bugs out trying to collect blood shards that it has no room for.

Your bot should keep running, just won't pick up the spare shards. I've had mine on for a few hours and I've only cleared shards about twice in between and it's been fine, just a huge waste.

 

[Tony]

fixed in next release

 

[kbrebel04]

Your bot should keep running, just won't pick up the spare shards. I've had mine on for a few hours and I've only cleared shards about twice in between and it's been fine, just a huge waste.

It does not. Even with Blood Shards disabled it will sit by the pile of Blood Shards that it cant hold, indefinitely.

fixed in next release

Thank you for the notification, Tony. Will this be soon today?