Official Call of Cthulhu 7th Edition Bug Report Thead

[superteddy57]

Pushed an update to address the errors you were seeing.

[Livius21]

Dit that and it still doesnt work even in a new out of the box campaign. Additioanally I get some error when I drag a chase to combat tracker and it doesnt show. I'm sure it was working a few months ago.Chase.pngcombat tracker.pnglog.png

[superteddy57]

I didn't know it was having trouble in the combat tracker. I focused on the record, please be a bit more elaborate when reporting to help make sure the exact issue is being looked into. I'll look this over when I have a free moment.

[superteddy57]

I'm going to need more time with this. I'm not quite understanding what was being done from the previous developers and need to work through it a bit more.

[superteddy57]

Dit that and it still doesnt work even in a new out of the box campaign. Additioanally I get some error when I drag a chase to combat tracker and it doesnt show. I'm sure it was working a few months ago.Chase.pngcombat tracker.pnglog.png

I'm in need of knowing how data is supposed to be laid out for the chase feature. Can you post a link of your zipped up campaign so I can do some testing with my changes?

[sedgetone]

There’s a video that may help with you understanding how chases work.

[superteddy57]

Thanks! it's not the process of the chase, but how the data is stored and saved in the campaign. Don't want to break chases in action if I don't use the same node names.

[Livius21]

So I'm not the only one experiencing this problem?
Like I said before the chase editor is broken. The hazards were showing in the small footprint graphic at top of window. There is also the remove (-) button for hazard that has now disappeared. Chase not adding to combat tracker is also another problem. Just try to replicate what the video is showing. If it can help, I have bought Fantasy ground and Cthulhu module in may 2025 and it was all working at this time so I'm guessing that some patch done after this is causing the problem. Many thanks for your help

[Livius21]

Heres my zipped out of the box campaign.
thanks

[Sinnerman]

(2nd attempt at posting, 1st one seems to have been lost)

Hello,
I've some problems with skills in character creation:

1 - "Fighting (Brawl)", "Lang - Own" and "Credit Rating" are marked as professional skills even before chosing a profession. It's not possible to add a sublabel to "Lang - Own". IMPORTANT NOTE: this seems to be fixed in the update I downloaded today: only "Credit Rating" is always marked as professional skill, and the sublabel of "Lang - Own" is again editable.
2 - If an occupation has a choice of a skill with fixed sublabel (ex. Entertainer with Art/Craft (Acting)) the skill is NOT added to the skill after occupation selection.
3 - "Lang - Own" base value is no longer calculated on the INT of the character but is always a NULL value.
4 - Skills marked as [UNCOMMON] always appear in the skill list.
5 - It's impossibile to mark/unmark a skill as occupational (if I try to fix point 2 by manually adding Art/Craft (Acting) to the list I can't then mark it as occupational)
6 - it's impossible to remove a skill from the list unless it has been added with one of the buttons atop the list. (can't remove UNCOMMON skill manually)
7 - If a profession has "Lang - Own" as occupational skill, the skill doesn't get marked as occupational nor the sublabel selected is added after been chosen in the occupation mask. NOTE: This changed in my last update, before that a second line with the correct sublabel was added to the list in addition to the fixed one with the uneditable sublabel (still a bug probably, but different). Still the base value is not correctly calculated.
8 - Pretty much the same of point 7 happens with Fighting (Brawl): the already present line in the list doen't get update with the occupational mark if the occupation you choose has it as occupational skill.

I've tested everything on a newly created campaign with only References, Base Manual & Investigator Manual loaded.
I'm pretty sure that none of this beahavior was present some weeks ago, but not really sure when the changes happened with the exception of point 7 that changed with the update I downloaded today.

Thanks