PDA

View Full Version : Combat Tracker Errors after new update



pralix1138
February 17th, 2021, 16:48
First off, I love the new update. However, I am now getting errors when I open the Combat Tracker on the Call of Cthulhu 7e ruleset for the first time in a session. The error is:
"[ERROR] Script execution error: [string "scripts/manager_actor2.lua"]:32: attempt to compare string with number"
Screenshot for clarity: 43839

This does not affect my VtM5 ruleset.

Any help would be appreciated. Thanks!

Trenloe
February 17th, 2021, 16:54
I can recreate the issue. Hopefully the devs will get a fix out ASAP.

superteddy57
February 17th, 2021, 17:45
Thank you for the report. Found the issue. An update will be incoming.

Jiminimonka
February 17th, 2021, 18:40
It is fixed now. Just click that Update button :)

pralix1138
February 17th, 2021, 18:43
The new update seems to have done the trick. Thanks so much for the quick fix, folks!

ClankyBlue
February 17th, 2021, 19:01
Can confirm that hotfix solved the issue. Thanks so much for the hard work!

Dave0910
September 24th, 2021, 21:25
I started having this problem, yesterday, after updating. It happens in a ruleset that I'm building. Apparently the parameters were changed for the DB.getValue(). Where it was previously set with a data type of "number", the actual value was changed to "number". I simply removed the third parameter with no problem, but why would the function be changed when it affects every ruleset?

superteddy57
September 24th, 2021, 21:33
This depends on the script error you are receiving and the code for your ruleset. In some cases you might have to convert a string number to an actual number. Without seeing your code and the error these can only be speculative answers. The third parameter is the default that is returned if the function can't find the node in question. So if you set it as "" it will return an empty string. If it's set to 0 then the number 0 is returned. Omitting it will return nil. Which would remove that said error.

Dave0910
September 24th, 2021, 22:13
Sorry, I didn’t see the new thread, for this. The issue was already fixed.