I noticed this over the weekend-- each time I'd log out (of my own choosing or otherwise!) and then log back in again, it would spin up to "PATCH" and something appeared to come down every single time. It would go by so quickly I could never tell for sure, but it was definitely a .dll.
All patching is done into the hoggs, and then afterwards any files needed on disk (like executables) are copied out and written to the disk.
So the game launch process is if I'm reading this right rewriting certain game system files just prior to launch... each time? Is this a security thing in case people tamper with them? Just trying to think of what would be the need for that design wise.
So the game launch process is if I'm reading this right rewriting certain game system files just prior to launch... each time? Is this a security thing in case people tamper with them? Just trying to think of what would be the need for that design wise.
It checks them each time, if the timestamp and size match it doesn't actually copy any data (unless force verify is on, then it remirrors everything). It doesn't touch any system files, just the DLLs and EXEs you see in the subfolder.
I would immagine its for security, as somebody or something could tamper with the game .exe and .dll and take account details. although there are other ways to do it also, its one or 2 less for hackers to get you on.
Also it may stop people making 'private' versions of the game.
Comments
OK, thanks. The way it visually outputs is just confusing, as it says patching.
What are mirrored files for, anyway? Really just curious.
--Monkey
So the game launch process is if I'm reading this right rewriting certain game system files just prior to launch... each time? Is this a security thing in case people tamper with them? Just trying to think of what would be the need for that design wise.
Also it may stop people making 'private' versions of the game.