Text-based adventure survival horror game
I see you've ignored the advice from your previous question. To avoid duplication, I'm going to quote them:

From this answer:


  Goto
  
  At a first approximation, never use goto. It makes it more or less
  impossible to follow code. Without goto, you also don't need labels.
  Instead, just call different functions. Or keep an internal state
  machine. Or really any possible other solution. Code with goto like
  this is incredibly brittle - what if you want to add more states
  somewhere in between? Good luck keeping track of everything.


From this answer:


  There many things here that can be improved. First off, let's tackle
  some best practices. Generally, doing stuff like this with system
  isn't very good:
  
  
system("pause");
system("cls");

  
  
  To start off, system("pause"); is a bad way of "pausing" for user
  input. First off, there's a decently sized overhead just to execute a
  shell command, and doing this is rather insecure. If you really need
  to pause on user input, and ignore it, then just do something like
  this:

std::cin.get();

  
  Secondly, putting anything like this at the top of your file is a bad
  idea:
  
  
using namespace std;

  
  
  This pollutes your local namespace with everything in std, and it
  can lead to some name conflicts, especially if you're using a library
  like boost. There's a good reason it's named std and not
  standard. It's easier to prefix everything with std:: rather than
  standard::.


Now for some advice specific to this question:

First, all the newlines and tabs are quite noisy. You can consider putting it in a variable:

std::string tab(6, '\t');
std::cout &lt;&lt; tab &lt;&lt; "...";


Secondly, instead of your goto approach, it's more likely that you want a while loop instead. Some users insist that the while loop is a glorified goto, but without the negatives.

std::string answer;
while (std::cin &gt;&gt; answer)
{
    // ...
}