PDA

View Full Version : Combat Tracker - Stack Overflow error



Tabarkus
August 25th, 2022, 23:32
My players are getting an error anytime I add PCs or NPCs to the Combat Tracker, including when the player first opens the combat tracker after logging in. This bug showed up with the 8/15 update.
The error repeats itself for the number of PCs and NPCs on the CT.

The error is: [ERROR] Script execution error: [string "ct/scripts/clientct_entry.lua"]:12: stack overflow

This error is reproduceable with no extensions loaded.
The error occurs only when I am using the DCC RPG ruleset. It does not occur in my D&D 5e game.
The Community Developer does not see a cause for the issue and no other's in the DCC community are reporting the issue.

See attached logs, if needed, from both the GMs system and a Player's system.

GM's system:
OS Windows 11 Home
Processor AMD Ryzen 7 3700X 8-Core Processor 3.59 GHz
RAM 16.0 GB
VIDEO: NVIDIA GeForce RTX 2060 SUPER 8 GB

Zacchaeus
August 26th, 2022, 00:40
If no one else is seeing this then something is off on your end by the sound of it. Try deleting the ruleset from the rulesets folder (or the vault if that is where it is) and then updating FGU. Make sure you don’t have any folders in your ruleset folder; if there are delete them as well.

Double check that you can repeat the error in a new campaign without any extensions (including themes).

Tabarkus
August 26th, 2022, 00:43
Will do, thanks for the suggestion.

Tabarkus
August 26th, 2022, 01:09
I am unfamiliar with deleting rulesets. The DCC ruleset is not in the ruleset folder. The Vault folder contains 35 .dat files associated with Goodman Games, the DCC publisher, but nothing specifically labeled DCC ruleset. I assume one of those .dat files is the ruleset, likely the largest one. If this is correct the Community Developer could direct me to the proper file.

Oh, and the error persists in a brand new campaign.

Moon Wizard
August 26th, 2022, 01:32
Answered in the DCC bug thread. Please run a new Check for Updates, as a hot fix got lost in the shuffle and has now been pushed to the patch system.

Regards,
JPG

Tabarkus
August 26th, 2022, 01:54
Yep, that fixed it. Thanks for the quick responses!