Plasteel getting partially refunded

Issue Description:
This is my first bug report so please be kind, I’ll do my best to help find a solution and provide evidence where I can. I noticed that this is reliably replicable for me in the last 48 hours

To summarise; when I upgrade something with Hadron, be it through consecration, blessing or perk swapping If I immediately swap from the character who I just completed a mission (Doing a mission first may be irrelevant to recreation) with to a different one the plasteel I just spent has been partially refunded back to my account.

(After further testing I can conclude it does not require a mission be played first)

Steps to Reproduce:

I haven’t been able to find a report or topic mentioning this so I’m unsure if this is a unique or incredibly rare issue.

I’m levelling my Ogryn, I play a mission, any mission. Doesn’t matter if we win or not. All that matters is to pick up plasteel beforehand. Once this happens, after the mission ends I either immediately go to Hadron and consecrate/re-bless. Then exit back out of the forge before using the escape menu to return to character selection. At this point the number displayed for plasteel is the same as what It was after deductions from hadron. However, once I load up another character this changes. I’ve been refunded hundreds of plasteel. I haven’t observed if diamantine also does this but I suspect so.

This can proc multiple times between runs. So far I’ve been able to observe this occurring a maximum of 3 times between runs, netting between 750-1500 plasteel returns, its as if the game thinks its charging me full price but my suspicion is from the figures I remember being refunded relative to what I had beforehand that the game is actually charging me for a base tier 1 consecration/blessing or perk swap. Costing me around 160-190ish in reality despite the fact I’m consecrating to tier 4 or equivalent blessing/perk

Platform:
Steam

Player ID:

C.G.Kitten

Approx. Time of Issue & Timezone:

Earliest notice being around 10pm GMT 02/09/2023

Reproduction Rate:
Constant (100%)

Edit I’d like to add that I was only doing one upgrade before swapping character and back which may or may not be important. I’m not sure but I thought it worth noting when I remembered this fact.

I have been able to consistently reproduce this after every match I have played in the last 24hours at least once after each mission. Even after multiple restarts.

Upload Supporting Evidence:

Upload Console Log & darktide_launcher.log:

darktide_launcher.log (571.4 KB)

console-2023-09-04-00.02.27-b1b773cc-3c6b-4844-bb2b-e9cb0bc81407.log (937.0 KB)

We’re checking it out. Thank you for your detailed report! :slight_smile:

Thank you for responding :slight_smile:

Truthfully you can thank [

Jorgamundr

](Twitch) I was unsure at first who to message or contact, I opened twitch and saw Jorgamundr streaming and he helped direct me to here and gave me the confidence to make an account to report this issue.

His last stream vod, at around the 3:29:25 mark was when I started asking for help as he was the person with the highest number of viewers on Darktide at that time. He was incredibly reassuring and directed me to report it in as much detail as possible as I was worried that It could get my account flagged for cheats.

Honestly, give this bug a suit, this deserves to be a feature :wink:

At least until a proper crafting rework has been implemented…

5 Likes

True and real!

2 Likes

I just noticed a similar (potentially the same) issue. I had been grinding plasteel on my psyker to upgrade gear on my ogryn. I had about 5000 that I spent last night right before logging off. I logged on today and had around 4500 plasteel. I was able to spend all the plasteel on upgrades, do 1 mission and had 4100 plasteel.

I am using several mods from Nexus so I have included my mod load order along with the launcher log and the console logs from last night and today.

Platform is Steam
Account name is NGC7293

mod_load_order.txt (204 Bytes)

darktide_launcher.log (153.2 KB)

console-2023-09-10-17.00.38-578614a3-48e6-46d2-a2b1-ebff01376d7f.log (368.0 KB)
console-2023-09-10-00.16.23-df2a4dc2-664e-477f-b734-0cd40a5bb73a.log (473.8 KB)

1 Like

I posted some potentially useful information on how to recreate this bug under support ticket 27914.

1 Like