Using latest version from CF

Issue does not exist anymore.

Theres' nothing I can do about it, other than rolling back the incoming changes to the UI (which introduced ACE libraries and extra events - where the error occurs).

And that I will do ...

Thanks for the report.

Hmm, couldn't that specific function just have a combat lockdown check / 'if not unitaffectingcombat("player") in it? I actually tried to find a reference to that in the main lua block but couldn't then started lookijg through the Ace subfolder and still couldn't find it so figured it was some dynamic thing that got passed over to the client? I dunno.

It could if it was inside Thaliz' itself. But it is not. I suspect it is some of the Ace code being triggered by an event. The Thaliz code itself is not called.

There are some other problems reported with Thaliz interfering with other addons, so for now I don't see any other solution than to revert to the older solution which doesnt use Ace3. I don't have much knowledge of the Ace3 library, but it must have been hooked up wrong in some way.

Hi @lvangh and thanks for reporting this error.

I did the migration of some code to the Ace3 framework and I am sorry about the error you have.
According to this post on the Ace3 forum, the error does not seem related to the framework itself.

I will investigate further, but as I did not encoutered this error, could you please give me more details about the situation you were involved in? Like the game client you have, the actions you were doing before the error occurs...