Hi, it is possibile to not heaving game data archived in PAK file? So when I patch game on steam or gog or any other eshop, people don't have to download few GB every time?

through the editor I am not sure, but you can use multiple PAKs to get around this(atleast it will allow you to split the assets into reasonable chunks to prevent multi GB patches), if you mean patch the game like content addition, then using new PAKs for those would also be better in that sense. also you don't need to submit new PAKs if the only thing you've changed is the executable itself(atleast it shouldn't)

Edit: I am not sure if this works but it should and that is dealing with the folder inside Esenthel editor folder found in projects, however I am not sure how that well that works.

You don't need this for steam. It automatically detects similar chunks (around 1 MB size) in each file and updates only the changed ones.
As for others then you can double click application properties and toggle the option called similar to "publish data as Pak"
For this option you specify 'DataPath' in the game instead of Paks.add (which is inside EE_INIT() in InitPre)
This however gives reduced performance (to have files stored separately instead of one big Pak)
Alternatively you can just distribute an installer that auto updates itself from your own server.
And last solution as Zervox mentioned is to have base Pak and patch Paks.

https://partner.steamgames.com/doc/sdk/u...ing_Depots

Quote:Each file is scanned and divided into small chunks of about 1MB. If the depot has been built before, this partitioning will preserve as many of the unchanged chunks as possible.

Ok, thanks for informations. We starting closed beta today (on steam), so we probably patch game every 2-3 days. I'm going to test how steam manage it.

Doing base packs and patch pack add quite of bit of gamesize at some point and is not recommended for big games iirc

I have to make a correction regarding what I said about multiple Paks.

what I meant is that you can split the Assets into
Models1
Models2
Audio1
Audio2

then if you only change data that belongs in Audio1 that is the only thing you need to upload to steam for patching instead of submitting one huge 10GB pak file(saves time uploading the new archive that will overwrite the original as well)

regarding the 1MB chunks data technique steam uses, the problem many developers have issues with it(I think this is why Pherael asked because it is not an unheard of problem people tend to have with some games on steam) is that they tend to use archiving methods/encryptions that gets rebuilt(their method might also be packaging the data in a random order),
then reencodes the entire library so none of the chunks will be registered as "unaltered"(atleast that is my thoughts on the matter)

Esenthel uses compression / encryption that's still compatible with steam's chunk system.