Tim Pilius

@Serverfrog Could you give me a bit more background on your specific use case for this request? What about it would you find useful in how you use this prefill?...

To the best of my knowledge there is no such thing as "Starcraft" anymore, it's only Starcraft Remastered `s1`. And no "Warcraft 3", only "Warcraft 3 : Reforged" with `w3`....

Hi Florian, Are you still seeing this issue a few weeks later? If it is I can try to dig a bit deeper

Closing since I haven't received any further info. Please feel free to reopen if the issue is still occurring.

In general, most of the documentation can/should be copy and pasted from SteamPrefill. Anything Steam specific should be removed.

Hi Ivan, Sorry to get back to you so late on this. Long story short... the way Battle.Net's has its pre-release content setup it isn't as simple as switching out...

Related issue from last time I looked at this, has a bit more discussion : #77

I'm not familiar with how Kubernetes works, but are the containers for this job being reused? Or run and then removed immediately? I think I might know what's going on...

Hi Chris, Apologies for the late reply. The solution to your issue is that BattlenetPrefill has a directory where it stores various configuration, and inside that folder is a file...

I'm going to close this for now. If the above doesn't solve your issue please feel free to reopen.