Which line is 76? Don't make us count them.
What's the error message? That usually indicates what the problem is.
But because I was curious what this whole thing was about, I copied it into the onlinegdb Python interpreter (which I had assumed you were using) and gave it a whirl.
Well, you've written Python2 code, and the online interpreter is Python3, so I had to fix all the print "foo" to print("foo") and then it was ready to go. Mostly.
In any case, it looks like there is no problem with line 76 by itself. The problem is that you didn't properly end the input command that was started on line 72. It needs a closing parenthesis, making it:
input64 = input("""1 - Fight
2 - Run
3 - Use Chem
4 - Use Food""")Although once you fix that, you'll have a problem with line 78, "3 escape = True".
And then line 206 will need to change the colon ':' to a semicolon ';' (or at least remove it).
And line 62 is trying to access questvar4 which has not been defined here; is it supplied somewhere else? Or did you mean to use questvar, questvar2, or questvar3 instead?
And line 184 references gundamage, but probably you meant fullgundamage?
It looks like the variables attack and meleeattack are not defined before they are first used, unless the user happens to select "1 - fight" as their action. (all other choices, including invalid ones, run into the problem)
I assume you would notice and fix all those problems after you got the first one fixed.
On a side note, it is a good idea to have variable names indicate something about what they hold. So "input64" could be "playerChoice" or "userInput" or something else meaningful. The name "input64" gives no hint what it's used for, especially when there are red herrings like "input2" and "input65" laying around. For those two situations, it appears that what you really mean to be doing is something like input("(press Enter to continue)") without assigning the result to a variable (since you never look at it).
You should also learn how to make functions, so that you can divide up the code into manageable pieces, with each function doing one meaningful unit of work. Right now the entire program is a mass of nested ifs and elses which is really hard to read and maintain. You could make a chooseAction() function, which prompts the user for what action they would like to take, then calls fight(), run(), useChem(), or useFood() based on the input. Then it would be much clearer what is happening, and it's easier to add new features like letting the user choose again if they gave bad input (if the useChem() or useFood() return False, because the user has no chem/food, or because they decided to not use them). And you could have a function which displays Health and Radiation after every action/round, rather than just once at the beginning.
After you've figured out functions, it shouldn't be too hard to pick up Object-Oriented Programming, which will make it easier to collect data into meaningful groups, like weapons, or food, or chem…