5 months ago - FatsharkLev - Direct link

Hmm, were you possibly downed when the Grudge Marked monsters were defeated?

Also, did you successfully complete the level?

Being downed, or not beating the level could cause the progress not to count.

5 months ago - FatsharkLev - Direct link

Ah okay! I can ask one of our backend developers to take a look in case something is awry.

Could you please provide me with your Steam profile URL (e.g. https://steamcommunity.com/id/FatsharkLev/) and your console log from the recent session that you defeated the 2 chaos spawns?

You should be able to identify the correct log via the time/date stamps in the filename. You can find your console logs here:

  1. Press the Windows key + R
  2. Enter %appdata% within the search input and select ‘OK’
  3. Navigate to AppData\Roaming\Fatshark\Vermintide 2\console_logs
  4. Locate the console log that corresponds with the session in which the issue occurred, by looking at the timestamps in the log names
  5. Upload the appropriate console log to us

Thanks!

5 months ago - FatsharkLev - Direct link

No problem! You should be able to attach and upload the single log file from the relevant session to a comment here.

5 months ago - FatsharkLev - Direct link

Perfect, thanks!

I’ve requested for one of our backend developers to take a look at your console log and account.

I’ll be back in touch as soon as I have any updates! :slight_smile:

5 months ago - FatsharkLev - Direct link

Hi @SOULLESS,

Apologies - it’s been a busy period and I’m stil awaiting a response from our backend developers. I’ve given them another nudge and I hope they’ll be able to take a look at this soon.

Thank you for your patience.

5 months ago - FatsharkLev - Direct link

Ah okay! :frowning: I’ve passed this log on to our backend developer also.

5 months ago - FatsharkLev - Direct link

@SOULLESS, thanks again for your patience. The challenges for Zealot and Mercenary should now be completed and claimable for you.

We’re unsure why these kills weren’t tracking correctly, but we’ll look into it to see if there’s an underlying issue we need to fix.