Not 100% sure if I understand what you are asking, but if I do, usually that is accomplished by making it the last condition ... so it is called if none of the known words applies (no explicit check if the word is not known, it is implicitly checked, because goto would have been called and the code would not have been reached).

Goto weirds me out, usually it is a loop over a list of words or if / else if / else statements ...

but you should be able to use a goto without any condition at the end, unless the context that it is taken out of does not allow that.

if %input1% equ bed goto bed_1
if %input1% equ door goto door_1
if %input1% equ TV goto tv_1
goto unknown_1

If that is not helpful you might need to specify the question / explain the situation in more detail ...

I don't recognize the language, but if there are containers that can store the known objects, then an explicit check would be possible - there are usually contains-methods that let you check if a list contains the object (String object in this case).

What do you have in place already? I guess it looks something like that?

:OutputState
Loop over gamestates in gamestates.txt, extract the description and echo it

:PromtAction
Write prompt message and assign input to variable
Goto HandleAction

:PromptObject
Write prompt message appropriate for current action
Goto HandleObjectAction

:PromptUseWith
Write prompt message and assign input to variable
Goto HandleUseWith

:HandleAction
Handle known action if no object is needed and goto PromptAction or OutputState
Goto PromptObject if a known action requires it
ECHO Action not found message
Goto PromptAction or OutputState

:HandleObjectAction
loop over objects.txt, extract the information you need for the action/object
Goto PromptUseWith if the object was found and the action requires another object
Handle object action if the object was found (set new gamestate) and goto PromptAction or OutputState
ECHO Object not found message
Goto PromptAction or OutputState

:HandleUseWith
loop over usewith.txt, extract the information you need for the action/objects
Handle object action if the object was found (set new gamestate) and goto PromptAction or OutputState
ECHO Object not found message
Goto PromptAction or OutputState

Commands would still be hardcoded, but you could read comma separated values files for the gamestate descriptions and object descriptions, gamestate changes etc. and assign the values of the record to variables.

In Bash I would probably use cat and sed, not sure what options CMD offers.

Any reason why you did not go for something more ... modern?

Well yes, instead of doing it this way

if %input27% equ metal goto metal_push_3
if %input27% equ bed goto bed_push_4
if %input27% equ brick goto brick_push_4
if %input27% equ bars goto bars_push_4
if %input27% equ liquid goto liquid_push_4

you would search the file for an occurrence of the word that the user has entered and store the text that should be displayed in a variable then always print the value of that variable if it does not equal an emptry string. Again, I know how I would do that in Bash, I only assume that there is a way to do something similar in CMD.

Guess you should think of a better way to handle gamestates. Try to have one push method and check the gamestate there. If you duplicate code like that you will develop more bad habits than actually gain valuable experience.

With the approach that I have outlined you could have one object file per gamestate.

Also ... many languages allow you to create a console application that you can execute from the command line. I bet most text-adventures were not written as command line scripts.

There are articles about writing text adventures. It might be helpful to read some of those to see how other people write a parser and deal with gamestates.