CS.RIN.RU - Steam Underground Community

Hi, i'm currently working on ACF updates, defining "archive" and "update" format.
as it has nothing to do with gcf/ncf, i need a new file format.

so i'm thinking i may make a new format supporting both gcf/ncf and acf. which means that in my future tools (cft2 ?) the current cft format will not be supported anymore.

as some other dev tools support the current format, what u guyz (devs and users) think about it ?

Suits me. As long as there is backwards compatibility (gcf/ncf) it's okay. I'm just wondering what will happen to the Updates DB, since it pretty much relies on your present impementation of "archive" and "update" format.
As Valve is gradually introducing the new format it would make sense not to abruptly replace previous update system, since it will do more harm than there are advantages. (Not to mention the leechers' rage )

_________________

So long as the old updates can be used, I have no problem with a new update format.

_________________
The phrase "Login to http://www.clue.org and issue the GET command" springs to mind...

I moderated this forum.

I'm making this new format more easily parsable for the update db if needed , but there would still be the same mecanisme :
archive files and update files

so nothing would change for update db.

The most important thing is that the old updates can still be applied. How that is done does not really matter, it could be a plugin independent from everything else. Then you could code the new stuff without worrying about backwards compatibility.

_________________
ℝ.

You may look at cachenet's archive/update options.

_________________
~