Appmanifest_XXXXXXXX

Don't.. Safety First.

It just identifies what game that app is.

Would advise you to not give it to him,he has no use for it,so its better to stay safe

Don't give it, they can download a game without owning it. I think so(?)

Don't hand out random files to random strangers.
Remember, one of the basic rules in internet security is: Be Paranoid.

Which guy? that is the question, if he's your friend that you know and speak to him often, ask him why, but I don't see a reason why not.
If it's some random guy, dont.

just take a text document, and then name/save it to that file name, send it to the person, everyone wins

The reason is because he own the game, but cant download it cuz he got internet traffic restriction at 10GB. And BFBC2 is 8GB already...

He's been in my friendlist since long ago, even tho i don't remember why are we friends.

The guy seems legit, got positive feedback from trading on his profile, and owns 100+ games.

I just wanted to make sure, if theres any fraudulent use of that file.

Thanks everyone tho!

Well, I thought that this was gonna be a new game entitled appmanifest_xxxxxx sadly, I was disappointed.

LOL @the people giving advice in this thread while having no clue about topic at hand, but i guess thats one of the basics of internet. Its safe to give that file to pretty much anyone, no relevant or compromising data is in it

I've asked friends for this exact file because of data corruption/transferring between hard drives requires it. It just contains the app identification strings, and where it's located. It can help save you from re-downloading if you already have the files downloaded. I had to do it with Saints Row the Third, twice. It's basically just a fancy .txt that says what verion the game is, file size, where it's located on the computer, app ID, and the last time it was launched.

It's perfectly fine to send it, he can't hack your account with your appmanifest_xx.acf files. It'll probably save him a day or two of downloading if he knows to open them as a .txt and edit the "appinstalldir" key.

Essentially the files are on his computer, but steam refuses to accept they are there because there is no appmanifest pointing to where they are, so it tries to download them again, rather than looking for the old non-associated files.

The appmanfest files are plain text identifier files for the current content delivery system Steam uses. They contain identification metadata and are completely safe (though equally pointless) to transfer. Here's my appmanifest_220 (Half-Life 2) as opened in notepad

"AppState"
{
"appID" "220"
"Universe" "1"
"StateFlags" "68"
"installdir" "Half-Life 2"
"LastUpdated" "1373945067"
"UpdateResult" "0"
"SizeOnDisk" "3982379997"
"buildid" "86989"
"LastOwner" "0"
"BytesToDownload" "0"
"BytesDownloaded" "0"
"UserConfig"
{
"name" "Half-Life 2"
"gameid" "220"
"language" "english"
"betakey" "public"
}
"MountedDepots"
{
"221" "3139631820230520823"
"222" "7243428813874054245"
}
}

Giving him the file won't allow him to do anything. Some believe having someone else's manifest for a game will change required data to download, access more DLC, allow account hijacking... all it does is display already publicly available metadata. It's quite worthless.

ok guys thanks a lot, im gunna send it then!