I've been noticing some intermittent issues with unpacking the Saw character specifically. Sometimes, but not always, the game gets confused between the Saw's disused attack mods and the health packs that are stacked with them - and ends up shuffling all the attack mods together. I've taken to saving as an object both the used and disused attack mods, so I can respawn them when this bug happens. My guess is that it's something timing related, because it happens most often when the mod is doing several things at once (like opening multiple boxes simultaneously).

Holy Strike card is somehow bugged out, when someone attempts to interact with the card you get an error and everything just goes to hell after that (card wise that is)

Not sure if this is TTS v13.0 issue or not, but hitting the Open Envelope button on Envelope D in Forgotten Circles appears to just delete everything from inside the envelope and then hitting it again causes a script error.

If the items inside are manually removed then most of its contents can be handled manually but I'm not sure how much scripting is supposed to do for us.

Never mind, figured out the above.

If someone lands here from google, without being too spoilery make sure to open envelope D before attempting to start scenario 115.

monsters are being placed with no data on the token, I have to select Elite or Normal to get the info to populate. Most spawn with their token number (the number to left of health) as 1. Multiple 1s, in other word

@QuesoBlanco
this is already fixed. you are probably not on the newest version. and for the stats you have to spawn the monster with the monster spawner not grab from bag to kick in the script. or you click elite normal button^^

@Kijan, is there a fix underway for the monster bag, or is it something that you guys are unable to fix? Regardless, great work from all you guys.

Yeah for me it's still showing up as 1 whenever a monster is spawned.

Is there a way to make the mod update to the latest version, and since I'm mid campaign, am I going to have to do anything like remake the characters and world state in a new save instance?

Publicado originalmente por Kaal:

I've been noticing some intermittent issues with unpacking the Saw character specifically. Sometimes, but not always, the game gets confused between the Saw's disused attack mods and the health packs that are stacked with them - and ends up shuffling all the attack mods together. I've taken to saving as an object both the used and disused attack mods, so I can respawn them when this bug happens. My guess is that it's something timing related, because it happens most often when the mod is doing several things at once (like opening multiple boxes simultaneously).

I've seen this as well. It's the medical cards doing it for sure, another character was packed away with one by mistake and the same thing happened to their box.

I put the medical cards into a bag before I pack them away as a result

Most of the mod is contained within the save file, so updating an existing campaign must involve creating a new game and recreating it. Some but not all of the elements (like items or road events) can simply be ported over, while others (like characters) will need to be made anew. There's a discussion thread posted that describes how best to do it - basically I just save everything as one big object, bring it into a freshly-made game, and go through it all.

I get an error every time I try the scenario complete/scenario lost buttons in the game manager (across multiple instances). It results in no post scenario automation. --this only started in the last month or so.

Error is: Error in Script (Global) function<spawnerClicked>:chunk_3:(806, 18-75): attempt to index a nil value

Publicado originalmente por esmalin:

I get an error every time I try the scenario complete/scenario lost buttons in the game manager (across multiple instances). It results in no post scenario automation. --this only started in the last month or so.

Can you test if it related to one of the player characters? Do you get the error in a fresh new game?

Publicado originalmente por ckraucun:

Can you test if it related to one of the player characters? Do you get the error in a fresh new game?

Not the OP, but same error.

Tested in a new game and error did not re-occur.

Went back to original game and discovered that one character (Triangles) couldn't be removed via the Remove Player button- it cleared the mat but left the components. Manually deleted everything, re-built character and that fixed the error.

Not sure what's going on there.

Publicado originalmente por ckraucun:

Can you test if it related to one of the player characters? Do you get the error in a fresh new game?

@ckraucun
@DocBosch

Thanks for the solution. Removing and rebuilding the Sunkeeper took care of the problem.

Now I think I found the cause: the Sun Keeper player had his character sheet up next to his player mat. Putting the sheet back where it originally spawns fixes the problem. So any objects that need to be updated seem to need to stay in a certain field--anywhere directly below the player mat, I think..

Publicado originalmente por esmalin:

Publicado originalmente por ckraucun:

Can you test if it related to one of the player characters? Do you get the error in a fresh new game?

@ckraucun
@DocBosch

Thanks for the solution. Removing and rebuilding the Sunkeeper took care of the problem.

Now I think I found the cause: the Sun Keeper player had his character sheet up next to his player mat. Putting the sheet back where it originally spawns fixes the problem. So any objects that need to be updated seem to need to stay in a certain field--anywhere directly below the player mat, I think..

Character sheet had been moved alongside mat for our problem character as well.