No problem, but think about this. When you output data to some medium, what are you doing? You are taking some variable or literal and writing it so you can see it somewhere (this could be a window, console, terminal, file, etc.). You can output in all sorts of ways, using escape charaters (ie \n), spaces, tabs, literals, variables, whatever you want really.
Now with input, what are we doing? We are taking some specified area of a medium, and reading data from it into a variable generally (You can also take input and do nothing at all with it, but thats not important). When you are inputting, you are sayin "Ok computer, take this segment of information right here, and store it in this". Whenever you use the extraction operator, it must be followed by a variable that you want this data stored in.
Now with the standard cin, it will read data from the stream, until cin hits its delimiter value, which for cin is a blank space. Now, it also wont actually process the data until it hits a newline character.
Something like this
cin >> v1 >> v2 >> v3;
Works just fine, because each extraction operator is followed by a variable each time. When this happens, it will read all data into v1 until the first blank space is encountered, and then it will read into v2 until the 2nd blank space, and so on.
These same ideas carry over to file I/O. When you are extracting data from a file, you must follow an extraction operator by a variable. So something like
file >> PlayerHealth>>"\n"
Will not work because you just put a literal after an extraction operator, so your compiler is getting all pissy.
http://www.cplusplus.com/reference/iostream/ifstream/